Main Page

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>VI-Toolkit</sitename>
    <dbname>vitoolkit_mw1</dbname>
    <base>https://wiki.vi-toolkit.com/index.php?title=Main_Page</base>
    <generator>MediaWiki 1.42.5</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">VI-Toolkit</namespace>
      <namespace key="5" case="first-letter">VI-Toolkit talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
    </namespaces>
  </siteinfo>
<page arvcontinue="">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1</id>
    <timestamp>2008-12-05T11:31:43Z</timestamp>
    <contributor>
      <username>MediaWiki default</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="448" xml:space="preserve">&lt;big&gt;'''MediaWiki has been successfully installed.'''&lt;/big&gt;

Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]</text>
    <sha1>4a6c39f2fbaf26606d74d99fd7e696f263fb2d0b</sha1>
  </revision>
  <revision>
    <id>8</id>
    <parentid>1</parentid>
    <timestamp>2008-12-06T02:52:50Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="460" xml:space="preserve">== VI Toolkit ==

Welcome at our new site which will contain information for developers about managing your Virtual Infrastructure using the available Software Development Kits from VMware.

This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here. If you want to find out how, then have a look [[VI-Toolkit:Users| here]]

We hope that you will enjoy the content posted on here!</text>
    <sha1>0464e73dba4e30ab079267cf72c520b675039b0c</sha1>
  </revision>
  <revision>
    <id>23</id>
    <parentid>8</parentid>
    <timestamp>2008-12-07T10:02:10Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="772" xml:space="preserve">== VI Toolkit ==

Welcome at our new site which will contain information for developers about extending and managing VMware virtual environments.
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide information for software developers. Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here. If you want to find out how, then have a look [[VI-Toolkit:Users| here]]

We hope that you will enjoy the content posted on here!</text>
    <sha1>39f2b90b086ccb86257f7a18f7b4f5c3c960c058</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VI-Toolkit:Users</title>
  <ns>4</ns>
  <id>2</id>
  <revision>
    <id>2</id>
    <timestamp>2008-12-05T15:14:04Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>users and restrictions</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="686" xml:space="preserve">=== Anonymous access ===
We do not allow anonymous edits on this web site. 
The sole reason for this is to combat spam a little bit.

=== Sign up ===
You are however welcome to add/edit content to the site after signing up.
Signing only requires a working email address and a name.
You can sign up [[Special:UserLogin| here]]

When adding content there is a restriction that the subject must be about VMware related products, problems or solutions.
For the moment we do not welcome posts with a clear commercial intent where a user is endorsing his or her product.
This rule might change in the future, it is not cast in stone. 

If you have a question about that then send us an email.</text>
    <sha1>6c8c2d33d774b027660d6f8652723ae05043972f</sha1>
  </revision>
  <revision>
    <id>3</id>
    <parentid>2</parentid>
    <timestamp>2008-12-05T15:15:08Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[Users]] moved to [[Vi-toolkit:Users]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="686" xml:space="preserve">=== Anonymous access ===
We do not allow anonymous edits on this web site. 
The sole reason for this is to combat spam a little bit.

=== Sign up ===
You are however welcome to add/edit content to the site after signing up.
Signing only requires a working email address and a name.
You can sign up [[Special:UserLogin| here]]

When adding content there is a restriction that the subject must be about VMware related products, problems or solutions.
For the moment we do not welcome posts with a clear commercial intent where a user is endorsing his or her product.
This rule might change in the future, it is not cast in stone. 

If you have a question about that then send us an email.</text>
    <sha1>6c8c2d33d774b027660d6f8652723ae05043972f</sha1>
  </revision>
  <revision>
    <id>6</id>
    <parentid>3</parentid>
    <timestamp>2008-12-05T16:14:47Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="726" xml:space="preserve">=== Anonymous access ===
We do not allow anonymous edits on this web site. 
The sole reason for this is to combat spam a little bit.

=== Sign up ===
You are however welcome to add/edit content to the site after signing up for a user account.
Joining the site only requires a working email address and a name.
You can sign up [[Special:UserLogin&amp;type=signup| here]]

When adding content there is a restriction that the subject must be about VMware related products, problems or solutions.
For the moment we do not welcome posts with a clear commercial intent where a user is endorsing his or her product.
This rule might change in the future, it is not cast in stone. 

If you have a question about that then send us an email.</text>
    <sha1>d4c52832abef4e17304d13eeadb354a161a80af4</sha1>
  </revision>
  <revision>
    <id>7</id>
    <parentid>6</parentid>
    <timestamp>2008-12-05T16:17:06Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="714" xml:space="preserve">=== Anonymous access ===
We do not allow anonymous edits on this web site. 
The sole reason for this is to combat spam a little bit.

=== Sign up ===
You are however welcome to add/edit content to the site after signing up for a user account.
Joining the site only requires a working email address and a name.
You can sign up [[Special:UserLogin| here]]

When adding content there is a restriction that the subject must be about VMware related products, problems or solutions.
For the moment we do not welcome posts with a clear commercial intent where a user is endorsing his or her product.
This rule might change in the future, it is not cast in stone. 

If you have a question about that then send us an email.</text>
    <sha1>058b4e16b52ca5ffbac5192eabdbea5bdb938b41</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Users</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>4</id>
    <timestamp>2008-12-05T15:15:08Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>[[Users]] moved to [[Vi-toolkit:Users]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="30" xml:space="preserve">#REDIRECT [[Vi-toolkit:Users]]</text>
    <sha1>93230c1e730834098d785a109c000a31bab3b573</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VI-Toolkit:About</title>
  <ns>4</ns>
  <id>4</id>
  <revision>
    <id>5</id>
    <timestamp>2008-12-05T15:26:02Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== About ====  This site is created in order to be able to store knowledge about Virtual Infrastructure and related VMware products.  At start of the site this will most likely be genera...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="846" xml:space="preserve">==== About ====

This site is created in order to be able to store knowledge about Virtual Infrastructure and related VMware products.

At start of the site this will most likely be general information about how-to solve particular problems, but over time the intention is to move the focus slightly over to managing the Virtual Infrastructure using the toolkits available from VMware.

There are many ways in which you can manage your Virtual environment and it is intended that the way in which you can do this is documented on this site.

The site is initiated by [http://communities.vmware.com/people/wila Wil van Antwerpen] but everyone is welcome to add his or her notes and/or ideas.

Hopefully this site will contribute to the general knowledge on managing your Virtualisation journey and help out on enjoying the journey as much as I do.</text>
    <sha1>060f86159ea868a371fdcf493ecf266b9aeb9e00</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>MediaWiki:Sidebar</title>
  <ns>8</ns>
  <id>5</id>
  <revision>
    <id>9</id>
    <timestamp>2008-12-06T15:41:10Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>removed current events</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="178" xml:space="preserve">* navigation
** mainpage|mainpage-description
** portal-url|portal
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
* SEARCH
* TOOLBOX
* LANGUAGES</text>
    <sha1>ea4584f4fef298379bead762e0d94a3bc4ecdc8b</sha1>
  </revision>
  <revision>
    <id>35</id>
    <parentid>9</parentid>
    <timestamp>2008-12-07T11:07:52Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="201" xml:space="preserve">* navigation
** mainpage|mainpage-description
** portal-url|portal
** recentchanges-url|recentchanges
** resources|resources
** randompage-url|randompage
** helppage|help
* SEARCH
* TOOLBOX
* LANGUAGES</text>
    <sha1>ff6d574e0751cc86ed48c62a0982d545120839b6</sha1>
  </revision>
  <revision>
    <id>36</id>
    <parentid>35</parentid>
    <timestamp>2008-12-07T11:08:39Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="201" xml:space="preserve">* navigation
** mainpage|mainpage-description
** portal-url|portal
** recentchanges-url|recentchanges
** resources|Resources
** randompage-url|randompage
** helppage|help
* SEARCH
* TOOLBOX
* LANGUAGES</text>
    <sha1>ba01ec79e1fcf370ed694d227c53844b807bc1db</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VI-Toolkit:Community Portal</title>
  <ns>4</ns>
  <id>6</id>
  <revision>
    <id>10</id>
    <timestamp>2008-12-06T23:32:12Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: [[VI Plugin]]  [[SDK]]  [[Java]]  [[Perl]]  [[.net]]  [[bash]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="62" xml:space="preserve">[[VI Plugin]]

[[SDK]]

[[Java]]

[[Perl]]

[[.net]]

[[bash]]</text>
    <sha1>e25ff4592cc4331ace096a261fa3837e14b7c61b</sha1>
  </revision>
  <revision>
    <id>32</id>
    <parentid>10</parentid>
    <timestamp>2008-12-07T11:01:15Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="257" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.


[[VI Plugin]]

[[SDK]]

[[Java]]

[[Perl]]

[[.net]]

[[bash]]</text>
    <sha1>861584b51b7f708e28d70ddd25052a3fde17f383</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VI Plugin</title>
  <ns>0</ns>
  <id>7</id>
  <revision>
    <id>11</id>
    <timestamp>2008-12-06T23:33:33Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: === VI plugins ===  ==== SVMotion ====  SVMotion is a VMware Infrastructure (VI) client plug-in that extends the client's functionality by providing an integrated, graphical tool that can ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="292" xml:space="preserve">=== VI plugins ===

==== SVMotion ====

SVMotion is a VMware Infrastructure (VI) client plug-in that extends the client's functionality by providing an integrated, graphical tool that can be used to invoke storage VMotion (SVMotion) operations. 

http://sourceforge.net/projects/vip-svmotion/</text>
    <sha1>51e9caa5080a1154e20cfefdab0e731d3bdc8c2f</sha1>
  </revision>
  <revision>
    <id>12</id>
    <parentid>11</parentid>
    <timestamp>2008-12-06T23:34:31Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="36" xml:space="preserve">=== VI plugins ===

[[vip-svmotion]]</text>
    <sha1>d9e5456ad2127f6f4a9f431050151db3a62c30a2</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Vip-svmotion</title>
  <ns>0</ns>
  <id>8</id>
  <revision>
    <id>13</id>
    <timestamp>2008-12-06T23:35:22Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== SVMotion ====  SVMotion is a VMware Infrastructure (VI) client plug-in that extends the client's functionality by providing an integrated, graphical tool that can be used to invoke st...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="296" xml:space="preserve">==== SVMotion ====

SVMotion is a VMware Infrastructure (VI) client plug-in that extends the client's functionality by providing an integrated, graphical tool that can be used to invoke storage VMotion (SVMotion) operations. 

http://sourceforge.net/projects/vip-svmotion/

[[Category:VI Plugin]]</text>
    <sha1>12d4b42e8b8a7a6c461c5be0d45388fe97394c4c</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>SDK</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>14</id>
    <timestamp>2008-12-06T23:39:03Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: [[VI Toolkit for Java]]  [[VI Toolkit for .net]]  [[VI Toolkit for perl]]  [[Vassert Linux SDK]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="96" xml:space="preserve">[[VI Toolkit for Java]]

[[VI Toolkit for .net]]

[[VI Toolkit for perl]]

[[Vassert Linux SDK]]</text>
    <sha1>233709d1786cd308668c8ee0ab7d4a46083424e4</sha1>
  </revision>
  <revision>
    <id>19</id>
    <parentid>14</parentid>
    <timestamp>2008-12-07T09:53:58Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="116" xml:space="preserve">[[VI Toolkit for Java]]

[[VI Toolkit for .net]]

[[VI Toolkit for perl]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]</text>
    <sha1>a72b7074a03f24cbe3ca661d6f4e80c3aa53a28e</sha1>
  </revision>
  <revision>
    <id>24</id>
    <parentid>19</parentid>
    <timestamp>2008-12-07T10:07:37Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="152" xml:space="preserve">[[VI Toolkit for Java]]

[[VMware Infrastructure Java API]]

[[VI Toolkit for .net]]

[[VI Toolkit for perl]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]</text>
    <sha1>a3344c8648550c8c8b78dad8a6e8a5e048885164</sha1>
  </revision>
  <revision>
    <id>30</id>
    <parentid>24</parentid>
    <timestamp>2008-12-07T10:19:57Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="162" xml:space="preserve">[[VI Toolkit for Java]]

[[VMware Infrastructure Java API]]

[[VI Toolkit for .net]]

[[VI Toolkit for perl]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[JVix]]</text>
    <sha1>4403aa0b13329d3bb8b2866506bccb5eab4107f0</sha1>
  </revision>
  <revision>
    <id>33</id>
    <parentid>30</parentid>
    <timestamp>2008-12-07T11:02:23Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="103" xml:space="preserve">[[VI Toolkit]]

[[VMware Infrastructure Java API]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[JVix]]</text>
    <sha1>310226b835f007e418b7a297c19a1e237919340c</sha1>
  </revision>
  <revision>
    <id>40</id>
    <parentid>33</parentid>
    <timestamp>2008-12-07T11:46:24Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="102" xml:space="preserve">[[VI Toolkit]]

[[VMware Infrastructure Java API]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]</text>
    <sha1>a2119479e6df71d651cac9e080ac734569048562</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Vitforjava</title>
  <ns>0</ns>
  <id>10</id>
  <revision>
    <id>15</id>
    <timestamp>2008-12-06T23:40:23Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== VI Toolkit for Java ====  The VI Toolkit for Java is a Java library that is patterned after the VI Perl Toolkit. Administrators and developers who like the ability to quickly create s...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="366" xml:space="preserve">==== VI Toolkit for Java ====

The VI Toolkit for Java is a Java library that is patterned after the VI Perl Toolkit. Administrators and developers who like the ability to quickly create scripts with the perl toolkit but appreciate the depth of Java will love the VI Toolkit for Java. 

http://sourceforge.net/projects/vitforjava/

[[Category:SDK]] [[Category:Java]]</text>
    <sha1>d040307f53e75fbb1eddeefe9c497dc0cdb6d1c0</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VI Toolkit for windows</title>
  <ns>0</ns>
  <id>11</id>
  <revision>
    <id>16</id>
    <timestamp>2008-12-06T23:41:54Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== VI Toolkit for .net ====  The VI Toolkit for .NET is a .NET library designed to bring object-oriented design to the VI API by transforming managed object references into first class o...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="349" xml:space="preserve">==== VI Toolkit for .net ====

The VI Toolkit for .NET is a .NET library designed to bring object-oriented design to the VI API by transforming managed object references into first class objects, as well as providing helpful method, property, and class abstractions.

http://sourceforge.net/projects/vitfordotnet/

[[Category:SDK]] [[Category:.net]]</text>
    <sha1>cd29a17bd3e1dde5aa3337b8c4f8f0dcde79975a</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VI Toolkit for perl</title>
  <ns>0</ns>
  <id>12</id>
  <revision>
    <id>17</id>
    <timestamp>2008-12-06T23:43:20Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== VI Toolkit for perl ====  The VMware Virtual Infrastructure Perl Toolkit (VI Perl Toolkit) provides a set of libraries and scripts to manage and control VMware virtual machines and se...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="341" xml:space="preserve">==== VI Toolkit for perl ====

The VMware Virtual Infrastructure Perl Toolkit (VI Perl Toolkit) provides a set of libraries and scripts to manage and control VMware virtual machines and servers using the VMware Virtual Infrastructure Web Service interface. 

http://sourceforge.net/projects/viperltoolkit/

[[Category:SDK]] [[Category:perl]]</text>
    <sha1>4ca73d71b7d5e9a973e247eed5ce09656b16b1b1</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Vassert Linux SDK</title>
  <ns>0</ns>
  <id>13</id>
  <revision>
    <id>18</id>
    <timestamp>2008-12-07T09:52:23Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vassert Linux SDK ====  Vassert is a new feature from VMware Workstation. It is promising for developers to enhance code reliablity with less run-time cost. This project is a library ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="284" xml:space="preserve">==== Vassert Linux SDK ====

Vassert is a new feature from VMware Workstation. It is promising for developers to enhance code reliablity with less run-time cost. This project is a library to enable vassert usage under Linux guest os. 

http://sourceforge.net/projects/vassertlinuxsdk/</text>
    <sha1>0c1be04fa456f8c3f239743002ca029f7beaa4a0</sha1>
  </revision>
  <revision>
    <id>21</id>
    <parentid>18</parentid>
    <timestamp>2008-12-07T09:56:34Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="302" xml:space="preserve">==== Vassert Linux SDK ====

Vassert is a new feature from VMware Workstation. It is promising for developers to enhance code reliablity with less run-time cost. This project is a library to enable vassert usage under Linux guest os. 

http://sourceforge.net/projects/vassertlinuxsdk/

[[Category:SDK]]</text>
    <sha1>3d387cc775975a45ea00b538ff148fa19d7b1f12</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VProbe Toolkit</title>
  <ns>0</ns>
  <id>14</id>
  <revision>
    <id>20</id>
    <timestamp>2008-12-07T09:54:18Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== VProbe Toolkit ====  This provides an interactive, programmer-friendly interface to VMware's VProbes facility. VProbes is a safe, dynamic technology for instrumenting software running...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="290" xml:space="preserve">==== VProbe Toolkit ====

This provides an interactive, programmer-friendly interface to VMware's VProbes facility. VProbes is a safe, dynamic technology for instrumenting software running in virtual machines, and the software stack itself. 

http://sourceforge.net/projects/vprobe-toolkit/</text>
    <sha1>f932073c238bdf2b8b9d885a8d3babbffcedfe56</sha1>
  </revision>
  <revision>
    <id>22</id>
    <parentid>20</parentid>
    <timestamp>2008-12-07T09:56:57Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="308" xml:space="preserve">==== VProbe Toolkit ====

This provides an interactive, programmer-friendly interface to VMware's VProbes facility. VProbes is a safe, dynamic technology for instrumenting software running in virtual machines, and the software stack itself. 

http://sourceforge.net/projects/vprobe-toolkit/

[[Category:SDK]]</text>
    <sha1>457f265b5371fdb6eaaabfadea1e2d62bb2e39fa</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VMware Infrastructure Java API</title>
  <ns>0</ns>
  <id>15</id>
  <revision>
    <id>25</id>
    <timestamp>2008-12-07T10:08:02Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== VMware Infrastructure Java API ====  The VMware Virtual Infrastructure Java API provides a set of libraries with full support of managed object model and utilities to manage and contr...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="364" xml:space="preserve">==== VMware Infrastructure Java API ====

The VMware Virtual Infrastructure Java API provides a set of libraries with full support of managed object model and utilities to manage and control VMware virtual machines and servers using the VMwware Virtual Infrastructure Web service interface. 

http://sourceforge.net/projects/vijava/

http://vijava.sourceforge.net/</text>
    <sha1>7cc2c4901f5eaf6e939ac6a6ae4cdb2a6922407e</sha1>
  </revision>
  <revision>
    <id>26</id>
    <parentid>25</parentid>
    <timestamp>2008-12-07T10:09:01Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="400" xml:space="preserve">==== VMware Infrastructure Java API ====

The VMware Virtual Infrastructure Java API provides a set of libraries with full support of managed object model and utilities to manage and control VMware virtual machines and servers using the VMwware Virtual Infrastructure Web service interface. 

http://sourceforge.net/projects/vijava/

http://vijava.sourceforge.net/

[[Category:SDK]] [[Category:Java]]</text>
    <sha1>a0442e9f83a858f64b00d9692b89d3b4f937d88b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Java</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>27</id>
    <timestamp>2008-12-07T10:11:04Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: [[VmWare commander for Java]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="29" xml:space="preserve">[[VmWare commander for Java]]</text>
    <sha1>ae382df9feef70a79adad024e313e34d628795f8</sha1>
  </revision>
  <revision>
    <id>46</id>
    <parentid>27</parentid>
    <timestamp>2008-12-07T11:59:54Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44" xml:space="preserve">[[VmWare commander for Java]]

[[Live View]]</text>
    <sha1>0741be6334b40b598ec0237d0c59c66b27e5e99f</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VmWare commander for Java</title>
  <ns>0</ns>
  <id>17</id>
  <revision>
    <id>28</id>
    <timestamp>2008-12-07T10:11:51Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== VmWare commander for Java ====  For starting / stopping, getting state, etc. of the VmWare guests. Translate Java calls into vmware shell commands, which are then executed through a l...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="315" xml:space="preserve">==== VmWare commander for Java ====

For starting / stopping, getting state, etc. of the VmWare guests. Translate Java calls into vmware shell commands, which are then executed through a locale shell or through a secure remote shell on to the VmWare server console.

http://sourceforge.net/projects/java-vmware-cmd/</text>
    <sha1>02ce716dea1c25e7b629ab8a143d9eb53bfe9e06</sha1>
  </revision>
  <revision>
    <id>29</id>
    <parentid>28</parentid>
    <timestamp>2008-12-07T10:14:51Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="334" xml:space="preserve">==== VmWare commander for Java ====

For starting / stopping, getting state, etc. of the VmWare guests. Translate Java calls into vmware shell commands, which are then executed through a locale shell or through a secure remote shell on to the VmWare server console.

http://sourceforge.net/projects/java-vmware-cmd/

[[Category:Java]]</text>
    <sha1>e6e0436a8b6ff2999f8f5be3802d410070ff7e52</sha1>
  </revision>
  <revision>
    <id>48</id>
    <parentid>29</parentid>
    <timestamp>2008-12-07T12:01:34Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="361" xml:space="preserve">==== VmWare commander for Java ====

For starting / stopping, getting state, etc. of the VmWare guests. Translate Java calls into vmware shell commands, which are then executed through a locale shell or through a secure remote shell on to the VmWare server console.

http://sourceforge.net/projects/java-vmware-cmd/

[[Category:Java]] [[Category:VM Management]]</text>
    <sha1>56f943254dd837b04e7920542e67d56f95d4d7ff</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>JVix</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>31</id>
    <timestamp>2008-12-07T10:20:05Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== JVix ====  JVix is a Java wrapper to the VMware VIX API, allowing control of virtual machines through a Java interface.  http://sourceforge.net/projects/jvix/</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">==== JVix ====

JVix is a Java wrapper to the VMware VIX API, allowing control of virtual machines through a Java interface.

http://sourceforge.net/projects/jvix/</text>
    <sha1>eb75c6d1967081a215a5369ac4543ec12f953225</sha1>
  </revision>
  <revision>
    <id>43</id>
    <parentid>31</parentid>
    <timestamp>2008-12-07T11:48:42Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="200" xml:space="preserve">==== JVix ====

JVix is a Java wrapper to the VMware VIX API, allowing control of virtual machines through a Java interface.

http://sourceforge.net/projects/jvix/


[[Category:SDK]] [[Category:Java]]</text>
    <sha1>db5b88d9026d19ab55a2a597fca2c3cb302f08e9</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VI Toolkit</title>
  <ns>0</ns>
  <id>19</id>
  <revision>
    <id>34</id>
    <timestamp>2008-12-07T11:02:33Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: [[VI Toolkit for Java]]  [[VI Toolkit for .net]]  [[VI Toolkit for perl]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="73" xml:space="preserve">[[VI Toolkit for Java]]

[[VI Toolkit for .net]]

[[VI Toolkit for perl]]</text>
    <sha1>978ea7a0c877bb4fd12af7284280b64f7ee8f1ab</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>37</id>
    <timestamp>2008-12-07T11:31:53Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: Places to visit for scripts and code snippets  * [[http://blogs.vmware.com/vipowershell VMware powershell blog]]  * [[http://www.vmware.com/communities/content/developer/samplecode/ VMware...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="570" xml:space="preserve">Places to visit for scripts and code snippets

* [[http://blogs.vmware.com/vipowershell VMware powershell blog]]

* [[http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]]

* [[http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]]

* [[http://communities.vmware.com/community/developer/utilities?view=documents VMware Community sample code documents]]

* [[http://powerscripting.net/ Powershell powerscripting.net]]

* [[http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]]</text>
    <sha1>68f34502d2d4130f3c18871e227ddc81c609de8c</sha1>
  </revision>
  <revision>
    <id>38</id>
    <parentid>37</parentid>
    <timestamp>2008-12-07T11:32:27Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="558" xml:space="preserve">Places to visit for scripts and code snippets

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://communities.vmware.com/community/developer/utilities?view=documents VMware Community sample code documents]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]</text>
    <sha1>bae1847e6c7beb755dfd7f4494b9ddb185df56f3</sha1>
  </revision>
  <revision>
    <id>39</id>
    <parentid>38</parentid>
    <timestamp>2008-12-07T11:35:00Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>removed documents page on sample code forum, looks like it has the same content</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="439" xml:space="preserve">Places to visit for scripts and code snippets

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]</text>
    <sha1>306f64ebb517a8f116a8826d1e325b8f050ee955</sha1>
  </revision>
  <revision>
    <id>50</id>
    <parentid>39</parentid>
    <timestamp>2008-12-07T12:07:11Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="509" xml:space="preserve">Places to visit for scripts and code snippets

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]</text>
    <sha1>887d390c1c1de95d476d3c0a4a3ba5acebef9eb3</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>41</id>
    <timestamp>2008-12-07T11:47:07Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page:  [[JVix]]  [[pyVix]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">
[[JVix]]

[[pyVix]]</text>
    <sha1>bc338db5bdc86a38c270c21c45062f62a84f0bce</sha1>
  </revision>
  <revision>
    <id>45</id>
    <parentid>41</parentid>
    <timestamp>2008-12-07T11:56:44Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="227" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

==== 3rd party ====
[[JVix]]

[[pyVix]]</text>
    <sha1>314fb4bba60c71f05b699a3f50a97aba10b430f9</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>PyVix</title>
  <ns>0</ns>
  <id>22</id>
  <revision>
    <id>42</id>
    <timestamp>2008-12-07T11:47:35Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Pyvix ====  pyvix is a Python wrapper for the VMWare(R) VIX C API that allows Python to programmatically control VMWare(R) virtual machines. Example operations include: powering on; s...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="309" xml:space="preserve">==== Pyvix ====

pyvix is a Python wrapper for the VMWare(R) VIX C API that allows Python to programmatically control VMWare(R) virtual machines. Example operations include: powering on; suspending; creating, reverting to, and removing snapshots; and running programs. 

http://sourceforge.net/projects/pyvix/</text>
    <sha1>5134750bcc23ac1334738018a5ea8930f2084a16</sha1>
  </revision>
  <revision>
    <id>44</id>
    <parentid>42</parentid>
    <timestamp>2008-12-07T11:49:10Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="348" xml:space="preserve">==== Pyvix ====

pyvix is a Python wrapper for the VMWare(R) VIX C API that allows Python to programmatically control VMWare(R) virtual machines. Example operations include: powering on; suspending; creating, reverting to, and removing snapshots; and running programs. 

http://sourceforge.net/projects/pyvix/


[[Category:SDK]] [[Category:python]]</text>
    <sha1>d750c917c8c9170c43110d5b1efc04d5f768d5b7</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Live View</title>
  <ns>0</ns>
  <id>23</id>
  <revision>
    <id>47</id>
    <timestamp>2008-12-07T12:00:07Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Live View ====  LiveView is a forensics tool that creates a VMware virtual machine out of a raw (dd-style) disk image. This allows an examiner to "boot up" the image and gain an inter...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="315" xml:space="preserve">==== Live View ====

LiveView is a forensics tool that creates a VMware virtual machine out of a raw (dd-style) disk image. This allows an examiner to "boot up" the image and gain an interactive, user-level perspective of the environment, all without modifying the image. 

http://sourceforge.net/projects/liveview/</text>
    <sha1>bd31cc3bc0c54eed3da0f1e4c65092edab6b43fb</sha1>
  </revision>
  <revision>
    <id>49</id>
    <parentid>47</parentid>
    <timestamp>2008-12-07T12:02:19Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="357" xml:space="preserve">==== Live View ====

LiveView is a forensics tool that creates a VMware virtual machine out of a raw (dd-style) disk image. This allows an examiner to "boot up" the image and gain an interactive, user-level perspective of the environment, all without modifying the image. 

http://sourceforge.net/projects/liveview/

[[Category:Java]] [[Category:Forensics]]</text>
    <sha1>83e824b95a191d2d77feb925a84dc304c436a458</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>51</id>
    <parentid>50</parentid>
    <timestamp>2008-12-07T12:08:18Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="530" xml:space="preserve">Places to visit for scripts, code snippets and tools with sources.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]</text>
    <sha1>0058a22fd7dc60b1564c8e9b6dafd56fd35db147</sha1>
  </revision>
  <revision>
    <id>58</id>
    <parentid>51</parentid>
    <timestamp>2008-12-07T20:51:02Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="661" xml:space="preserve">Places to visit for scripts, code snippets and tools with sources.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]</text>
    <sha1>1e93847a7f586af8b83b38028e47a52eaa65f7c0</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>VI-Toolkit:Community Portal</title>
  <ns>4</ns>
  <id>6</id>
  <revision>
    <id>52</id>
    <parentid>32</parentid>
    <timestamp>2008-12-07T19:48:52Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="273" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.


[[VI Plugin]]

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[.net]]

[[bash]]</text>
    <sha1>94bf1bfb406d52e297b9b05f9ca21fc06e582eb5</sha1>
  </revision>
  <revision>
    <id>60</id>
    <parentid>52</parentid>
    <timestamp>2008-12-07T21:01:09Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="343" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.
Hopefully we'll succeed at that over time, it is a pretty high goal :)

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[.net]]

[[bash]]</text>
    <sha1>d1aad87bf04dda027b57948a2fb0d10568e1ffbf</sha1>
  </revision>
  <revision>
    <id>61</id>
    <parentid>60</parentid>
    <timestamp>2008-12-07T21:03:26Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="344" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal :)

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[.net]]

[[bash]]</text>
    <sha1>62ec32c97517798b7ec5033a54e978283cc96d4e</sha1>
  </revision>
  <revision>
    <id>80</id>
    <parentid>61</parentid>
    <timestamp>2008-12-08T17:27:32Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="357" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal :)

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[.net]]

[[bash]]

[[scripts]]</text>
    <sha1>8737993d6ba3efa4f5573e33eeba072c46200023</sha1>
  </revision>
  <revision>
    <id>98</id>
    <parentid>80</parentid>
    <timestamp>2008-12-09T18:02:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="422" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[.net]]

[[bash]]

[[scripts]]

[[Projects]]</text>
    <sha1>bf7c9e7693a6c20dab518c2eaeeb163488f7cbfa</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>53</id>
    <timestamp>2008-12-07T20:16:45Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/defau...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="220" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]</text>
    <sha1>44660121a176fc6af62f08c860d17e3feef6b282</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>VI Toolkit for windows</title>
  <ns>0</ns>
  <id>11</id>
  <revision>
    <id>54</id>
    <parentid>16</parentid>
    <timestamp>2008-12-07T20:45:12Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[VI Toolkit for .net]] moved to [[VI Toolkit for windows]]: combine page with VMware's official release</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="349" xml:space="preserve">==== VI Toolkit for .net ====

The VI Toolkit for .NET is a .NET library designed to bring object-oriented design to the VI API by transforming managed object references into first class objects, as well as providing helpful method, property, and class abstractions.

http://sourceforge.net/projects/vitfordotnet/

[[Category:SDK]] [[Category:.net]]</text>
    <sha1>cd29a17bd3e1dde5aa3337b8c4f8f0dcde79975a</sha1>
  </revision>
  <revision>
    <id>57</id>
    <parentid>54</parentid>
    <timestamp>2008-12-07T20:48:29Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="572" xml:space="preserve">==== VI Toolkit for windows ====

The official [http://www.vmware.com/support/developer/windowstoolkit/ VMware VI Toolkit for windows landing page] for accessing the Virtual Infrastructure API using [[PowerShell]] or .net

==== VI Toolkit for .net ====

The VI Toolkit for .NET is a .NET library designed to bring object-oriented design to the VI API by transforming managed object references into first class objects, as well as providing helpful method, property, and class abstractions.

http://sourceforge.net/projects/vitfordotnet/

[[Category:SDK]] [[Category:.net]]</text>
    <sha1>75717e65b760a348d7325ab6d1fe4cc89e12f187</sha1>
  </revision>
  <revision>
    <id>59</id>
    <parentid>57</parentid>
    <timestamp>2008-12-07T20:57:26Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="989" xml:space="preserve">==== VI Toolkit for windows ====

The official [http://www.vmware.com/support/developer/windowstoolkit/ VMware VI Toolkit for windows landing page] for accessing the Virtual Infrastructure API using [[PowerShell]] or .net

==== VI Toolkit extensions ====

For this you'll need to upgrade to [http://www.microsoft.com/downloads/details.aspx?familyid=7C8051C2-9BFC-4C81-859D-0864979FA403&amp;displaylang=en PowerShell 2 CTP2] and the code is at:
http://www.codeplex.com/vitoolkitextensions

See this NTPRO.nl article for details:
[http://www.ntpro.nl/blog/archives/741-Enabling-the-VI-Toolkit-Extensions.html Enabling the VI Toolkit Extensions]

==== VI Toolkit for .net ====

The VI Toolkit for .NET is a .NET library designed to bring object-oriented design to the VI API by transforming managed object references into first class objects, as well as providing helpful method, property, and class abstractions.

http://sourceforge.net/projects/vitfordotnet/

[[Category:SDK]] [[Category:.net]]</text>
    <sha1>a3ff03791187295d1ee61c859031bc24e55fd3a1</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>VI Toolkit for .net</title>
  <ns>0</ns>
  <id>25</id>
  <revision>
    <id>55</id>
    <timestamp>2008-12-07T20:45:12Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>[[VI Toolkit for .net]] moved to [[VI Toolkit for windows]]: combine page with VMware's official release</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="36" xml:space="preserve">#REDIRECT [[VI Toolkit for windows]]</text>
    <sha1>df58561ca663f66d8c861353ddc5f45c58d58845</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>VI Toolkit</title>
  <ns>0</ns>
  <id>19</id>
  <revision>
    <id>56</id>
    <parentid>34</parentid>
    <timestamp>2008-12-07T20:45:58Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="76" xml:space="preserve">[[VI Toolkit for windows]]

[[VI Toolkit for perl]]

[[VI Toolkit for Java]]</text>
    <sha1>7e0582a8e130df91613b24be40aac894175e382e</sha1>
  </revision>
  <revision>
    <id>62</id>
    <parentid>56</parentid>
    <timestamp>2008-12-07T21:32:39Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="221" xml:space="preserve">The VMware Infrastructure Toolkit is the interface to the VMware Infrastructure API (VI API) for administering your virtual machines and hosts.

[[VI Toolkit for windows]]

[[VI Toolkit for perl]]

[[VI Toolkit for Java]]</text>
    <sha1>fc2b7cda7c95a71af5460bc9898bdebfbfb4a854</sha1>
  </revision>
  <revision>
    <id>90</id>
    <parentid>62</parentid>
    <timestamp>2008-12-08T19:11:37Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="307" xml:space="preserve">The VMware Infrastructure Toolkit is the interface to the VMware Infrastructure API (VI API) for administering your virtual machines and hosts.

[[VI Toolkit for windows]]

[[VI Toolkit for perl]]

[[VMware Infrastructure Java API]]

===3rd party ===

* [[VI Toolkit for Java]] merged with the above project</text>
    <sha1>1a928f639de7faaf18d2dbb772c67712577cec8b</sha1>
  </revision>
  <revision>
    <id>93</id>
    <parentid>90</parentid>
    <timestamp>2008-12-08T19:13:48Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="298" xml:space="preserve">The VMware Infrastructure Toolkit is the interface to the VMware Infrastructure API (VI API) for administering your virtual machines and hosts.

[[VI Toolkit for windows]]

[[VI Toolkit for perl]]

[[VMware Infrastructure Java API]]

===3rd party ===

* [[Vitforjava]] merged with the above project</text>
    <sha1>1d406ca32548adde738699384ff797d72cfe1c31</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Perl</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>63</id>
    <timestamp>2008-12-07T22:01:02Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: [[Esx scripts]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">[[Esx scripts]]</text>
    <sha1>e0027826927deb43af7c7c83671552fbc587e9f6</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Esx scripts</title>
  <ns>0</ns>
  <id>27</id>
  <revision>
    <id>64</id>
    <timestamp>2008-12-07T22:01:32Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== esx scripts ====  Scripts written that help you manage VMWare ESX   http://sourceforge.net/projects/esx-scripts/</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="117" xml:space="preserve">==== esx scripts ====

Scripts written that help you manage VMWare ESX 

http://sourceforge.net/projects/esx-scripts/</text>
    <sha1>74ec499a89bc6412caec347210bd145eea7092b7</sha1>
  </revision>
  <revision>
    <id>65</id>
    <parentid>64</parentid>
    <timestamp>2008-12-07T22:02:39Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="164" xml:space="preserve">==== esx scripts ====

Scripts written that help you manage VMWare ESX 

http://sourceforge.net/projects/esx-scripts/


[[Category:Perl]] [[Category:VM Management]]</text>
    <sha1>5df022cd75898e26de8ee404f602b3d06c4f510b</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>SDK</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>66</id>
    <parentid>40</parentid>
    <timestamp>2008-12-07T22:45:36Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="143" xml:space="preserve">[[VI Toolkit]]

[[VMware Infrastructure Java API]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[VMware Virtual Disk Development Kit]]</text>
    <sha1>59b7a2285719d39aa19f6f22313dbf8e720b935b</sha1>
  </revision>
  <revision>
    <id>89</id>
    <parentid>66</parentid>
    <timestamp>2008-12-08T19:10:32Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="107" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[VMware Virtual Disk Development Kit]]</text>
    <sha1>079bd351632be1ac5231855acbc446df18cb8feb</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>VMware Virtual Disk Development Kit</title>
  <ns>0</ns>
  <id>28</id>
  <revision>
    <id>67</id>
    <timestamp>2008-12-07T22:46:37Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Virtual Disk Development Kit ====  The Virtual Disk Development Kit is a collection of C libraries, code samples, utilities, and documentation to help you create or access VMware virt...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="253" xml:space="preserve">==== Virtual Disk Development Kit ====

The Virtual Disk Development Kit is a collection of C libraries, code samples, utilities, and documentation to help you create or access VMware virtual disk storage. 

http://www.vmware.com/support/developer/vddk/</text>
    <sha1>90180db6c6da2af425363e3398884a23563f308e</sha1>
  </revision>
  <revision>
    <id>68</id>
    <parentid>67</parentid>
    <timestamp>2008-12-07T22:47:25Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="271" xml:space="preserve">==== Virtual Disk Development Kit ====

The Virtual Disk Development Kit is a collection of C libraries, code samples, utilities, and documentation to help you create or access VMware virtual disk storage. 

http://www.vmware.com/support/developer/vddk/

[[Category:SDK]]</text>
    <sha1>5908a3ca59dcb1ca45926010ebada60d1e4d2a75</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>RTFM ESX 3.x Service Console Guide</title>
  <ns>0</ns>
  <id>30</id>
  <revision>
    <id>70</id>
    <timestamp>2008-12-07T22:56:31Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== ESX 3.x Service Console Guide ====  This is the guide for Service Console programming as assembled by Mike Laverick from RTFM. Useful only for ESX not ESXi as there is not console in ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="245" xml:space="preserve">==== ESX 3.x Service Console Guide ====

This is the guide for Service Console programming as assembled by Mike Laverick from RTFM.
Useful only for ESX not ESXi as there is not console in the thin version of ESX.

http://www.rtfm-ed.co.uk/?p=261</text>
    <sha1>646e365026a165255090d95d889a303d62c7bddc</sha1>
  </revision>
  <revision>
    <id>71</id>
    <parentid>70</parentid>
    <timestamp>2008-12-07T22:56:47Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="246" xml:space="preserve">==== ESX 3.x Service Console Guide ====

This is the guide for Service Console programming as assembled by Mike Laverick from RTFM.

Useful only for ESX not ESXi as there is not console in the thin version of ESX.

http://www.rtfm-ed.co.uk/?p=261</text>
    <sha1>32538fbcfd3b7691b1664e1f2c90cc4c353b28f7</sha1>
  </revision>
  <revision>
    <id>72</id>
    <parentid>71</parentid>
    <timestamp>2008-12-07T22:57:32Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="256" xml:space="preserve">==== ESX 3.x Service Console Guide ====

This is the guide for Service Console programming as assembled by Mike Laverick from RTFM Education.

Useful only for ESX not ESXi as there is not console in the thin version of ESX.

http://www.rtfm-ed.co.uk/?p=261</text>
    <sha1>3879be76f40677b0a510bf4e398fda2577c07c9f</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>ESX3i Remote CLI documentation</title>
  <ns>0</ns>
  <id>31</id>
  <revision>
    <id>74</id>
    <timestamp>2008-12-07T23:35:30Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== ESX3i Remove CLI documentation ====  The official documentation for using the RCLI interface  [http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_rcli.pdf VMware Remote Command...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="237" xml:space="preserve">==== ESX3i Remove CLI documentation ====

The official documentation for using the RCLI interface

[http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_rcli.pdf VMware Remote Command-Line Interface Installation and Reference Guide]</text>
    <sha1>9b112986a96c7aefdc4a10a3deb525d16af950d9</sha1>
  </revision>
  <revision>
    <id>75</id>
    <parentid>74</parentid>
    <timestamp>2008-12-07T23:36:08Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="249" xml:space="preserve">==== ESX3i Remove CLI documentation ====

The official documentation for using the RCLI interface for ESX3.5i

[http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_rcli.pdf VMware Remote Command-Line Interface Installation and Reference Guide]</text>
    <sha1>177c2b01bad8bddc7484106d30f505152dbd88c2</sha1>
  </revision>
  <revision>
    <id>76</id>
    <parentid>75</parentid>
    <timestamp>2008-12-07T23:36:26Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="249" xml:space="preserve">==== ESX3i Remote CLI documentation ====

The official documentation for using the RCLI interface for ESX3.5i

[http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_rcli.pdf VMware Remote Command-Line Interface Installation and Reference Guide]</text>
    <sha1>688fb0179238ccb7d60e4ed5d737cf2e8fdb24cd</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>77</id>
    <parentid>45</parentid>
    <timestamp>2008-12-08T05:19:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="241" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]</text>
    <sha1>e6cd130d5a757c722e01aa2fcafcbba1cadd770e</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Pyvmware</title>
  <ns>0</ns>
  <id>32</id>
  <revision>
    <id>78</id>
    <timestamp>2008-12-08T05:20:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: A python module that makes use of the vmware client sdk to control vmware instances.  NOTE: Currently beta with limited implemented methods. Enough to start, stop, and revert a VM.   http:...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="217" xml:space="preserve">A python module that makes use of the vmware client sdk to control vmware instances.

NOTE: Currently beta with limited implemented methods. Enough to start, stop, and revert a VM. 

http://code.google.com/p/pyvmware/</text>
    <sha1>f4c99c6d542ec7da1095b8af8398b0ab1290e4e9</sha1>
  </revision>
  <revision>
    <id>79</id>
    <parentid>78</parentid>
    <timestamp>2008-12-08T05:21:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="255" xml:space="preserve">A python module that makes use of the vmware client sdk to control vmware instances.

NOTE: Currently beta with limited implemented methods. Enough to start, stop, and revert a VM. 

http://code.google.com/p/pyvmware/

[[Category:SDK]] [[Category:python]]</text>
    <sha1>e57d6c93416d941706ca6e47fbee8d933b6c8c13</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>81</id>
    <timestamp>2008-12-08T17:31:53Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vmrun scripts ====  Scripts to execute to automate actions in your guest.  [[vmrun batch file execution]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="110" xml:space="preserve">==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]</text>
    <sha1>3a3c89529ed6511e692b612d609ad102ae25601a</sha1>
  </revision>
  <revision>
    <id>95</id>
    <parentid>81</parentid>
    <timestamp>2008-12-09T17:17:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="152" xml:space="preserve">==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]</text>
    <sha1>c68826f63cfaacc1b67b2ebf14c90bce5802814d</sha1>
  </revision>
  <revision>
    <id>102</id>
    <parentid>95</parentid>
    <timestamp>2008-12-10T20:34:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="406" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html ESX 2.3 scripting API users manual]

[[ESX3i Remote CLI documentation]]


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]</text>
    <sha1>1e24090ea52e41696915439a47dc6f94b54e2d41</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Help:Contents</title>
  <ns>12</ns>
  <id>34</id>
  <revision>
    <id>82</id>
    <timestamp>2008-12-08T17:40:18Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: The VI-Toolkit site is a place for all to contribute their knowledge for the greater good.  Anyone who visits this website is invited to make a contribution.  This page contains a few tips...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2064" xml:space="preserve">The VI-Toolkit site is a place for all to contribute their knowledge for the greater good.  Anyone who visits this website is invited to make a contribution.  This page contains a few tips for those who are new to the world of wikis.

Don't be afraid to have a go at something.  The worst that can happen is that someone else will either revert your contribution, or tidy it up to meet some standards of the site.

If you want to experiment with the wiki, then use the [[WikiPlayGround]] page.

==Getting started contributing content==

===Editing===
The wiki allows you to edit any page by clicking the 'edit' tab.

===Adding a new page===
To add a new page you need to find an existing page and place a link to a new page on that .

You can create a link using

&lt;pre&gt;
[[&lt;link name&gt;]]
&lt;/pre&gt;

When trying to link to an existing page, remember that the links are case sensitive, so ''VMWARE'' doesn't equal ''VMware''.

If the link name isn't descriptive enough, then you can make it more so by adding some more text:

&lt;pre&gt;
[[&lt;link name&gt;|&lt;description&gt;]]
&lt;/pre&gt;

Links that are blue already exist, while red ones are pages that haven't been created.  If you click on a red link, you are taken to the edit screen where you can start writing.

So when you add to the wiki, you first create a link to the page and then you add the page (not the other way around which is the normal way in most systems).

== More advanced things ==
=== using categories ===
Use categories to sort items. Put Category tags at the end of the page.

For example (again, without spaces)
&lt;pre&gt;
[[Category:&lt;some category&gt;]] [[Category:&lt;some other category&gt;]]
&lt;/pre&gt;

To mark that one category is a subcategory of another, click on the link to go to your category page, and in there edit the category page itself to add a 'category' tag to where it should point.

[http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet More details on the wiki style formatting used (cheatsheet) in wikipedia web sites.]


Remember to put your category at the bottom of the edited text.

[[Category: VI-Toolkit]]</text>
    <sha1>c3f8a3e55a3f9eebe7915a19e2474cb715af6550</sha1>
  </revision>
  <revision>
    <id>86</id>
    <parentid>82</parentid>
    <timestamp>2008-12-08T17:53:33Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2770" xml:space="preserve">The VI-Toolkit site is a place for all to contribute their knowledge for the greater good.  Anyone who visits this website is invited to make a contribution.  This page contains a few tips for those who are new to the world of wikis.

Don't be afraid to have a go at something.  The worst that can happen is that someone else will either revert your contribution, or tidy it up to meet some standards of the site.

If you want to experiment with the wiki, then use the [[WikiPlayGround]] page.

==Getting started contributing content==

===Editing===
The wiki allows you to edit any page by clicking the 'edit' link at the bottom of the page.

===Adding a new page===
To add a new page you need to find an existing page and place a link to a new page on that .

You can create a link using

&lt;pre&gt;
[[&lt;link name&gt;]]
&lt;/pre&gt;

When trying to link to an existing page, remember that the links are case sensitive, so ''VMWARE'' doesn't equal ''VMware''.

If the link name isn't descriptive enough, then you can make it more so by adding some more text:

&lt;pre&gt;
[[&lt;link name&gt;|&lt;description&gt;]]
&lt;/pre&gt;

Links that are blue already exist, while red ones are pages that haven't been created.  If you click on a red link, you are taken to the edit screen where you can start writing.

So when you add to the wiki, you first create a link to the page and then you add the page (not the other way around which is the normal way in most systems).

===Adding source code===
Formatting source code works by inserting a single space in front of the script:

 vmkfstools -i /vmfs/volumes/templates/gold-master.vmdk /vmfs/volumes/myVMFS/myOS.vmdk


===External links===
An external link looks like this, the link and description are separated by a single space character.
&lt;pre&gt;
[&lt;link name&gt; &lt;description&gt;]
&lt;/pre&gt;

[http://www.google.com The google site]

You can also just put the link there, the wiki software will automatically change it into a clickable link

http://www.google.com

===Adding lists===

# This is a numbered list
# with several items
# added to it

and here's a list with bullet items
* item 1
* item 2
* item 3

== More advanced things ==
=== using categories ===
Use categories to sort items. Put Category tags at the end of the page.

For example (again, without spaces)
&lt;pre&gt;
[[Category:&lt;some category&gt;]] [[Category:&lt;some other category&gt;]]
&lt;/pre&gt;

To mark that one category is a subcategory of another, click on the link to go to your category page, and in there edit the category page itself to add a 'category' tag to where it should point.

[http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet More details on the wiki style formatting used (cheatsheet) in wikipedia web sites.]


Remember to put your category at the bottom of the edited text.

[[Category: VI-Toolkit]]</text>
    <sha1>2b24ec6cf9d2296b48443fa96e013a1e8c39ec60</sha1>
  </revision>
  <revision>
    <id>87</id>
    <parentid>86</parentid>
    <timestamp>2008-12-08T17:54:23Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2770" xml:space="preserve">The VI-Toolkit site is a place for all to contribute their knowledge for the greater good.  Anyone who visits this website is invited to make a contribution.  This page contains a few tips for those who are new to the world of wikis.

Don't be afraid to have a go at something.  The worst that can happen is that someone else will either revert your contribution, or tidy it up to meet some standards of the site.

If you want to experiment with the wiki, then use the [[WikiPlayGround]] page.

==Getting started contributing content==

===Editing===
The wiki allows you to edit any page by clicking the 'edit' link at the bottom of the page.

===Adding a new page===
To add a new page you need to find an existing page and place a link to a new page on that .

You can create a link using

&lt;pre&gt;
[[&lt;link name&gt;]]
&lt;/pre&gt;

When trying to link to an existing page, remember that the links are case sensitive, so ''VMWARE'' doesn't equal ''VMware''.

If the link name isn't descriptive enough, then you can make it more so by adding some more text:

&lt;pre&gt;
[[&lt;link name&gt;|&lt;description&gt;]]
&lt;/pre&gt;

Links that are blue already exist, while red ones are pages that haven't been created.  If you click on a red link, you are taken to the edit screen where you can start writing.

So when you add to the wiki, you first create a link to the page and then you add the page (not the other way around which is the normal way in most systems).

===Adding source code===
Formatting source code works by inserting a single space in front of the source:

 vmkfstools -i /vmfs/volumes/templates/gold-master.vmdk /vmfs/volumes/myVMFS/myOS.vmdk


===External links===
An external link looks like this, the link and description are separated by a single space character.
&lt;pre&gt;
[&lt;link name&gt; &lt;description&gt;]
&lt;/pre&gt;

[http://www.google.com The google site]

You can also just put the link there, the wiki software will automatically change it into a clickable link

http://www.google.com

===Adding lists===

# This is a numbered list
# with several items
# added to it

and here's a list with bullet items
* item 1
* item 2
* item 3

== More advanced things ==
=== using categories ===
Use categories to sort items. Put Category tags at the end of the page.

For example (again, without spaces)
&lt;pre&gt;
[[Category:&lt;some category&gt;]] [[Category:&lt;some other category&gt;]]
&lt;/pre&gt;

To mark that one category is a subcategory of another, click on the link to go to your category page, and in there edit the category page itself to add a 'category' tag to where it should point.

[http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet More details on the wiki style formatting used (cheatsheet) in wikipedia web sites.]


Remember to put your category at the bottom of the edited text.

[[Category: VI-Toolkit]]</text>
    <sha1>7e6b4f923a2edaaf915c7d8490a904c7a6bd33bf</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>WikiPlayGround</title>
  <ns>0</ns>
  <id>35</id>
  <revision>
    <id>83</id>
    <timestamp>2008-12-08T17:43:20Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Wiki Playground ====  You are ''' welcome ''' to make any changes in here and test out how a wiki works. Click on the EDIT link at the bottom of the page to make changes or to have a ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="422" xml:space="preserve">==== Wiki Playground ====

You are ''' welcome ''' to make any changes in here and test out how a wiki works.
Click on the EDIT link at the bottom of the page to make changes or to have a look how this formatting works

#. This is a numbered list
#. with several items
#. added to it

and here's a list with bullet items
* item 1
* item 2
* item 3

An external link looks like this

[http://www.google.com The google site]</text>
    <sha1>dc26260b1ee57cde354f3d27e3628ebe73a450fb</sha1>
  </revision>
  <revision>
    <id>84</id>
    <parentid>83</parentid>
    <timestamp>2008-12-08T17:45:54Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="589" xml:space="preserve">==== Wiki Playground ====

You are ''' welcome ''' to make any changes in here and test out how a wiki works.
Click on the EDIT link at the bottom of the page to make changes or to have a look how this formatting works

# This is a numbered list
# with several items
# added to it

and here's a list with bullet items
* item 1
* item 2
* item 3

An external link looks like this

[http://www.google.com The google site]

Formatting source code works by inserting a single space in front of the script:

 vmkfstools -i /vmfs/volumes/templates/gold-master.vmdk /vmfs/volumes/myVMFS/myOS.vmdk</text>
    <sha1>89cade62e8fc834a7c58eafb848d0ffe2f4c9cac</sha1>
  </revision>
  <revision>
    <id>85</id>
    <parentid>84</parentid>
    <timestamp>2008-12-08T17:46:11Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="590" xml:space="preserve">==== Wiki Playground ====

You are ''' welcome ''' to make any changes in here and test out how a wiki works.

Click on the EDIT link at the bottom of the page to make changes or to have a look how this formatting works

# This is a numbered list
# with several items
# added to it

and here's a list with bullet items
* item 1
* item 2
* item 3

An external link looks like this

[http://www.google.com The google site]

Formatting source code works by inserting a single space in front of the script:

 vmkfstools -i /vmfs/volumes/templates/gold-master.vmdk /vmfs/volumes/myVMFS/myOS.vmdk</text>
    <sha1>667c86ee85bc62dfb169a60201019985296d2d0b</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Vmrun batch file execution</title>
  <ns>0</ns>
  <id>36</id>
  <revision>
    <id>88</id>
    <timestamp>2008-12-08T18:41:36Z</timestamp>
    <contributor>
      <username>Vmroyale</username>
      <id>4</id>
    </contributor>
    <comment>How to use vmrun to execute batch files in Windows Guests</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="397" xml:space="preserve">In order to use vmrun to run a batch file on a Windows guest, you can use RunProgramInGuest and explicity call cmd.exe with the /c switch.

 vmrun -T ws -gu USERNAME -gp PASSWORD runProgramInGuest "C:\Virtual Machines\WinXP2\WinXP2.vmx" %COMSPEC% "/c C:\batch.bat"

This command will issue %COMSPEC%, which is a pointer to cmd.exe, to run the batch file C:\batch.bat on the WinXP2 virtual machine.</text>
    <sha1>e7d79d6f95e75da96467d7b63b1010b149a86183</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Vitforjava</title>
  <ns>0</ns>
  <id>10</id>
  <revision>
    <id>91</id>
    <parentid>15</parentid>
    <timestamp>2008-12-08T19:13:02Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[VI Toolkit for Java]] moved to [[Vitforjava]]: Incorrectly put under official SDK (oops)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="366" xml:space="preserve">==== VI Toolkit for Java ====

The VI Toolkit for Java is a Java library that is patterned after the VI Perl Toolkit. Administrators and developers who like the ability to quickly create scripts with the perl toolkit but appreciate the depth of Java will love the VI Toolkit for Java. 

http://sourceforge.net/projects/vitforjava/

[[Category:SDK]] [[Category:Java]]</text>
    <sha1>d040307f53e75fbb1eddeefe9c497dc0cdb6d1c0</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>VI Toolkit for Java</title>
  <ns>0</ns>
  <id>37</id>
  <revision>
    <id>92</id>
    <timestamp>2008-12-08T19:13:02Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>[[VI Toolkit for Java]] moved to [[Vitforjava]]: Incorrectly put under official SDK (oops)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24" xml:space="preserve">#REDIRECT [[Vitforjava]]</text>
    <sha1>811214cb263d68eb0aab4008cd9bc45cd296ef26</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>VMware Infrastructure Java API</title>
  <ns>0</ns>
  <id>15</id>
  <revision>
    <id>94</id>
    <parentid>26</parentid>
    <timestamp>2008-12-08T19:18:39Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>added Steve Jin's I Java eclipse plugin announcement</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="506" xml:space="preserve">==== VMware Infrastructure Java API ====

The VMware Virtual Infrastructure Java API provides a set of libraries with full support of managed object model and utilities to manage and control VMware virtual machines and servers using the VMwware Virtual Infrastructure Web service interface. 

http://sourceforge.net/projects/vijava/

http://vijava.sourceforge.net/

[http://communities.vmware.com/thread/183407 Preview: VI Java Plug-in for Eclipse (open source project)]

[[Category:SDK]] [[Category:Java]]</text>
    <sha1>acd463d84ddbd9563aca72fd4a1d4784211ab36a</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Vmrun return all IPs for running VMs</title>
  <ns>0</ns>
  <id>38</id>
  <revision>
    <id>96</id>
    <timestamp>2008-12-09T17:21:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Return all IPs for running VMs ====  If you want to do this through vmrun on VMware Server 2, then you can do the following:   vmrun -T server -h https://myserver/sdk -u root -p passw...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="882" xml:space="preserve">==== Return all IPs for running VMs ====

If you want to do this through vmrun on VMware Server 2, then you can do the following:

 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd runProgramInGuest "[standard] test/Clone of SLES10sp1-64bit.vmx" /bin/sh "/sbin/ifconfig &gt; /tmp/ip-info.txt"
 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd copyFileFromGuestToHost "[standard] test/Clone of SLES10sp1-64bit.vmx" /tmp/ip-info.txt /host/path/ip-info.txt"
 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd deleteFileInGuest "[standard] test/Clone of SLES10sp1-64bit.vmx" /tmp/ip-info.txt

This will redirect the output of ifconfig to a file on the guest, then copy that file to the host. It also cleans up the file, just to be tidy.


See also:

http://communities.vmware.com/message/1087204#1087204</text>
    <sha1>b95076c36a509aa753f917b21dd14d68afd4acda</sha1>
  </revision>
  <revision>
    <id>97</id>
    <parentid>96</parentid>
    <timestamp>2008-12-09T17:22:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>tidied it up a little bit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="837" xml:space="preserve">==== Return all IPs for running VMs ====

If you want to do this through vmrun on VMware Server 2, then you can do the following:

 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd runProgramInGuest "[standard] test/SLES10sp1.vmx" /bin/sh "/sbin/ifconfig &gt; /tmp/ip-info.txt"
 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd copyFileFromGuestToHost "[standard] test/SLES10sp1.vmx" /tmp/ip-info.txt /host/path/ip-info.txt"
 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd deleteFileInGuest "[standard] test/SLES10sp1.vmx" /tmp/ip-info.txt

This will redirect the output of ifconfig to a file on the guest, then copy that file to the host. It also cleans up the file, just to be tidy.


See also:

http://communities.vmware.com/message/1087204#1087204</text>
    <sha1>14833dab8f666a689c885ce2a405c84d1ba6cc83</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>99</id>
    <timestamp>2008-12-09T18:03:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: [[iMKS Remote Console]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23" xml:space="preserve">[[iMKS Remote Console]]</text>
    <sha1>8b86416d4fc683a61e86845211f1d818af1af62d</sha1>
  </revision>
</page>
<page arvcontinue="20081207120818|51">
  <title>IMKS Remote Console</title>
  <ns>0</ns>
  <id>40</id>
  <revision>
    <id>100</id>
    <timestamp>2008-12-09T18:05:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Currently managing your VMware infrastructure is limited to windows only x86 clients. This project opens up the ability to manage your Virtual Machines using just about any operating syste...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="662" xml:space="preserve">Currently managing your VMware infrastructure is limited to windows only x86 clients. This project opens up the ability to manage your Virtual Machines using just about any operating system or processor infrastructure.

With iMKS installed as an ESXi "Helper VM" you can open Remote Consoles, attach CD media, and interact with VM's as if it were a real service console. The VMware RemoteCLI and latest RemoteMKS (from VMware Player 2 RC1) integrate to allow work on an ESXi box (Or VI3 / ESX 2.x / Server 1.x / RDP) from a PC / Mac / Linux / Solaris Desktop -- And it's all encrypted over port 443

[http://communities.vmware.com/blogs/dmilisic The iMKS Weblog]</text>
    <sha1>97158da5d351f2359604259dda89cee4228b6577</sha1>
  </revision>
  <revision>
    <id>101</id>
    <parentid>100</parentid>
    <timestamp>2008-12-09T18:08:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="691" xml:space="preserve">Currently managing your VMware infrastructure is limited to windows only x86 clients. This project opens up the ability to manage your Virtual Machines using just about any operating system or processor infrastructure.

With iMKS installed as an ESXi "Helper VM" you can open Remote Consoles, attach CD media, and interact with VM's as if it were a real service console. The VMware RemoteCLI and latest RemoteMKS (from VMware Player 2 RC1) integrate to allow work on an ESXi box (Or VI3 / ESX 2.x / Server 1.x / RDP) from a PC / Mac / Linux / Solaris Desktop -- And it's all encrypted over port 443

[http://communities.vmware.com/blogs/dmilisic The iMKS Weblog]

 [[Category:VM Management]]</text>
    <sha1>c5204b9b2aebc260cdbed6a01c2d12d51a3805db</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>VI-Toolkit:Community Portal</title>
  <ns>4</ns>
  <id>6</id>
  <revision>
    <id>103</id>
    <parentid>98</parentid>
    <timestamp>2008-12-10T20:35:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="412" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[.net]]

[[scripts]]

[[Projects]]</text>
    <sha1>e0c834efb0cbbdba168752d9480d7d21a825593d</sha1>
  </revision>
  <revision>
    <id>108</id>
    <parentid>103</parentid>
    <timestamp>2008-12-10T21:01:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="402" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]</text>
    <sha1>02de02d83ba611948d393cf28926a6abe85fd1d4</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>104</id>
    <parentid>102</parentid>
    <timestamp>2008-12-10T20:39:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="649" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html ESX 2.3 scripting API users manual]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]</text>
    <sha1>1bfecb61e3488313bb82e99e2f7a6e7975799a73</sha1>
  </revision>
  <revision>
    <id>109</id>
    <parentid>104</parentid>
    <timestamp>2008-12-10T21:03:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="712" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html ESX 2.3 scripting API users manual]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]</text>
    <sha1>55cb8b93116f83f9f0b9ab8f6718fa4bca28b09c</sha1>
  </revision>
  <revision>
    <id>118</id>
    <parentid>109</parentid>
    <timestamp>2008-12-11T16:38:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="831" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]</text>
    <sha1>4ac5bc50af14c8aa0eb42d4dc52cdf3dae09743e</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>VI Plugin</title>
  <ns>0</ns>
  <id>7</id>
  <revision>
    <id>105</id>
    <parentid>12</parentid>
    <timestamp>2008-12-10T20:50:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="364" xml:space="preserve">=== VI plugins ===

[[vip-svmotion]]

==== External links ====

Excellent article from David Davis about VI Plugins
* [http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1321254,00.html VMware VI Client plug-ins and how to manage them]

Andrew Kutz open source VI Plugin projects
* http://code.google.com/p/akutz/

and his blog
* http://akutz.wordpress.com/</text>
    <sha1>5d1dc2acd3e7f226fd5c4b82611db7e12da228de</sha1>
  </revision>
  <revision>
    <id>106</id>
    <parentid>105</parentid>
    <timestamp>2008-12-10T20:50:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="366" xml:space="preserve">=== VI plugins ===

[[vip-svmotion]]

==== External links ====

Excellent article from David Davis about VI Plugins
* [http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1321254,00.html VMware VI Client plug-ins and how to manage them]

Andrew Kutz's open source VI Plugin projects
* http://code.google.com/p/akutz/

and his blog
* http://akutz.wordpress.com/</text>
    <sha1>c952cccc3f1abc509f649245e00c98ebb60c1a3b</sha1>
  </revision>
  <revision>
    <id>119</id>
    <parentid>106</parentid>
    <timestamp>2008-12-11T19:11:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="501" xml:space="preserve">=== VI plugins ===

[[vip-svmotion]]

=== VMware documentation ===

[http://www.vmware.com/support/developer/vc-sdk/vcplugin-exp/index.html VMware VI Plugin documentation]

==== External links ====

Excellent article from David Davis about VI Plugins
* [http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1321254,00.html VMware VI Client plug-ins and how to manage them]

Andrew Kutz's open source VI Plugin projects
* http://code.google.com/p/akutz/

and his blog
* http://akutz.wordpress.com/</text>
    <sha1>4cc16c02b563d0955c8947b8c9aeedcf463f57c2</sha1>
  </revision>
  <revision>
    <id>120</id>
    <parentid>119</parentid>
    <timestamp>2008-12-11T21:50:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="564" xml:space="preserve">=== VI plugins ===

[[vip-svmotion]]

[http://communities.vmware.com/thread/126786 Add Port Groups]

=== VMware documentation ===

[http://www.vmware.com/support/developer/vc-sdk/vcplugin-exp/index.html VMware VI Plugin documentation]

==== External links ====

Excellent article from David Davis about VI Plugins
* [http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1321254,00.html VMware VI Client plug-ins and how to manage them]

Andrew Kutz's open source VI Plugin projects
* http://code.google.com/p/akutz/

and his blog
* http://akutz.wordpress.com/</text>
    <sha1>8e0b9d3696e9c16d5368c0f8125aa1d0bd0afe18</sha1>
  </revision>
  <revision>
    <id>121</id>
    <parentid>120</parentid>
    <timestamp>2008-12-11T21:51:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="680" xml:space="preserve">=== VI plugins ===
We could dub this the akutz page if it wasn't for the link to the official VMware VI plugin documentation below. ;)

[[vip-svmotion]]

[http://communities.vmware.com/thread/126786 Add Port Groups]

=== VMware documentation ===

[http://www.vmware.com/support/developer/vc-sdk/vcplugin-exp/index.html VMware VI Plugin documentation]

==== External links ====

Excellent article from David Davis about VI Plugins
* [http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1321254,00.html VMware VI Client plug-ins and how to manage them]

Andrew Kutz's open source VI Plugin projects
* http://code.google.com/p/akutz/

and his blog
* http://akutz.wordpress.com/</text>
    <sha1>c67118f186da733c31f2dca4827a05fb6c6b3141</sha1>
  </revision>
  <revision>
    <id>122</id>
    <parentid>121</parentid>
    <timestamp>2008-12-11T21:55:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="795" xml:space="preserve">=== VI plugins ===
We could dub this the akutz page if it wasn't for the link to the official VMware VI plugin documentation below. ;)

[[vip-svmotion]]

[http://communities.vmware.com/thread/126786 Add Port Groups]

=== VMware documentation ===

[http://www.vmware.com/support/developer/vc-sdk/vcplugin-exp/index.html VMware VI Plugin documentation]

[http://communities.vmware.com/docs/DOC-5881 Developing a Complete VI Client Plug-in with Tomcat and VI Java API]

==== External links ====

Excellent article from David Davis about VI Plugins
* [http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1321254,00.html VMware VI Client plug-ins and how to manage them]

Andrew Kutz's open source VI Plugin projects
* http://code.google.com/p/akutz/

and his blog
* http://akutz.wordpress.com/</text>
    <sha1>f7b28ff58deebd8b05f7fd3840c1080274c91b63</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>107</id>
    <parentid>58</parentid>
    <timestamp>2008-12-10T21:00:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="777" xml:space="preserve">Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://teckinfo.blogspot.com Virtu-Al blog]</text>
    <sha1>92e87aac0252bd90ebc61a7e243b338fa8982168</sha1>
  </revision>
  <revision>
    <id>151</id>
    <parentid>107</parentid>
    <timestamp>2008-12-13T09:50:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1004" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://teckinfo.blogspot.com Virtu-Al blog]

* [http://www.astroarch.com/ Edward Haletky's site]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]</text>
    <sha1>e82526acd97468fff61d7c5fb61b7b7b4c91b47a</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Build host vmware kernel modules</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>110</id>
    <timestamp>2008-12-10T21:34:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface.  Because of this it provides a much smoother end u...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2469" xml:space="preserve">The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

You must run the following script with root priviledges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm /etc/vmware/not_configured 


You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora systems:
 su -c "yum install kernel-devel"


After the manual compile your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko</text>
    <sha1>22e38aa9eff4af1b6581a32e5720f19221d4f631</sha1>
  </revision>
  <revision>
    <id>111</id>
    <parentid>110</parentid>
    <timestamp>2008-12-10T21:41:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>fixed typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2468" xml:space="preserve">The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm /etc/vmware/not_configured 


You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora systems:
 su -c "yum install kernel-devel"


After the manual compile your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko</text>
    <sha1>284999481644acd2a9ab37a21c245c414e6b5a5f</sha1>
  </revision>
  <revision>
    <id>112</id>
    <parentid>111</parentid>
    <timestamp>2008-12-10T21:43:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2484" xml:space="preserve">The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm /etc/vmware/not_configured 


You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"


After the manual compile your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko</text>
    <sha1>34a3ac0072dba6dd3657a71e7810a9df185080af</sha1>
  </revision>
  <revision>
    <id>113</id>
    <parentid>112</parentid>
    <timestamp>2008-12-11T09:24:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2485" xml:space="preserve">The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm /etc/vmware/not_configured 


You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"


After the manual compile your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko</text>
    <sha1>0798db797f32dafb94c47b659fd509a693f9a4f5</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>114</id>
    <parentid>77</parentid>
    <timestamp>2008-12-11T16:14:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="255" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]</text>
    <sha1>24640c55a1a29f22d67e2f9d2d111d6cf20ef31f</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Rexx/Vix</title>
  <ns>0</ns>
  <id>42</id>
  <revision>
    <id>115</id>
    <timestamp>2008-12-11T16:15:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Rexx/Vix ====  Rexx/Vix is a Rexx interface for the VMWare API (Vix). This interface allows a Rexx programmer to control VMWare Server and Virtual Machines running on VMWare Server.  ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="229" xml:space="preserve">==== Rexx/Vix ====

Rexx/Vix is a Rexx interface for the VMWare API (Vix). This interface allows a Rexx programmer to control VMWare Server and Virtual Machines running on VMWare Server. 

http://sourceforge.net/projects/rexxvix/</text>
    <sha1>bea34ee5f9752004036841c647400b274325dbd9</sha1>
  </revision>
  <revision>
    <id>116</id>
    <parentid>115</parentid>
    <timestamp>2008-12-11T16:17:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="295" xml:space="preserve">==== Rexx/Vix ====

Rexx/Vix is a Rexx interface for the VMWare API (Vix). This interface allows a Rexx programmer to control VMWare Server and Virtual Machines running on VMWare Server. 

NOTE: Currently alpha stage

http://sourceforge.net/projects/rexxvix/


[[Category:SDK]] [[Category:rexx]]</text>
    <sha1>179b0305da589f6adb0f1b04e22868e01b67ac37</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>117</id>
    <parentid>23</parentid>
    <timestamp>2008-12-11T16:28:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1011" xml:space="preserve">== VI Toolkit ==
'' December 11, 2008 ''

Welcome at our new site which will contain information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

Right now it is much closer to being a collection of hyperlinks to code found on the net.

This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil</text>
    <sha1>c198b99b9be68e6914a032899511aefcf4d8d126</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>SDK</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>123</id>
    <parentid>89</parentid>
    <timestamp>2008-12-13T06:56:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="118" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]</text>
    <sha1>d9453d5884b8951c5dbda18757c6292c4d081cf5</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>124</id>
    <timestamp>2008-12-13T07:18:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== The VI metashell ====  The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server. It can be invoked from the sh...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1783" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]]

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
[[vimsh: hostsvc/]]
[[vimsh: vmsvc/]]        
[[vimsh: csinfo]]
[[vimsh: help]]
[[vimsh: puload]]
[[vimsh: internalsvc/]]
[[vimsh: csls]]
[[vimsh: pinfo]]
[[vimsh: puse]]          
[[vimsh: proxysvc/]]
[[vimsh: argtype]]
[[vimsh: csuimport]]
[[vimsh: pload]]
[[vimsh: quit]]          
[[vimsh: solo/]]
[[vimsh: cls]]
[[vimsh: echo]]
[[vimsh: ploadpath]]
[[vimsh: sleep]]         
[[vimsh: vimsvc/]]
[[vimsh: csimport]]
[[vimsh: exit]]
[[vimsh: pls]]
[[vimsh: source]]</text>
    <sha1>1a71e47051cf7dc549c14b87d92652ea7afb8e14</sha1>
  </revision>
  <revision>
    <id>125</id>
    <parentid>124</parentid>
    <timestamp>2008-12-13T07:19:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added some formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1808" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]]

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)

 [[vimsh: hostsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: csinfo]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: internalsvc/]]
 [[vimsh: csls]]
 [[vimsh: pinfo]]
 [[vimsh: puse]]          
 [[vimsh: proxysvc/]]
 [[vimsh: argtype]]
 [[vimsh: csuimport]]
 [[vimsh: pload]]
 [[vimsh: quit]]          
 [[vimsh: solo/]]
 [[vimsh: cls]]
 [[vimsh: echo]]
 [[vimsh: ploadpath]]
 [[vimsh: sleep]]         
 [[vimsh: vimsvc/]]
 [[vimsh: csimport]]
 [[vimsh: exit]]
 [[vimsh: pls]]
 [[vimsh: source]]</text>
    <sha1>6cb97be927dbc30d40c1001ae23b05dd32354427</sha1>
  </revision>
  <revision>
    <id>126</id>
    <parentid>125</parentid>
    <timestamp>2008-12-13T07:26:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2375" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]]

==== List of commands ====

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)

 [[vimsh: hostsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: csinfo]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: internalsvc/]]
 [[vimsh: csls]]
 [[vimsh: pinfo]]
 [[vimsh: puse]]          
 [[vimsh: proxysvc/]]
 [[vimsh: argtype]]
 [[vimsh: csuimport]]
 [[vimsh: pload]]
 [[vimsh: quit]]          
 [[vimsh: solo/]]
 [[vimsh: cls]]
 [[vimsh: echo]]
 [[vimsh: ploadpath]]
 [[vimsh: sleep]]         
 [[vimsh: vimsvc/]]
 [[vimsh: csimport]]
 [[vimsh: exit]]
 [[vimsh: pls]]
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]</text>
    <sha1>9fd9b47bd18563c7a9c67ccffd15f70998102046</sha1>
  </revision>
  <revision>
    <id>127</id>
    <parentid>126</parentid>
    <timestamp>2008-12-13T07:29:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>more markup and info</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2573" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]]

==== List of commands ====

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated)

 [[vimsh: hostsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: csinfo]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: internalsvc/]]
 [[vimsh: csls]]
 [[vimsh: pinfo]]
 [[vimsh: puse]]          
 [[vimsh: proxysvc/]]
 [[vimsh: argtype]]
 [[vimsh: csuimport]]
 [[vimsh: pload]]
 [[vimsh: quit]]          
 [[vimsh: solo/]]
 [[vimsh: cls]]
 [[vimsh: echo]]
 [[vimsh: ploadpath]]
 [[vimsh: sleep]]         
 [[vimsh: vimsvc/]]
 [[vimsh: csimport]]
 [[vimsh: exit]]
 [[vimsh: pls]]
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]</text>
    <sha1>093849d2dba22386e5c8e71140b78d954795e24b</sha1>
  </revision>
  <revision>
    <id>129</id>
    <parentid>127</parentid>
    <timestamp>2008-12-13T07:46:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3106" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;

==== List of commands ====

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated)

 [[vimsh: hostsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: csinfo]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: internalsvc/]]
 [[vimsh: csls]]
 [[vimsh: pinfo]]
 [[vimsh: puse]]          
 [[vimsh: proxysvc/]]
 [[vimsh: argtype]]
 [[vimsh: csuimport]]
 [[vimsh: pload]]
 [[vimsh: quit]]          
 [[vimsh: solo/]]
 [[vimsh: cls]]
 [[vimsh: echo]]
 [[vimsh: ploadpath]]
 [[vimsh: sleep]]         
 [[vimsh: vimsvc/]]
 [[vimsh: csimport]]
 [[vimsh: exit]]
 [[vimsh: pls]]
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]</text>
    <sha1>17285edcfaef709c94e4416bfe5cfef7b87ba416</sha1>
  </revision>
  <revision>
    <id>130</id>
    <parentid>129</parentid>
    <timestamp>2008-12-13T07:46:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3136" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;

==== List of commands ====

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated)

 [[vimsh: hostsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: csinfo]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: internalsvc/]]
 [[vimsh: csls]]
 [[vimsh: pinfo]]
 [[vimsh: puse]]          
 [[vimsh: proxysvc/]]
 [[vimsh: argtype]]
 [[vimsh: csuimport]]
 [[vimsh: pload]]
 [[vimsh: quit]]          
 [[vimsh: solo/]]
 [[vimsh: cls]]
 [[vimsh: echo]]
 [[vimsh: ploadpath]]
 [[vimsh: sleep]]         
 [[vimsh: vimsvc/]]
 [[vimsh: csimport]]
 [[vimsh: exit]]
 [[vimsh: pls]]
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]</text>
    <sha1>c35d9e50648b1262f75f205b1805bd2983200431</sha1>
  </revision>
  <revision>
    <id>131</id>
    <parentid>130</parentid>
    <timestamp>2008-12-13T07:53:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3229" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;

==== List of commands ====

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated)

 [[vimsh: hostsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: csinfo]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: internalsvc/]]
 [[vimsh: csls]]
 [[vimsh: pinfo]]
 [[vimsh: puse]]          
 [[vimsh: proxysvc/]]
 [[vimsh: argtype]]
 [[vimsh: csuimport]]
 [[vimsh: pload]]
 [[vimsh: quit]]          
 [[vimsh: solo/]]
 [[vimsh: cls]]
 [[vimsh: echo]]
 [[vimsh: ploadpath]]
 [[vimsh: sleep]]         
 [[vimsh: vimsvc/]]
 [[vimsh: csimport]]
 [[vimsh: exit]]
 [[vimsh: pls]]
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]</text>
    <sha1>dd06a595ec7f0207bbc9d4f118660543fc864509</sha1>
  </revision>
  <revision>
    <id>134</id>
    <parentid>131</parentid>
    <timestamp>2008-12-13T08:16:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>humans like alphabetic order..</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3229" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?)

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;

==== List of commands ====

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated)

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]</text>
    <sha1>089de8166812d680ef05e97b2b116725c71d716d</sha1>
  </revision>
  <revision>
    <id>140</id>
    <parentid>134</parentid>
    <timestamp>2008-12-13T09:12:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3337" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;

==== List of commands ====

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated)

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]</text>
    <sha1>92f8c05bcdc09ca4871d0dfed264a0c6f513d874</sha1>
  </revision>
  <revision>
    <id>145</id>
    <parentid>140</parentid>
    <timestamp>2008-12-13T09:19:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3373" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can almost do anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;

==== List of commands ====

Following is a list of the availabled commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)
Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated)

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

[[Category: ESX]][[Category: SDK]]</text>
    <sha1>346b12915f15c13b3b02bab723750960d01389e2</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vmware-vim-cmd</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>128</id>
    <timestamp>2008-12-13T07:34:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vmware-vim-cmd ====  The command line version of the [[vimsh]] command. This can be used in your scripts and replaces the alternative   vimsh -n -e &lt;command&gt;  so now you can use:  vmw...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="245" xml:space="preserve">==== Vmware-vim-cmd ====

The command line version of the [[vimsh]] command.
This can be used in your scripts and replaces the alternative 
 vimsh -n -e &lt;command&gt;

so now you can use:
 vmware-vim-cmd &lt;command&gt;

[[Category: ESX]][[Category: SDK]]</text>
    <sha1>cd7a5382421155d1b4942c6407016a04d67e111f</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: hostsvc/</title>
  <ns>0</ns>
  <id>45</id>
  <revision>
    <id>132</id>
    <timestamp>2008-12-13T08:07:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page:   [/]$ hostsvc/  advopt/                    cpuinfo                             pci_add                     autostartmanager/    firewall_disable_ruleset      pci_remove                  d...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1855" xml:space="preserve">
 [/]$ hostsvc/
 advopt/                    cpuinfo                             pci_add                   
 autostartmanager/    firewall_disable_ruleset      pci_remove                
 datastore/                firewall_enable_ruleset      queryconnectioninfo       
 datastorebrowser/     hostconfig                        querydisabledmethods      
 firmware/                 hosthardware                    refresh_firewall          
 net/                         hostsummary                    refresh_services          
 rsrc/                        login                                 runtimeinfo               
 storage/                   logout                               set_hostid                
 summary/                maintenance_mode_enter   standby_mode_enter        
 vmotion/                  maintenance_mode_exit     standby_mode_exit         
 connect                    memoryinfo                       task_list        


 [[hostsvc/ advopt/]]
 [[hostsvc/ autostartmanager/]]
 [[hostsvc/ datastore/]]
 [[hostsvc/ datastorebrowser/]]
 [[hostsvc/ firmware/]]
 [[hostsvc/ net/]]
 [[hostsvc/ rsrc/]]
 [[hostsvc/ storage/]]
 [[hostsvc/ summary/]]
 [[hostsvc/ vmotion/]]
 [[hostsvc/ connect]]
 [[hostsvc/ cpuinfo]]
 [[hostsvc/ firewall_disable_ruleset]]
 [[hostsvc/ firewall_enable_ruleset]] 
 [[hostsvc/ hostconfig]]
 [[hostsvc/ hosthardware]]
 [[hostsvc/ hostsummary]]
 [[hostsvc/ login]]
 [[hostsvc/ logout
 [[hostsvc/ maintenance_mode_enter]]
 [[hostsvc/ maintenance_mode_exit]]
 [[hostsvc/ memoryinfo]]
 [[hostsvc/ pci_add]]
 [[hostsvc/ pci_remove]]
 [[hostsvc/ queryconnectioninfo]]
 [[hostsvc/ querydisabledmethods]]
 [[hostsvc/ refresh_firewall]]
 [[hostsvc/ refresh_services]] 
 [[hostsvc/ runtimeinfo]] 
 [[hostsvc/ set_hostid]] 
 [[hostsvc/ standby_mode_enter]] 
 [[hostsvc/ standby_mode_exit]] 
 [[hostsvc/ task_list]]</text>
    <sha1>edf645e9cdf6e891144018af257fb46264d852cd</sha1>
  </revision>
  <revision>
    <id>133</id>
    <parentid>132</parentid>
    <timestamp>2008-12-13T08:08:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>fix link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1856" xml:space="preserve"> [/]$ hostsvc/
 advopt/                    cpuinfo                             pci_add                   
 autostartmanager/    firewall_disable_ruleset      pci_remove                
 datastore/                firewall_enable_ruleset      queryconnectioninfo       
 datastorebrowser/     hostconfig                        querydisabledmethods      
 firmware/                 hosthardware                    refresh_firewall          
 net/                         hostsummary                    refresh_services          
 rsrc/                        login                                 runtimeinfo               
 storage/                   logout                               set_hostid                
 summary/                maintenance_mode_enter   standby_mode_enter        
 vmotion/                  maintenance_mode_exit     standby_mode_exit         
 connect                    memoryinfo                       task_list        


 [[hostsvc/ advopt/]]
 [[hostsvc/ autostartmanager/]]
 [[hostsvc/ datastore/]]
 [[hostsvc/ datastorebrowser/]]
 [[hostsvc/ firmware/]]
 [[hostsvc/ net/]]
 [[hostsvc/ rsrc/]]
 [[hostsvc/ storage/]]
 [[hostsvc/ summary/]]
 [[hostsvc/ vmotion/]]
 [[hostsvc/ connect]]
 [[hostsvc/ cpuinfo]]
 [[hostsvc/ firewall_disable_ruleset]]
 [[hostsvc/ firewall_enable_ruleset]] 
 [[hostsvc/ hostconfig]]
 [[hostsvc/ hosthardware]]
 [[hostsvc/ hostsummary]]
 [[hostsvc/ login]]
 [[hostsvc/ logout]]
 [[hostsvc/ maintenance_mode_enter]]
 [[hostsvc/ maintenance_mode_exit]]
 [[hostsvc/ memoryinfo]]
 [[hostsvc/ pci_add]]
 [[hostsvc/ pci_remove]]
 [[hostsvc/ queryconnectioninfo]]
 [[hostsvc/ querydisabledmethods]]
 [[hostsvc/ refresh_firewall]]
 [[hostsvc/ refresh_services]] 
 [[hostsvc/ runtimeinfo]] 
 [[hostsvc/ set_hostid]] 
 [[hostsvc/ standby_mode_enter]] 
 [[hostsvc/ standby_mode_exit]] 
 [[hostsvc/ task_list]]</text>
    <sha1>dccb5b08d6cebf3ab09e3200d3416efe82ae506d</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: vmsvc/</title>
  <ns>0</ns>
  <id>46</id>
  <revision>
    <id>135</id>
    <timestamp>2008-12-13T09:04:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page:  [/]$ vmsvc/  acquiremksticket          get.configoption              power.off                   connect                       get.datastores                 power.on                    c...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1677" xml:space="preserve"> [/]$ vmsvc/
 acquiremksticket          get.configoption              power.off                 
 connect                       get.datastores                 power.on                  
 convert.toTemplate      get.disabledmethods        power.reboot              
 convert.toVm               get.environment              power.reset               
 createdummyvm          get.filelayout                   power.shutdown            
 destroy                       get.guest                         power.suspend             
 device.connection         get.guestheartbeatStatus  reload                    
 device.connusbdev       get.managedentitystatus   setscreenres              
 device.disconnusbdev   get.networks                    snapshot.create           
 device.diskadd             get.runtime                      snapshot.get              
 device.diskaddexisting  get.snapshotinfo               snapshot.remove           
 device.diskremove       get.summary                    snapshot.removeall        
 device.getdevices         get.tasklist                       snapshot.revert           
 device.toolsSyncSet      getallvms                        snapshot.setoption        
 device.vmiadd              gethostconstraints            tools.cancelinstall       
 device.vmiremove         login                              tools.install             
 devices.createnic           logout                            tools.upgrade             
 get.capability                message                        unregister                
 get.config                     power.getstate                upgrade                   
 get.config.cpuidmask     power.hibernate</text>
    <sha1>ceb2037fc6f04c59cc8f5564205f04a1eca71193</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: solo/</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>136</id>
    <timestamp>2008-12-13T09:05:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page:  [/]$ solo/   connect          login             querycfgopt         registervm         environment   logout           querycfgoptdesc</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve"> [/]$ solo/ 
 connect          login             querycfgopt         registervm       
 environment   logout           querycfgoptdesc</text>
    <sha1>51b7b34fa768922e9dc93e0ce1676420e0b3bd81</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: internalsvc/</title>
  <ns>0</ns>
  <id>48</id>
  <revision>
    <id>137</id>
    <timestamp>2008-12-13T09:07:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page:  [/]$ internalsvc/  perfcount/              redirect_stderr           refresh_pnic              access_address      redirect_stdout           set_exception_variable    connect             ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="510" xml:space="preserve"> [/]$ internalsvc/
 perfcount/              redirect_stderr           refresh_pnic            
 access_address      redirect_stdout           set_exception_variable  
 connect                  refresh                      set_log_level           
 host_mode_lock     refresh_consolenic      shutdown                
 login                     refresh_datastores      throw_exception         
 loglist                    refresh_gateway         use_fds                 
 logout                   refresh_network</text>
    <sha1>82de3a22674315301a766195520963c2c1711862</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: proxysvc/</title>
  <ns>0</ns>
  <id>49</id>
  <revision>
    <id>138</id>
    <timestamp>2008-12-13T09:08:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page:  [/]$ proxysvc/     add_np_service   connect          logout           remove_service     add_tcp_service  login              port_info        service_list</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve"> [/]$ proxysvc/   
 add_np_service   connect          logout           remove_service   
 add_tcp_service  login              port_info        service_list</text>
    <sha1>45903121cb329220b1275a79805f574ffdc3a351</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: vimsvc/</title>
  <ns>0</ns>
  <id>50</id>
  <revision>
    <id>139</id>
    <timestamp>2008-12-13T09:09:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page:  [/]$ vimsvc/    auth/              login                    task_cancel         task_list           connect           logout                 task_description    license            propert...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="207" xml:space="preserve"> [/]$ vimsvc/  
 auth/              login                    task_cancel         task_list         
 connect           logout                 task_description  
 license            property_dump    task_info</text>
    <sha1>ce4c63bbff653b380ad38ebe6bfaed369051272b</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: ?</title>
  <ns>0</ns>
  <id>51</id>
  <revision>
    <id>141</id>
    <timestamp>2008-12-13T09:13:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: The online help.  Usage: ? &lt;command&gt;  Will print the available help for the selected command.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="93" xml:space="preserve">The online help.

Usage: ? &lt;command&gt;

Will print the available help for the selected command.</text>
    <sha1>58e43d2dae5fe45bf0cd14b5eaf9a77eaf0adefd</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: exit</title>
  <ns>0</ns>
  <id>52</id>
  <revision>
    <id>142</id>
    <timestamp>2008-12-13T09:13:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: [/]$ ? exit Usage: quit  Quit the shell.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="40" xml:space="preserve">[/]$ ? exit
Usage: quit

Quit the shell.</text>
    <sha1>32a7e6fff3418afab117700bbece57f127659a9d</sha1>
  </revision>
  <revision>
    <id>143</id>
    <parentid>142</parentid>
    <timestamp>2008-12-13T09:14:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="57" xml:space="preserve">==== vimsh exit command ====
Usage: quit

Quit the shell.</text>
    <sha1>894c75ae0d4a7430144d4bf2d0a0a28025dd4e87</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Hostsvc/maintenance mode enter</title>
  <ns>0</ns>
  <id>53</id>
  <revision>
    <id>144</id>
    <timestamp>2008-12-13T09:18:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Hostsvc/maintenance_mode_enter ==== Usage: maintenance_mode_enter [timeout]  Put the host in maintenace mode.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="114" xml:space="preserve">==== Hostsvc/maintenance_mode_enter ====
Usage: maintenance_mode_enter [timeout]

Put the host in maintenace mode.</text>
    <sha1>f4f8df27ef0b29137d3861350af4f8752d378c43</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: source</title>
  <ns>0</ns>
  <id>54</id>
  <revision>
    <id>146</id>
    <timestamp>2008-12-13T09:29:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh source command ====  Usage: source filename  Load commands defined in file filename.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="95" xml:space="preserve">==== vimsh source command ====

Usage: source filename

Load commands defined in file filename.</text>
    <sha1>182314298ffeb6e0bac5b79ba527f74232ef3a05</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vimsh: sleep</title>
  <ns>0</ns>
  <id>55</id>
  <revision>
    <id>147</id>
    <timestamp>2008-12-13T09:29:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh sleep command ==== Usage: sleep [time in seconds]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="60" xml:space="preserve">==== vimsh sleep command ====
Usage: sleep [time in seconds]</text>
    <sha1>0e4f4b5551704dd0839b677eb4f7e4e4681413f5</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>VI-Toolkit:About</title>
  <ns>4</ns>
  <id>4</id>
  <revision>
    <id>148</id>
    <parentid>5</parentid>
    <timestamp>2008-12-13T09:35:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>things are starting to fall into place...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="966" xml:space="preserve">==== About ====

This site is created in order to be able to store knowledge about Virtual Infrastructure and related VMware products.

At start, the site this will contain lots of links to information on the internet and have general information about how-to solve particular problems, but over time the intention is to move the focus slightly over to managing your Virtual Infrastructure using the toolkits available from VMware.

There are many ways in which you can manage your Virtual environment and it is intended that the way in which you can do this is documented on this site.

The site is initiated by [http://communities.vmware.com/people/wila Wil van Antwerpen] but everyone is welcome to add his or her notes and/or ideas.

Hopefully this site will contribute to the general knowledge on managing your Virtualisation journey and help out on enjoying this journey as much as I do.

Below is a list of things completed for our site:
[[Vitoolkit: Status]]</text>
    <sha1>0e1ee493f110d78f8190c03fd53918c1c9d6e793</sha1>
  </revision>
</page>
<page arvcontinue="20081210203507|103">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>149</id>
    <timestamp>2008-12-13T09:42:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Status site ====  December 5, 2008: Initial setup  December 13, 2008: This page :)   ==== Things to do ====  Here's a list of things still to do, there's no time line as I don't want ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="732" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: This page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

- Add daily backup to another machine
- Add proper category pages
- Add "what's new" to the main page
- Add # of articles/pages to the main page

- Fix css for code snippets, it doesn't look like the current font is monospaced
- Fix theme template / settings so that we can edit per paragraph as well

- Find a better way to present what's available on the site
- Improve main page
- Add example code</text>
    <sha1>bd526a04d91a54761a26bb2fd38d3804a8c8266c</sha1>
  </revision>
  <revision>
    <id>150</id>
    <parentid>149</parentid>
    <timestamp>2008-12-13T09:43:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="770" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: This page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages
* Add "what's new" to the main page
* Add # of articles/pages to the main page

* Fix css for code snippets, it doesn't look like the current font is monospaced
* Fix theme template / settings so that we can edit per paragraph as well

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code</text>
    <sha1>b327b5e745ccb6d5d57d91f0f7c1e46360ccfc93</sha1>
  </revision>
  <revision>
    <id>152</id>
    <parentid>150</parentid>
    <timestamp>2008-12-13T10:25:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1185" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: This page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages
* Add "what's new" to the main page
* Add # of articles/pages to the main page

* Fix css for code snippets, it doesn't look like the current font is monospaced
* Fix theme template / settings so that we can edit per paragraph as well

* Do email notifications work? (I think not)

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion])
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] My impression is that at this stage it´s a bit over the top.</text>
    <sha1>24c1a837c21cb1bde83b300af67ea46a396466c3</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>153</id>
    <parentid>152</parentid>
    <timestamp>2008-12-13T10:27:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1333" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: This page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages
* Add "what's new" to the main page
* Add # of articles/pages to the main page

* Fix css for code snippets, it doesn't look like the current font is monospaced
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect

* Do email notifications work? (I think not)

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?</text>
    <sha1>10c029f341e755bcf1320f41d44e1a87a6343c62</sha1>
  </revision>
  <revision>
    <id>154</id>
    <parentid>153</parentid>
    <timestamp>2008-12-13T10:30:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1452" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: This page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages
* Add "what's new" to the main page
* Add # of articles/pages to the main page

* Fix css for code snippets, it doesn't look like the current font is monospaced
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)
* Do email notifications work? (I think not)

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?</text>
    <sha1>14f1cf0c92106a70b152738481b828ca38430710</sha1>
  </revision>
  <revision>
    <id>156</id>
    <parentid>154</parentid>
    <timestamp>2008-12-13T12:21:02Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1482" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages
* Add "what's new" to the main page
* Add # of articles/pages to the main page

* Fix css for code snippets, it doesn't look like the current font is monospaced
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)
* Do email notifications work? (I think not)

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?</text>
    <sha1>3c76694cbf93a2d0b140ff21d1dea5b2efee7bbd</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>VI-Toolkit:About</title>
  <ns>4</ns>
  <id>4</id>
  <revision>
    <id>155</id>
    <parentid>148</parentid>
    <timestamp>2008-12-13T12:19:51Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1094" xml:space="preserve">==== About ====

This site is created in order to be able to store knowledge about Virtual Infrastructure and related VMware products.

At start, the site this will contain lots of links to information on the internet and have general information about how-to solve particular problems, but over time the intention is to move the focus slightly over to managing your Virtual Infrastructure using the toolkits available from VMware.

There are many ways in which you can manage your Virtual environment and it is intended that the way in which you can do this is documented on this site.

The site is initiated by [http://communities.vmware.com/people/wila Wil van Antwerpen] but everyone is welcome to add his or her notes and/or ideas. If you want to contact me then do so via my profile above or send me an email to wila at .... the domain name of the site here.

Hopefully this site will contribute to the general knowledge on managing your Virtualisation journey and help out on enjoying this journey as much as I do.

Below is a list of things completed for our site:
[[Vitoolkit: Status]]</text>
    <sha1>35592417a5245bc27fca5b2e7df2bb9e3d7d8997</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Java</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>157</id>
    <parentid>46</parentid>
    <timestamp>2008-12-13T20:27:49Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="58" xml:space="preserve">[[VmWare commander for Java]]

[[Live View]]

[[vMonitor]]</text>
    <sha1>1e02ba3f9c06c4044760dfb720cde9491bfd1967</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>VMonitor</title>
  <ns>0</ns>
  <id>57</id>
  <revision>
    <id>158</id>
    <timestamp>2008-12-13T20:28:26Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vMonitor ====  vMonitor is a system tray application that monitors the status of a virtualization solution. Currently vMonitor is supported on Microsoft Windows, OS X, Gnome, and KDE ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="269" xml:space="preserve">==== vMonitor ====

vMonitor is a system tray application that monitors the status of a virtualization solution. Currently vMonitor is supported on Microsoft Windows, OS X, Gnome, and KDE for monitoring VMware Infrastructure. 

http://sourceforge.net/projects/vmonitor/</text>
    <sha1>16c7c5df51e4c0785d363dab59aa807f3dfeed40</sha1>
  </revision>
  <revision>
    <id>161</id>
    <parentid>158</parentid>
    <timestamp>2008-12-13T21:04:37Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="317" xml:space="preserve">==== vMonitor ====

vMonitor is a system tray application that monitors the status of a virtualization solution. Currently vMonitor is supported on Microsoft Windows, OS X, Gnome, and KDE for monitoring VMware Infrastructure. 

http://sourceforge.net/projects/vmonitor/

 [[Category:VM Management]]  [[Category:Java]]</text>
    <sha1>f65f048e11ea4c2ceb99e4e8e6fc6a8861efbc8b</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>159</id>
    <parentid>99</parentid>
    <timestamp>2008-12-13T20:31:10Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="33" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]</text>
    <sha1>cc1f4cd02e3241149ec9260782e5c315aa8e0fd7</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>VMGL</title>
  <ns>0</ns>
  <id>58</id>
  <revision>
    <id>160</id>
    <timestamp>2008-12-13T20:31:20Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== VMGL ====  OpenGL apps running inside a VM use VMGL to obtain graphics hardware acceleration. VMGL supports VMware, Xen PV and HVM, qemu, and KVM VMs; X11-based OS such as Linux, Free...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="280" xml:space="preserve">==== VMGL ====

OpenGL apps running inside a VM use VMGL to obtain graphics hardware acceleration. VMGL supports VMware, Xen PV and HVM, qemu, and KVM VMs; X11-based OS such as Linux, FreeBSD and OpenSolaris; and ATI, Nvidia and Intel GPUs. 

http://sourceforge.net/projects/vmgl/</text>
    <sha1>ff5dd055063320ec9d75d01bea5648890f30b455</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: argtype</title>
  <ns>0</ns>
  <id>59</id>
  <revision>
    <id>162</id>
    <timestamp>2008-12-14T08:50:03Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh argtype command ====  Usage: argtype  Lists the registered argument types.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="85" xml:space="preserve">==== vimsh argtype command ====

Usage: argtype

Lists the registered argument types.</text>
    <sha1>da394ae18a49fb0a900314d894614c5b0058ed13</sha1>
  </revision>
  <revision>
    <id>193</id>
    <parentid>162</parentid>
    <timestamp>2008-12-14T09:23:52Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="106" xml:space="preserve">==== vimsh argtype command ====

Usage: argtype

Lists the registered argument types.

[[Category: Vimsh]]</text>
    <sha1>77693a1bcc2c5b25c7641ac6ad10d213efeba822</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: cls</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>163</id>
    <timestamp>2008-12-14T08:51:33Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh cls command ==== Usage: cls [folder]  List commands in a folder.  By convention folders contain a trailing slash and will be listed first.  Does not recursively list folders. Wh...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="326" xml:space="preserve">==== vimsh cls command ====
Usage: cls [folder]

List commands in a folder.  By convention folders contain a trailing
slash and will be listed first.  Does not recursively list folders.
When used with no arguments, lists the commands in the root folder.

See 'csinfo commands' for more information about the command namespace.</text>
    <sha1>1927e1423b3aa26ee03e2c400a828b782e9cbb8c</sha1>
  </revision>
  <revision>
    <id>169</id>
    <parentid>163</parentid>
    <timestamp>2008-12-14T08:57:55Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="330" xml:space="preserve">==== vimsh cls command ====
Usage: cls [folder]

List commands in a folder.  By convention folders contain a trailing
slash and will be listed first.  Does not recursively list folders.
When used with no arguments, lists the commands in the root folder.

See '[[csinfo]] commands' for more information about the command namespace.</text>
    <sha1>a65ef6826596e525f73ec0af3a7b4331bc155c1d</sha1>
  </revision>
  <revision>
    <id>170</id>
    <parentid>169</parentid>
    <timestamp>2008-12-14T08:59:18Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="346" xml:space="preserve">==== vimsh cls command ====
Usage: cls [folder]

List commands in a folder.  By convention folders contain a trailing
slash and will be listed first.  Does not recursively list folders.
When used with no arguments, lists the commands in the root folder.

See '[[Vimsh: csinfo | csinfo commands]]' for more information about the command namespace.</text>
    <sha1>7f1eb853ae101106a9bee6aa4d2c5ae6dd8d3a89</sha1>
  </revision>
  <revision>
    <id>194</id>
    <parentid>170</parentid>
    <timestamp>2008-12-14T09:24:14Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="367" xml:space="preserve">==== vimsh cls command ====
Usage: cls [folder]

List commands in a folder.  By convention folders contain a trailing
slash and will be listed first.  Does not recursively list folders.
When used with no arguments, lists the commands in the root folder.

See '[[Vimsh: csinfo | csinfo commands]]' for more information about the command namespace.

[[Category: Vimsh]]</text>
    <sha1>e0c6da9f2bd5d19465771a6e2baf2858f9c2ab96</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: csimport</title>
  <ns>0</ns>
  <id>61</id>
  <revision>
    <id>164</id>
    <timestamp>2008-12-14T08:52:35Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh csimport command ==== Usage: csimport [commandset] [folder]  Imports a command set at a specific location in the namespace.  If the folder location is not specified, imports the...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="390" xml:space="preserve">==== vimsh csimport command ====
Usage: csimport [commandset] [folder]

Imports a command set at a specific location in the namespace.  If the
folder location is not specified, imports the command set in the default
folder for that command set.  If no arguments are specified, the command
displays the current set of imports.

See 'csinfo plugin' and 'csinfo commands' for more information.</text>
    <sha1>c82a889e3138df8320b4687ad662522bcfecd34e</sha1>
  </revision>
  <revision>
    <id>195</id>
    <parentid>164</parentid>
    <timestamp>2008-12-14T09:24:55Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="429" xml:space="preserve">==== vimsh csimport command ====
Usage: csimport [commandset] [folder]

Imports a command set at a specific location in the namespace.  If the
folder location is not specified, imports the command set in the default
folder for that command set.  If no arguments are specified, the command
displays the current set of imports.

See '[[Vimsh: csinfo|csinfo plugin]]' and 'csinfo commands' for more information.

[[Category: Vimsh]]</text>
    <sha1>625a6da9125c72d107cdfb7a5f0e0f8e06464507</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: csinfo</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>165</id>
    <timestamp>2008-12-14T08:53:31Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh csinfo command ==== Usage: csinfo commandset  Displays information about a command set.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="98" xml:space="preserve">==== vimsh csinfo command ====
Usage: csinfo commandset

Displays information about a command set.</text>
    <sha1>c773b3f8f9264165b9241495524efb8601337d58</sha1>
  </revision>
  <revision>
    <id>168</id>
    <parentid>165</parentid>
    <timestamp>2008-12-14T08:56:44Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1629" xml:space="preserve">==== vimsh csinfo command ====
Usage: csinfo commandset

Displays information about a command set.


[/]$ csinfo plugin

Plugin commands

A plugin is a dynamic module that provides additional commands that can be
used to extend the capabilities of the shell.  A plugin is loaded by using
either puse or pload and specifying the file path of the plugin.  The file
path can be specified by an absolute path.  Relative paths may be used if a
list of search paths is provided using the ploadpath command.  A plugin is
named.  The names of loaded plugins can be determined using the pls command.
Plugins can be unloaded using the name.

The commands provided by a plugin are grouped into one or more command sets.
Each command set represents a logical grouping of commands that can be added
to the shell.  Like plugins, a command set is also named.  This name is used
for operations to manage command sets.  The list of available command sets
and the commands in each command set can be found using csls.

To add commands to the shell, use csimport to import a command set at a
particular place in the command namespace.  Each command set contains a
default location in the namespace, so no import point needs to be specified.
Command sets may be imported into existing command namespace folders so long
as the command names in the command set do not conflict with a name already
in the folder.  A command namespace folder is defined when commands exist
under the namespace and undefined when no commands exist.

The default import folder is '/'.

For more information about this command set:
  use 'csls plugin' to list its commands.</text>
    <sha1>a224d9dc7d46b4ac71b64e488beca4d79461e6f6</sha1>
  </revision>
  <revision>
    <id>173</id>
    <parentid>168</parentid>
    <timestamp>2008-12-14T09:02:52Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1645" xml:space="preserve">==== vimsh csinfo command ====
Usage: csinfo commandset

Displays information about a command set.


[/]$ csinfo plugin

Plugin commands

A plugin is a dynamic module that provides additional commands that can be
used to extend the capabilities of the shell.  A plugin is loaded by using
either puse or pload and specifying the file path of the plugin.  The file
path can be specified by an absolute path.  Relative paths may be used if a
list of search paths is provided using the ploadpath command.  A plugin is
named.  The names of loaded plugins can be determined using the pls command.
Plugins can be unloaded using the name.

The commands provided by a plugin are grouped into one or more command sets.
Each command set represents a logical grouping of commands that can be added
to the shell.  Like plugins, a command set is also named.  This name is used
for operations to manage command sets.  The list of available command sets
and the commands in each command set can be found using csls.

To add commands to the shell, use csimport to import a command set at a
particular place in the command namespace.  Each command set contains a
default location in the namespace, so no import point needs to be specified.
Command sets may be imported into existing command namespace folders so long
as the command names in the command set do not conflict with a name already
in the folder.  A command namespace folder is defined when commands exist
under the namespace and undefined when no commands exist.

The default import folder is '/'.

For more information about this command set:
  use '[[Vimsh: csls|csls plugin]]' to list its commands.</text>
    <sha1>8610c7e15173869a646e5fe34a31084bc7aba5d4</sha1>
  </revision>
  <revision>
    <id>196</id>
    <parentid>173</parentid>
    <timestamp>2008-12-14T09:25:24Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1666" xml:space="preserve">==== vimsh csinfo command ====
Usage: csinfo commandset

Displays information about a command set.


[/]$ csinfo plugin

Plugin commands

A plugin is a dynamic module that provides additional commands that can be
used to extend the capabilities of the shell.  A plugin is loaded by using
either puse or pload and specifying the file path of the plugin.  The file
path can be specified by an absolute path.  Relative paths may be used if a
list of search paths is provided using the ploadpath command.  A plugin is
named.  The names of loaded plugins can be determined using the pls command.
Plugins can be unloaded using the name.

The commands provided by a plugin are grouped into one or more command sets.
Each command set represents a logical grouping of commands that can be added
to the shell.  Like plugins, a command set is also named.  This name is used
for operations to manage command sets.  The list of available command sets
and the commands in each command set can be found using csls.

To add commands to the shell, use csimport to import a command set at a
particular place in the command namespace.  Each command set contains a
default location in the namespace, so no import point needs to be specified.
Command sets may be imported into existing command namespace folders so long
as the command names in the command set do not conflict with a name already
in the folder.  A command namespace folder is defined when commands exist
under the namespace and undefined when no commands exist.

The default import folder is '/'.

For more information about this command set:
  use '[[Vimsh: csls|csls plugin]]' to list its commands.

[[Category: Vimsh]]</text>
    <sha1>3c5386443f26634c0e36e505cd8f615dc81b22fe</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: csls</title>
  <ns>0</ns>
  <id>63</id>
  <revision>
    <id>166</id>
    <timestamp>2008-12-14T08:54:18Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh csls command ==== Usage: csls [commandset]  List the name of the command sets that are currently available.  When a command set name is specified, lists commands in the command ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="192" xml:space="preserve">==== vimsh csls command ====
Usage: csls [commandset]

List the name of the command sets that are currently available.  When a
command set name is specified, lists commands in the command set.</text>
    <sha1>584746b32e89a54306e08dfddc37de5607df1b54</sha1>
  </revision>
  <revision>
    <id>171</id>
    <parentid>166</parentid>
    <timestamp>2008-12-14T09:01:08Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="269" xml:space="preserve">==== vimsh csls command ====
Usage: csls [commandset]

List the name of the command sets that are currently available.  When a
command set name is specified, lists commands in the command set.

[/]$ csls plugin
pinfo      puse       pload      puload     ploadpath  pls</text>
    <sha1>48a25f89d5241ad54050ce33500e6c2f909620f0</sha1>
  </revision>
  <revision>
    <id>172</id>
    <parentid>171</parentid>
    <timestamp>2008-12-14T09:01:30Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="273" xml:space="preserve">==== vimsh csls command ====
Usage: csls [commandset]

List the name of the command sets that are currently available.  When a
command set name is specified, lists commands in the command set.

 [/]$ csls plugin
 
 pinfo      puse       pload      puload     ploadpath  pls</text>
    <sha1>48ec84963f71d396f9388335c81d20c1eaa538da</sha1>
  </revision>
  <revision>
    <id>197</id>
    <parentid>172</parentid>
    <timestamp>2008-12-14T09:25:47Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="294" xml:space="preserve">==== vimsh csls command ====
Usage: csls [commandset]

List the name of the command sets that are currently available.  When a
command set name is specified, lists commands in the command set.

 [/]$ csls plugin
 
 pinfo      puse       pload      puload     ploadpath  pls

[[Category: Vimsh]]</text>
    <sha1>9d2ddafe6bf56e8b367b1b893f01b063065a7d47</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: csuimport</title>
  <ns>0</ns>
  <id>64</id>
  <revision>
    <id>167</id>
    <timestamp>2008-12-14T08:55:18Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh csuimport command ==== Usage: csuimport commandset [folder]  Unimports a command set from a specific location in the namespace.  If the folder is not specified, uimports the com...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="305" xml:space="preserve">==== vimsh csuimport command ====
Usage: csuimport commandset [folder]

Unimports a command set from a specific location in the namespace.  If the
folder is not specified, uimports the command set in the default folder for
that command set.

See 'csinfo plugin' and 'csinfo commands' for more information.</text>
    <sha1>7a9667177cb487df8be7a5c2c5ab18ed8880906f</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: echo</title>
  <ns>0</ns>
  <id>65</id>
  <revision>
    <id>174</id>
    <timestamp>2008-12-14T09:06:13Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh: echo command ==== Usage: echo [-n] [string] [string2] ...  Options:   -n            Don't print a newline.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="118" xml:space="preserve">==== vimsh: echo command ====
Usage: echo [-n] [string] [string2] ...

Options:
  -n            Don't print a newline.</text>
    <sha1>4c655182836b2a407fc2631a0697ed86ab5d3969</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: help</title>
  <ns>0</ns>
  <id>66</id>
  <revision>
    <id>175</id>
    <timestamp>2008-12-14T09:08:25Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh help command ==== Usage: help [command]  Print help for commands.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="76" xml:space="preserve">==== Vimsh help command ====
Usage: help [command]

Print help for commands.</text>
    <sha1>2eb1cb500c3a8653cff1ec1b8d0d7450a5d07e74</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: puload</title>
  <ns>0</ns>
  <id>67</id>
  <revision>
    <id>176</id>
    <timestamp>2008-12-14T09:09:26Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh puload command ==== Usage: puload [-f] plugin  Unloads a plugin specified using the plugin name.  Options:   -f            Unimport all command sets for this plugin.  See '[[Vim...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="257" xml:space="preserve">==== vimsh puload command ====
Usage: puload [-f] plugin

Unloads a plugin specified using the plugin name.

Options:
  -f            Unimport all command sets for this plugin.

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.</text>
    <sha1>63c52d099e6d2d4964bdfe0bf3856f6148bb2f39</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: pinfo</title>
  <ns>0</ns>
  <id>68</id>
  <revision>
    <id>177</id>
    <timestamp>2008-12-14T09:10:20Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh: pinfo command ==== Usage: pinfo plugin  Displays information about a plugin.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="88" xml:space="preserve">==== Vimsh: pinfo command ====
Usage: pinfo plugin

Displays information about a plugin.</text>
    <sha1>21f776484c878c52fe177e8f8600a1769da1a832</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: pload</title>
  <ns>0</ns>
  <id>69</id>
  <revision>
    <id>178</id>
    <timestamp>2008-12-14T09:11:24Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh pload command ==== Usage: pload filepath  Loads a plugin specified in file name.  See '[[Vims: csinfo|csinfo plugin]]' for more information about using plugins.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="171" xml:space="preserve">==== vimsh pload command ====
Usage: pload filepath

Loads a plugin specified in file name.

See '[[Vims: csinfo|csinfo plugin]]' for more information about using plugins.</text>
    <sha1>6ca1ad5bdf04dec78bd9ac4f5db69b467cbb0e5a</sha1>
  </revision>
  <revision>
    <id>179</id>
    <parentid>178</parentid>
    <timestamp>2008-12-14T09:11:37Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">==== vimsh pload command ====
Usage: pload filepath

Loads a plugin specified in file name.

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.</text>
    <sha1>696121c7101520652a2c5e41be307ebe3e4103eb</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: ploadpath</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>180</id>
    <timestamp>2008-12-14T09:14:03Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh ploadpath command ==== Usage: ploadpath [-u] [filepath] [filepath2] ...  Specifies search path for locating plugins.  Multiple paths may be specified. Invoking command with no s...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="374" xml:space="preserve">==== Vimsh ploadpath command ====
Usage: ploadpath [-u] [filepath] [filepath2] ...

Specifies search path for locating plugins.  Multiple paths may be specified.
Invoking command with no search paths prints out current plugin search path.

Options:
  -u            Undefine plugin search path.

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.</text>
    <sha1>24d80d2d0047539fc80f12feb31cc18112e99c4d</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: pls</title>
  <ns>0</ns>
  <id>71</id>
  <revision>
    <id>181</id>
    <timestamp>2008-12-14T09:14:54Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh: pls command ==== Usage: pls [-s] [plugin]  List the name of the plugins that are currently loaded.  When a plugin name is specified, lists the commands or command sets provided...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="391" xml:space="preserve">==== Vimsh: pls command ====
Usage: pls [-s] [plugin]

List the name of the plugins that are currently loaded.  When a plugin name
is specified, lists the commands or command sets provided by the plugin.

Options:
  -s            List command sets for this plugin.  Default is to list
                commands.

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.</text>
    <sha1>cb6f1fc98e71ac71218f687ca23e883b138d9a27</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: puse</title>
  <ns>0</ns>
  <id>72</id>
  <revision>
    <id>182</id>
    <timestamp>2008-12-14T09:15:49Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh puse command ==== Usage: puse filepath  Loads a plugin specified by filepath and imports command sets in default location.  See '[[Vimsh: csinfo|csinfo plugin]]' for more inform...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="214" xml:space="preserve">==== Vimsh puse command ====
Usage: puse filepath

Loads a plugin specified by filepath and imports command sets in default
location.  See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.</text>
    <sha1>c3f57e3cc019722635feb9d3849b078054834880</sha1>
  </revision>
  <revision>
    <id>183</id>
    <parentid>182</parentid>
    <timestamp>2008-12-14T09:16:02Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="216" xml:space="preserve">==== Vimsh puse command ====
Usage: puse filepath

Loads a plugin specified by filepath and imports command sets in default
location.  

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.</text>
    <sha1>9316ca5c6b7a66215134b47f031e3af550e884e4</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: quit</title>
  <ns>0</ns>
  <id>73</id>
  <revision>
    <id>184</id>
    <timestamp>2008-12-14T09:16:41Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh quit command ==== Usage: quit  Quit the shell.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="57" xml:space="preserve">==== Vimsh quit command ====
Usage: quit

Quit the shell.</text>
    <sha1>cf2d2ffe5009e32edc722e0be5486f1898fe7a4a</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>185</id>
    <parentid>145</parentid>
    <timestamp>2008-12-14T09:20:15Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3464" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;

==== List of commands ====

Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki, not sure if that's a smart thing to do...)

Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help. 

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that it will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>69dda3b43a0349f58613432f79c59d28cd2085ac</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: hostsvc/</title>
  <ns>0</ns>
  <id>45</id>
  <revision>
    <id>186</id>
    <parentid>133</parentid>
    <timestamp>2008-12-14T09:20:45Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1877" xml:space="preserve"> [/]$ hostsvc/
 advopt/                    cpuinfo                             pci_add                   
 autostartmanager/    firewall_disable_ruleset      pci_remove                
 datastore/                firewall_enable_ruleset      queryconnectioninfo       
 datastorebrowser/     hostconfig                        querydisabledmethods      
 firmware/                 hosthardware                    refresh_firewall          
 net/                         hostsummary                    refresh_services          
 rsrc/                        login                                 runtimeinfo               
 storage/                   logout                               set_hostid                
 summary/                maintenance_mode_enter   standby_mode_enter        
 vmotion/                  maintenance_mode_exit     standby_mode_exit         
 connect                    memoryinfo                       task_list        


 [[hostsvc/ advopt/]]
 [[hostsvc/ autostartmanager/]]
 [[hostsvc/ datastore/]]
 [[hostsvc/ datastorebrowser/]]
 [[hostsvc/ firmware/]]
 [[hostsvc/ net/]]
 [[hostsvc/ rsrc/]]
 [[hostsvc/ storage/]]
 [[hostsvc/ summary/]]
 [[hostsvc/ vmotion/]]
 [[hostsvc/ connect]]
 [[hostsvc/ cpuinfo]]
 [[hostsvc/ firewall_disable_ruleset]]
 [[hostsvc/ firewall_enable_ruleset]] 
 [[hostsvc/ hostconfig]]
 [[hostsvc/ hosthardware]]
 [[hostsvc/ hostsummary]]
 [[hostsvc/ login]]
 [[hostsvc/ logout]]
 [[hostsvc/ maintenance_mode_enter]]
 [[hostsvc/ maintenance_mode_exit]]
 [[hostsvc/ memoryinfo]]
 [[hostsvc/ pci_add]]
 [[hostsvc/ pci_remove]]
 [[hostsvc/ queryconnectioninfo]]
 [[hostsvc/ querydisabledmethods]]
 [[hostsvc/ refresh_firewall]]
 [[hostsvc/ refresh_services]] 
 [[hostsvc/ runtimeinfo]] 
 [[hostsvc/ set_hostid]] 
 [[hostsvc/ standby_mode_enter]] 
 [[hostsvc/ standby_mode_exit]] 
 [[hostsvc/ task_list]]

[[Category: Vimsh]]</text>
    <sha1>257301fc6695c96ca8b3a8e698a3f951ab1391c7</sha1>
  </revision>
  <revision>
    <id>199</id>
    <parentid>186</parentid>
    <timestamp>2008-12-15T00:12:42Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2043" xml:space="preserve">==== Hostsvc sub ====

ESX host services, lists and/or change host specific information such as firewall information, host status like maintenance mode and standby.

 [/]$ hostsvc/
 advopt/                    cpuinfo                             pci_add                   
 autostartmanager/    firewall_disable_ruleset      pci_remove                
 datastore/                firewall_enable_ruleset      queryconnectioninfo       
 datastorebrowser/     hostconfig                        querydisabledmethods      
 firmware/                 hosthardware                    refresh_firewall          
 net/                         hostsummary                    refresh_services          
 rsrc/                        login                                 runtimeinfo               
 storage/                   logout                               set_hostid                
 summary/                maintenance_mode_enter   standby_mode_enter        
 vmotion/                  maintenance_mode_exit     standby_mode_exit         
 connect                    memoryinfo                       task_list        


 [[hostsvc/ advopt/]]
 [[hostsvc/ autostartmanager/]]
 [[hostsvc/ datastore/]]
 [[hostsvc/ datastorebrowser/]]
 [[hostsvc/ firmware/]]
 [[hostsvc/ net/]]
 [[hostsvc/ rsrc/]]
 [[hostsvc/ storage/]]
 [[hostsvc/ summary/]]
 [[hostsvc/ vmotion/]]
 [[hostsvc/ connect]]
 [[hostsvc/ cpuinfo]]
 [[hostsvc/ firewall_disable_ruleset]]
 [[hostsvc/ firewall_enable_ruleset]] 
 [[hostsvc/ hostconfig]]
 [[hostsvc/ hosthardware]]
 [[hostsvc/ hostsummary]]
 [[hostsvc/ login]]
 [[hostsvc/ logout]]
 [[hostsvc/ maintenance_mode_enter]]
 [[hostsvc/ maintenance_mode_exit]]
 [[hostsvc/ memoryinfo]]
 [[hostsvc/ pci_add]]
 [[hostsvc/ pci_remove]]
 [[hostsvc/ queryconnectioninfo]]
 [[hostsvc/ querydisabledmethods]]
 [[hostsvc/ refresh_firewall]]
 [[hostsvc/ refresh_services]] 
 [[hostsvc/ runtimeinfo]] 
 [[hostsvc/ set_hostid]] 
 [[hostsvc/ standby_mode_enter]] 
 [[hostsvc/ standby_mode_exit]] 
 [[hostsvc/ task_list]]

[[Category: Vimsh]]</text>
    <sha1>ce202ff9c1182e502bc7a06e7f9a190d9be06925</sha1>
  </revision>
  <revision>
    <id>200</id>
    <parentid>199</parentid>
    <timestamp>2008-12-15T00:14:25Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>removed spaces between links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2011" xml:space="preserve">==== Hostsvc sub ====

ESX host services, lists and/or change host specific information such as firewall information, host status like maintenance mode and standby.

 [/]$ hostsvc/
 advopt/                    cpuinfo                             pci_add                   
 autostartmanager/    firewall_disable_ruleset      pci_remove                
 datastore/                firewall_enable_ruleset      queryconnectioninfo       
 datastorebrowser/     hostconfig                        querydisabledmethods      
 firmware/                 hosthardware                    refresh_firewall          
 net/                         hostsummary                    refresh_services          
 rsrc/                        login                                 runtimeinfo               
 storage/                   logout                               set_hostid                
 summary/                maintenance_mode_enter   standby_mode_enter        
 vmotion/                  maintenance_mode_exit     standby_mode_exit         
 connect                    memoryinfo                       task_list        


 [[hostsvc/advopt/]]
 [[hostsvc/autostartmanager/]]
 [[hostsvc/datastore/]]
 [[hostsvc/datastorebrowser/]]
 [[hostsvc/firmware/]]
 [[hostsvc/net/]]
 [[hostsvc/rsrc/]]
 [[hostsvc/storage/]]
 [[hostsvc/summary/]]
 [[hostsvc/vmotion/]]
 [[hostsvc/connect]]
 [[hostsvc/cpuinfo]]
 [[hostsvc/firewall_disable_ruleset]]
 [[hostsvc/firewall_enable_ruleset]] 
 [[hostsvc/hostconfig]]
 [[hostsvc/hosthardware]]
 [[hostsvc/hostsummary]]
 [[hostsvc/login]]
 [[hostsvc/logout]]
 [[hostsvc/ maintenance_mode_enter]]
 [[hostsvc/maintenance_mode_exit]]
 [[hostsvc/memoryinfo]]
 [[hostsvc/pci_add]]
 [[hostsvc/pci_remove]]
 [[hostsvc/queryconnectioninfo]]
 [[hostsvc/querydisabledmethods]]
 [[hostsvc/refresh_firewall]]
 [[hostsvc/refresh_services]] 
 [[hostsvc/runtimeinfo]] 
 [[hostsvc/set_hostid]] 
 [[hostsvc/standby_mode_enter]] 
 [[hostsvc/standby_mode_exit]] 
 [[hostsvc/task_list]]

[[Category: Vimsh]]</text>
    <sha1>828132b3568f0af6a10e731a1fc5aab77889828a</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: internalsvc/</title>
  <ns>0</ns>
  <id>48</id>
  <revision>
    <id>187</id>
    <parentid>137</parentid>
    <timestamp>2008-12-14T09:21:09Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="531" xml:space="preserve"> [/]$ internalsvc/
 perfcount/              redirect_stderr           refresh_pnic            
 access_address      redirect_stdout           set_exception_variable  
 connect                  refresh                      set_log_level           
 host_mode_lock     refresh_consolenic      shutdown                
 login                     refresh_datastores      throw_exception         
 loglist                    refresh_gateway         use_fds                 
 logout                   refresh_network

[[Category: Vimsh]]</text>
    <sha1>dcc8a3675f4e1904d18948d1143ea3a2eaa1d829</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: proxysvc/</title>
  <ns>0</ns>
  <id>49</id>
  <revision>
    <id>188</id>
    <parentid>138</parentid>
    <timestamp>2008-12-14T09:21:28Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="176" xml:space="preserve"> [/]$ proxysvc/   
 add_np_service   connect          logout           remove_service   
 add_tcp_service  login              port_info        service_list

[[Category: Vimsh]]</text>
    <sha1>d64111ee3bae1e7cf2004ad857e57024974875e4</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: solo/</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>189</id>
    <parentid>136</parentid>
    <timestamp>2008-12-14T09:21:46Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve"> [/]$ solo/ 
 connect          login             querycfgopt         registervm       
 environment   logout           querycfgoptdesc

[[Category: Vimsh]]</text>
    <sha1>0b900eae3f25bad12b3b29e40dea3fbe322740f1</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: vimsvc/</title>
  <ns>0</ns>
  <id>50</id>
  <revision>
    <id>190</id>
    <parentid>139</parentid>
    <timestamp>2008-12-14T09:22:05Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="228" xml:space="preserve"> [/]$ vimsvc/  
 auth/              login                    task_cancel         task_list         
 connect           logout                 task_description  
 license            property_dump    task_info

[[Category: Vimsh]]</text>
    <sha1>8abde5a3ba5e513693d5e73e34c6e8a231b7c8fc</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: vmsvc/</title>
  <ns>0</ns>
  <id>46</id>
  <revision>
    <id>191</id>
    <parentid>135</parentid>
    <timestamp>2008-12-14T09:22:29Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1698" xml:space="preserve"> [/]$ vmsvc/
 acquiremksticket          get.configoption              power.off                 
 connect                       get.datastores                 power.on                  
 convert.toTemplate      get.disabledmethods        power.reboot              
 convert.toVm               get.environment              power.reset               
 createdummyvm          get.filelayout                   power.shutdown            
 destroy                       get.guest                         power.suspend             
 device.connection         get.guestheartbeatStatus  reload                    
 device.connusbdev       get.managedentitystatus   setscreenres              
 device.disconnusbdev   get.networks                    snapshot.create           
 device.diskadd             get.runtime                      snapshot.get              
 device.diskaddexisting  get.snapshotinfo               snapshot.remove           
 device.diskremove       get.summary                    snapshot.removeall        
 device.getdevices         get.tasklist                       snapshot.revert           
 device.toolsSyncSet      getallvms                        snapshot.setoption        
 device.vmiadd              gethostconstraints            tools.cancelinstall       
 device.vmiremove         login                              tools.install             
 devices.createnic           logout                            tools.upgrade             
 get.capability                message                        unregister                
 get.config                     power.getstate                upgrade                   
 get.config.cpuidmask     power.hibernate

[[Category: Vimsh]]</text>
    <sha1>8dff034f9e6929eb9da14336adb167776767be95</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Vimsh: ?</title>
  <ns>0</ns>
  <id>51</id>
  <revision>
    <id>192</id>
    <parentid>141</parentid>
    <timestamp>2008-12-14T09:23:34Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="202" xml:space="preserve">==== Vimsh ? command====
The online help.

Usage: ? &lt;command&gt;

Will print the available help for the selected command.

This fine command is used as a starting point for this manual

[[Category: Vimsh]]</text>
    <sha1>bb7e5784a18a9fbdbb70b15b3b481b2badfa203d</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Hostsvc/maintenance mode enter</title>
  <ns>0</ns>
  <id>53</id>
  <revision>
    <id>198</id>
    <parentid>144</parentid>
    <timestamp>2008-12-14T09:28:34Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="136" xml:space="preserve">==== Hostsvc/maintenance_mode_enter ====
Usage: maintenance_mode_enter [timeout]

Put the host in maintenance mode.

[[Category: Vimsh]]</text>
    <sha1>91c3f3bfc9fa106cf8ec5ad0a55c869e96c6fbae</sha1>
  </revision>
  <revision>
    <id>201</id>
    <parentid>198</parentid>
    <timestamp>2008-12-15T00:14:54Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[Hostsvc/ maintenance mode enter]] moved to [[Hostsvc/maintenance mode enter]]: oblivious space</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="136" xml:space="preserve">==== Hostsvc/maintenance_mode_enter ====
Usage: maintenance_mode_enter [timeout]

Put the host in maintenance mode.

[[Category: Vimsh]]</text>
    <sha1>91c3f3bfc9fa106cf8ec5ad0a55c869e96c6fbae</sha1>
  </revision>
</page>
<page arvcontinue="20081213102725|153">
  <title>Hostsvc/ maintenance mode enter</title>
  <ns>0</ns>
  <id>74</id>
  <revision>
    <id>202</id>
    <timestamp>2008-12-15T00:14:54Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>[[Hostsvc/ maintenance mode enter]] moved to [[Hostsvc/maintenance mode enter]]: oblivious space</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44" xml:space="preserve">#REDIRECT [[Hostsvc/maintenance mode enter]]</text>
    <sha1>8dfae71151ea063806fa7852292633577fd26e2f</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: hostsvc/</title>
  <ns>0</ns>
  <id>45</id>
  <revision>
    <id>203</id>
    <parentid>200</parentid>
    <timestamp>2008-12-15T00:15:30Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2010" xml:space="preserve">==== Hostsvc sub ====

ESX host services, lists and/or change host specific information such as firewall information, host status like maintenance mode and standby.

 [/]$ hostsvc/
 advopt/                    cpuinfo                             pci_add                   
 autostartmanager/    firewall_disable_ruleset      pci_remove                
 datastore/                firewall_enable_ruleset      queryconnectioninfo       
 datastorebrowser/     hostconfig                        querydisabledmethods      
 firmware/                 hosthardware                    refresh_firewall          
 net/                         hostsummary                    refresh_services          
 rsrc/                        login                                 runtimeinfo               
 storage/                   logout                               set_hostid                
 summary/                maintenance_mode_enter   standby_mode_enter        
 vmotion/                  maintenance_mode_exit     standby_mode_exit         
 connect                    memoryinfo                       task_list        


 [[hostsvc/advopt/]]
 [[hostsvc/autostartmanager/]]
 [[hostsvc/datastore/]]
 [[hostsvc/datastorebrowser/]]
 [[hostsvc/firmware/]]
 [[hostsvc/net/]]
 [[hostsvc/rsrc/]]
 [[hostsvc/storage/]]
 [[hostsvc/summary/]]
 [[hostsvc/vmotion/]]
 [[hostsvc/connect]]
 [[hostsvc/cpuinfo]]
 [[hostsvc/firewall_disable_ruleset]]
 [[hostsvc/firewall_enable_ruleset]] 
 [[hostsvc/hostconfig]]
 [[hostsvc/hosthardware]]
 [[hostsvc/hostsummary]]
 [[hostsvc/login]]
 [[hostsvc/logout]]
 [[hostsvc/maintenance_mode_enter]]
 [[hostsvc/maintenance_mode_exit]]
 [[hostsvc/memoryinfo]]
 [[hostsvc/pci_add]]
 [[hostsvc/pci_remove]]
 [[hostsvc/queryconnectioninfo]]
 [[hostsvc/querydisabledmethods]]
 [[hostsvc/refresh_firewall]]
 [[hostsvc/refresh_services]] 
 [[hostsvc/runtimeinfo]] 
 [[hostsvc/set_hostid]] 
 [[hostsvc/standby_mode_enter]] 
 [[hostsvc/standby_mode_exit]] 
 [[hostsvc/task_list]]

[[Category: Vimsh]]</text>
    <sha1>daddb9b7121ea8ed4c4e3c610d441e67914bc7bf</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/connect</title>
  <ns>0</ns>
  <id>75</id>
  <revision>
    <id>204</id>
    <timestamp>2008-12-15T00:16:23Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/connect ==== Usage: connect [hostname] [port] [key] [cert] [product]  Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="410" xml:space="preserve">==== vimsh hostsvc/connect ====
Usage: connect [hostname] [port] [key] [cert] [product]

Connects to product (solo|vpxa|vpxd) listening at hostname on
TCP port port using a private key and a certificate.

By default product is 'solo', hostname is 'localhost'.

 Port is 902.
 private key is at /etc/vmware/ssl/rui.key
 certificate is at /etc/vmware/ssl/rui.crt

To disable SSL, use an empty key or certificate.</text>
    <sha1>62ae3ef913dd525752c171abdc5d2cf1a3aa8803</sha1>
  </revision>
  <revision>
    <id>205</id>
    <parentid>204</parentid>
    <timestamp>2008-12-15T00:17:01Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="431" xml:space="preserve">==== vimsh hostsvc/connect ====
Usage: connect [hostname] [port] [key] [cert] [product]

Connects to product (solo|vpxa|vpxd) listening at hostname on
TCP port port using a private key and a certificate.

By default product is 'solo', hostname is 'localhost'.

 Port is 902.
 private key is at /etc/vmware/ssl/rui.key
 certificate is at /etc/vmware/ssl/rui.crt

To disable SSL, use an empty key or certificate.

[[Category: Vimsh]]</text>
    <sha1>58c8331da1670bba50718a85b793c419f6edc6df</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/cpuinfo</title>
  <ns>0</ns>
  <id>76</id>
  <revision>
    <id>206</id>
    <timestamp>2008-12-15T00:18:16Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/cpuinfo ====  Usage: cpuinfo [hyperthreadCfg]  Get the CPU information.  If hyperthreadCfg is specified, sets configuration for hyperthreading.  Valid values include 'tr...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="226" xml:space="preserve">==== vimsh hostsvc/cpuinfo ====

Usage: cpuinfo [hyperthreadCfg]

Get the CPU information.  If hyperthreadCfg is specified, sets configuration
for hyperthreading.  Valid values include 'true' and 'false'.


[[Category: vimsh]]</text>
    <sha1>a2c4045dfb7831e43599190a292f0e5d2fe73d8a</sha1>
  </revision>
  <revision>
    <id>207</id>
    <parentid>206</parentid>
    <timestamp>2008-12-15T00:18:40Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="228" xml:space="preserve">==== vimsh hostsvc/cpuinfo ====

Usage: cpuinfo [hyperthreadCfg]

Get the CPU information.  If hyperthreadCfg is specified, sets configuration
for hyperthreading.  

Valid values include 'true' and 'false'.


[[Category: vimsh]]</text>
    <sha1>d702611c696b1e7341ca5c89f6b0b2d713549f27</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/firewall disable ruleset</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>208</id>
    <timestamp>2008-12-15T00:20:28Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/firewall_disable_ruleset ====  Usage: firewall_disable_ruleset ruleset  disable_ruleset  Disable a particular firewall ruleset.   [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="168" xml:space="preserve">==== vimsh hostsvc/firewall_disable_ruleset ====

Usage: firewall_disable_ruleset ruleset

disable_ruleset

Disable a particular firewall ruleset.


[[Category: vimsh]]</text>
    <sha1>5c0c1fb1d4d87989e1dc8b6bb3e075837b701be6</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/firewall enable ruleset</title>
  <ns>0</ns>
  <id>78</id>
  <revision>
    <id>209</id>
    <timestamp>2008-12-15T00:21:46Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/firewall_enable_ruleset ====  Usage: firewall_enable_ruleset ruleset  enable_ruleset  Enable a particular firewall ruleset.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">==== vimsh hostsvc/firewall_enable_ruleset ====

Usage: firewall_enable_ruleset ruleset

enable_ruleset

Enable a particular firewall ruleset.

[[Category: Vimsh]]</text>
    <sha1>d6bb9b80cd9c2d7b4dc0bb95bc0ebd185857d6af</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: csuimport</title>
  <ns>0</ns>
  <id>64</id>
  <revision>
    <id>210</id>
    <parentid>167</parentid>
    <timestamp>2008-12-15T00:23:23Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="326" xml:space="preserve">==== vimsh csuimport command ====
Usage: csuimport commandset [folder]

Unimports a command set from a specific location in the namespace.  If the
folder is not specified, uimports the command set in the default folder for
that command set.

See 'csinfo plugin' and 'csinfo commands' for more information.

[[Category: Vimsh]]</text>
    <sha1>34523c89b9116d8935520ee953513c0da558ef08</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: echo</title>
  <ns>0</ns>
  <id>65</id>
  <revision>
    <id>211</id>
    <parentid>174</parentid>
    <timestamp>2008-12-15T00:23:44Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="139" xml:space="preserve">==== vimsh: echo command ====
Usage: echo [-n] [string] [string2] ...

Options:
  -n            Don't print a newline.

[[Category: Vimsh]]</text>
    <sha1>e2b588ac17b8210b4fbd8fea95bde65c54aa9d84</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: exit</title>
  <ns>0</ns>
  <id>52</id>
  <revision>
    <id>212</id>
    <parentid>143</parentid>
    <timestamp>2008-12-15T00:24:03Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="78" xml:space="preserve">==== vimsh exit command ====
Usage: quit

Quit the shell.

[[Category: Vimsh]]</text>
    <sha1>19279b9b2a16a5539ec2608262b86bf050599335</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: help</title>
  <ns>0</ns>
  <id>66</id>
  <revision>
    <id>213</id>
    <parentid>175</parentid>
    <timestamp>2008-12-15T00:24:21Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="97" xml:space="preserve">==== Vimsh help command ====
Usage: help [command]

Print help for commands.

[[Category: Vimsh]]</text>
    <sha1>9f80df285f7a3de718956cfc6ea3ed77a4bb2e6c</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: puload</title>
  <ns>0</ns>
  <id>67</id>
  <revision>
    <id>214</id>
    <parentid>176</parentid>
    <timestamp>2008-12-15T00:24:40Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="278" xml:space="preserve">==== vimsh puload command ====
Usage: puload [-f] plugin

Unloads a plugin specified using the plugin name.

Options:
  -f            Unimport all command sets for this plugin.

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.

[[Category: Vimsh]]</text>
    <sha1>2288919c9c9f336812898db4c2516fc71188c385</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: pinfo</title>
  <ns>0</ns>
  <id>68</id>
  <revision>
    <id>215</id>
    <parentid>177</parentid>
    <timestamp>2008-12-15T00:24:58Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">==== Vimsh: pinfo command ====
Usage: pinfo plugin

Displays information about a plugin.

[[Category: Vimsh]]</text>
    <sha1>5f5928cd2099461ca137d6545f65a284b72fb6bb</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: pload</title>
  <ns>0</ns>
  <id>69</id>
  <revision>
    <id>216</id>
    <parentid>179</parentid>
    <timestamp>2008-12-15T00:25:17Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="193" xml:space="preserve">==== vimsh pload command ====
Usage: pload filepath

Loads a plugin specified in file name.

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.

[[Category: Vimsh]]</text>
    <sha1>734ea90300431ceb572b8b1c8c9cf98f21870d4b</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: ploadpath</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>217</id>
    <parentid>180</parentid>
    <timestamp>2008-12-15T00:25:35Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="395" xml:space="preserve">==== Vimsh ploadpath command ====
Usage: ploadpath [-u] [filepath] [filepath2] ...

Specifies search path for locating plugins.  Multiple paths may be specified.
Invoking command with no search paths prints out current plugin search path.

Options:
  -u            Undefine plugin search path.

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.

[[Category: Vimsh]]</text>
    <sha1>cdb69b549d8e6a8b3ddf532d54156809670819f3</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: pls</title>
  <ns>0</ns>
  <id>71</id>
  <revision>
    <id>218</id>
    <parentid>181</parentid>
    <timestamp>2008-12-15T00:25:53Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="412" xml:space="preserve">==== Vimsh: pls command ====
Usage: pls [-s] [plugin]

List the name of the plugins that are currently loaded.  When a plugin name
is specified, lists the commands or command sets provided by the plugin.

Options:
  -s            List command sets for this plugin.  Default is to list
                commands.

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.

[[Category: Vimsh]]</text>
    <sha1>5db412e07a7ab8b0d673110843b0ee3f39703cd3</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: puse</title>
  <ns>0</ns>
  <id>72</id>
  <revision>
    <id>219</id>
    <parentid>183</parentid>
    <timestamp>2008-12-15T00:26:12Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="237" xml:space="preserve">==== Vimsh puse command ====
Usage: puse filepath

Loads a plugin specified by filepath and imports command sets in default
location.  

See '[[Vimsh: csinfo|csinfo plugin]]' for more information about using plugins.

[[Category: Vimsh]]</text>
    <sha1>50f8137cfdc58a17aa75d6585309e883770e62c4</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: quit</title>
  <ns>0</ns>
  <id>73</id>
  <revision>
    <id>220</id>
    <parentid>184</parentid>
    <timestamp>2008-12-15T00:26:31Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="78" xml:space="preserve">==== Vimsh quit command ====
Usage: quit

Quit the shell.

[[Category: Vimsh]]</text>
    <sha1>cdb5eddb824cc2762246bec9d6aad55f77a36261</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: sleep</title>
  <ns>0</ns>
  <id>55</id>
  <revision>
    <id>221</id>
    <parentid>147</parentid>
    <timestamp>2008-12-15T00:27:11Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="161" xml:space="preserve">==== vimsh sleep command ====
Usage: sleep [time in seconds]

Very useful in a script if a process is expected to take some time to complete.
[[Category: Vimsh]]</text>
    <sha1>4aa347ee3607880fe57ea42b39c0cb9961c9828c</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Vimsh: source</title>
  <ns>0</ns>
  <id>54</id>
  <revision>
    <id>222</id>
    <parentid>146</parentid>
    <timestamp>2008-12-15T00:27:33Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="116" xml:space="preserve">==== vimsh source command ====

Usage: source filename

Load commands defined in file filename.

[[Category: Vimsh]]</text>
    <sha1>a32fd926d3e914d32c248e1f23ba9f5c11f159f2</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/hostconfig</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>223</id>
    <timestamp>2008-12-15T00:29:06Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/hostconfig ==== Usage: hostconfig  Retrieves the host config managed object references.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="127" xml:space="preserve">==== vimsh hostsvc/hostconfig ====
Usage: hostconfig

Retrieves the host config managed object references.

[[Category: Vimsh]]</text>
    <sha1>52d96a1c0812a70aeefebd434b2e51d4acf58829</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/hosthardware</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>224</id>
    <timestamp>2008-12-15T00:30:00Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh Hostsvc/hosthardware ==== Usage: hosthardware  Retrieves the host hardware information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="119" xml:space="preserve">==== Vimsh Hostsvc/hosthardware ====
Usage: hosthardware

Retrieves the host hardware information.

[[Category: Vimsh]]</text>
    <sha1>21f0b4388398fe71bf6f8a44a22875cb34cead2f</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/hostsummary</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>225</id>
    <timestamp>2008-12-15T00:30:53Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/hostsummary ==== Usage: hostsummary  Retrieves the host summary information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="116" xml:space="preserve">==== Vimsh hostsvc/hostsummary ====
Usage: hostsummary

Retrieves the host summary information.

[[Category: Vimsh]]</text>
    <sha1>327942cdcd83cebcb1784c1e6ec49dad8824753f</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/login</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>226</id>
    <timestamp>2008-12-15T00:31:45Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/login ==== Usage: login [username] [password]  Logs in to host, creating a new session.  If no password is specified, will use a local authentication mechanism.  [[Categ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="200" xml:space="preserve">==== Vimsh hostsvc/login ====
Usage: login [username] [password]

Logs in to host, creating a new session.  If no password is specified, will
use a local authentication mechanism.

[[Category: Vimsh]]</text>
    <sha1>d39799b2367aa5ac71941d4a2f2a0ca932ec7fe1</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/logout</title>
  <ns>0</ns>
  <id>83</id>
  <revision>
    <id>227</id>
    <timestamp>2008-12-15T00:32:32Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/logout ==== Usage: logout  Logs out from host, destroying existing session.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="115" xml:space="preserve">==== Vimsh hostsvc/logout ====
Usage: logout

Logs out from host, destroying existing session.

[[Category: Vimsh]]</text>
    <sha1>9a2533690235c7d22b0f57c8fbbc6af160c9c4a9</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/maintenance mode exit</title>
  <ns>0</ns>
  <id>84</id>
  <revision>
    <id>228</id>
    <timestamp>2008-12-15T00:33:31Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/maintenance_mode_exit ==== Usage: maintenance_mode_exit [timeout]  Take the host out of maintenance mode.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="145" xml:space="preserve">==== vimsh hostsvc/maintenance_mode_exit ====
Usage: maintenance_mode_exit [timeout]

Take the host out of maintenance mode.

[[Category: Vimsh]]</text>
    <sha1>c8d96b2d1c1bf90c1ee301c8aeaf3a70098042bb</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/memoryinfo</title>
  <ns>0</ns>
  <id>85</id>
  <revision>
    <id>229</id>
    <timestamp>2008-12-15T00:34:21Z</timestamp>
    <contributor>
      <username>WikiSysop</username>
      <id>1</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/memoryinfo ==== Usage: memoryinfo [memoryCfg]  Get the memory information.  If memoryCfg is specified, sets configured memory.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="166" xml:space="preserve">==== Vimsh hostsvc/memoryinfo ====
Usage: memoryinfo [memoryCfg]

Get the memory information.  If memoryCfg is specified, sets configured memory.

[[Category: Vimsh]]</text>
    <sha1>f421ee30b419edf776999ef32a258ac9041ae7cb</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Build host vmware kernel modules</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>230</id>
    <parentid>113</parentid>
    <timestamp>2008-12-15T06:36:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added SUSE lines</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2698" xml:space="preserve">====Integrated modules build script sometimes fails====
The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

====The solution====
You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm /etc/vmware/not_configured 

====Preconditions for the script to work====
You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko</text>
    <sha1>47c4b3b3f20fdfba04bc2a6ccc9895ba1308f76a</sha1>
  </revision>
  <revision>
    <id>231</id>
    <parentid>230</parentid>
    <timestamp>2008-12-15T06:37:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2699" xml:space="preserve">====Integrated modules build script sometimes fails====
The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

====The solution====
You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm /etc/vmware/not_configured 

====Preconditions for the script to work====
You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko</text>
    <sha1>a879585042378ef261e9502e2ce6ef0f09350c3b</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/pci add</title>
  <ns>0</ns>
  <id>86</id>
  <revision>
    <id>232</id>
    <timestamp>2008-12-15T07:10:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/pci_add ==== Usage: pci_add [OPTIONS] BusID SlotID FunctionID DeviceName  Adds a physical PCI device.  Options:    --classId=int        Class ID.     --vendorId=int     ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="303" xml:space="preserve">==== vimsh hostsvc/pci_add ====
Usage: pci_add [OPTIONS] BusID SlotID FunctionID DeviceName

Adds a physical PCI device.

Options:
   --classId=int
       Class ID.

   --vendorId=int
       Vendor ID.

   --vendorName=string
       Vendor Name.

   --deviceId=int
       Device Id.

[[Category: Vimsh]]</text>
    <sha1>b7166ec65e8ac5fd017a965c1f0a6426af8d2d3c</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/pci remove</title>
  <ns>0</ns>
  <id>87</id>
  <revision>
    <id>233</id>
    <timestamp>2008-12-15T07:11:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/pci_remove ==== Usage: pci_remove Pci ID  Removes a physical PCI device.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="112" xml:space="preserve">==== Vimsh hostsvc/pci_remove ====
Usage: pci_remove Pci ID

Removes a physical PCI device.

[[Category: Vimsh]]</text>
    <sha1>5a638e8c02b8505b0b14ea9fc1ced99265fe7b83</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/queryconnectioninfo</title>
  <ns>0</ns>
  <id>88</id>
  <revision>
    <id>234</id>
    <timestamp>2008-12-15T07:12:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/queryconnectioninfo==== Usage: queryconn  Query for connection information from the host.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="129" xml:space="preserve">==== Vimsh hostsvc/queryconnectioninfo====
Usage: queryconn

Query for connection information from the host.

[[Category: Vimsh]]</text>
    <sha1>24e9b77cd248f24dbdeb9571cbd90e55492b35a9</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/querydisabledmethods</title>
  <ns>0</ns>
  <id>89</id>
  <revision>
    <id>235</id>
    <timestamp>2008-12-15T07:13:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/querydisabledmethods==== Usage: querydisabled  Query for disabled methods on the host.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">==== Vimsh hostsvc/querydisabledmethods====
Usage: querydisabled

Query for disabled methods on the host.

[[Category: Vimsh]]</text>
    <sha1>b84a197c70d81eab5889851ef181d678338c446d</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/refresh firewall</title>
  <ns>0</ns>
  <id>90</id>
  <revision>
    <id>236</id>
    <timestamp>2008-12-15T07:15:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/refresh_firewall ==== Usage: refresh_firewall  refresh_firewall  Refesh the firewall state.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="131" xml:space="preserve">==== Vimsh hostsvc/refresh_firewall ====
Usage: refresh_firewall

refresh_firewall

Refesh the firewall state.

[[Category: Vimsh]]</text>
    <sha1>5fb90db54509816876c8ddf5dec9e09e92c4de14</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/refresh services</title>
  <ns>0</ns>
  <id>91</id>
  <revision>
    <id>237</id>
    <timestamp>2008-12-15T07:16:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/refresh_services ==== Usage: refresh_services  refresh_services  Refresh the host service state.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="136" xml:space="preserve">==== Vimsh hostsvc/refresh_services ====
Usage: refresh_services

refresh_services

Refresh the host service state.

[[Category: Vimsh]]</text>
    <sha1>b6d1669a0fd3c60d84dfded8ceb6308c9805a840</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/runtimeinfo</title>
  <ns>0</ns>
  <id>92</id>
  <revision>
    <id>238</id>
    <timestamp>2008-12-15T07:17:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/runtimeinfo==== Usage: runtimeinfo  Retrieves the host runtime information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="115" xml:space="preserve">==== Vimsh hostsvc/runtimeinfo====
Usage: runtimeinfo

Retrieves the host runtime information.

[[Category: Vimsh]]</text>
    <sha1>1987f853bb322368f59b423e79fb991b348cd8f4</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/set hostid</title>
  <ns>0</ns>
  <id>93</id>
  <revision>
    <id>239</id>
    <timestamp>2008-12-15T07:17:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/set_hostid ==== Usage: set_hostid hostid  Sets the host id that the following host configuration commands apply to.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== Vimsh hostsvc/set_hostid ====
Usage: set_hostid hostid

Sets the host id that the following host configuration commands apply to.</text>
    <sha1>8b695d415e692911c12e79ddad4161308ace333b</sha1>
  </revision>
  <revision>
    <id>240</id>
    <parentid>239</parentid>
    <timestamp>2008-12-15T07:18:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve">==== Vimsh hostsvc/set_hostid ====
Usage: set_hostid hostid

Sets the host id that the following host configuration commands apply to.

[[Category: Vimsh]]</text>
    <sha1>f79989f5a2f7207c46f5962da86f51c20445fe06</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/standby mode enter</title>
  <ns>0</ns>
  <id>94</id>
  <revision>
    <id>241</id>
    <timestamp>2008-12-15T07:19:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/standby_mode_enter==== Usage: standby_mode_enter [timeout]  Put the host in standby mode.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="129" xml:space="preserve">==== Vimsh hostsvc/standby_mode_enter====
Usage: standby_mode_enter [timeout]

Put the host in standby mode.

[[Category: Vimsh]]</text>
    <sha1>9849a56faee96ceea89ed2649f48082af32f5600</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/standby mode exit</title>
  <ns>0</ns>
  <id>95</id>
  <revision>
    <id>242</id>
    <timestamp>2008-12-15T07:20:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/standby_mode_exit==== Usage: standby_mode_exit [timeout]  Take the host out of standby mode.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== Vimsh hostsvc/standby_mode_exit====
Usage: standby_mode_exit [timeout]

Take the host out of standby mode.

[[Category: Vimsh]]</text>
    <sha1>7fe738c674f524fbc069b56308938ce49691dede</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/task list</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>243</id>
    <timestamp>2008-12-15T07:21:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/task_list ==== Usage: task_list  Get list of recent tasks on virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="117" xml:space="preserve">==== Vimsh hostsvc/task_list ====
Usage: task_list

Get list of recent tasks on virtual machine.

[[Category: Vimsh]]</text>
    <sha1>4898b3b73fa48baecc783477a440851f003ef367</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/</title>
  <ns>0</ns>
  <id>97</id>
  <revision>
    <id>244</id>
    <timestamp>2008-12-15T07:35:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh Hostsvc/net/====  Get and set host network configuration of DNS, portgroup, virtual Switch and physical nics.  [/]$ ? hostsvc/net/  mockup/                          portgroup_re...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3296" xml:space="preserve">==== Vimsh Hostsvc/net/====

Get and set host network configuration of DNS, portgroup, virtual Switch and physical nics.

[/]$ ? hostsvc/net/
 mockup/                          portgroup_remove           
 provider/                          portgroup_set              
 capabilities                        portgroup_unsetpolicy      
 config                               query_networkhint          
 config_append                   refresh                    
 config_incremental_update  route_info                 
 config_load                        route_set                  
 config_save                       vnic_add                   
 console_route_set              vnic_info                  
 consolevnic_add                vnic_remove                
 consolevnic_info                vnic_set                   
 consolevnic_remove          vswitch_add                
 consolevnic_set                 vswitch_info               
 dns_info                           vswitch_pnicinfo           
 dns_set                            vswitch_remove             
 dns_unset                         vswitch_setautobridge      
 info                                  vswitch_setbondbridge      
 offload_capabilities            vswitch_setnumports        
 pnic_info                           vswitch_setpolicy          
 pnic_setip                          vswitch_setsimplebridge    
 pnic_setlinkspeed               vswitch_unsetbridge        
 portgroup_add         


 [[hostsvc/net/mockup/]]             
 [[hostsvc/net/provider/]]         
 [[hostsvc/net/capabilities]]    
 [[hostsvc/net/config]]                
 [[hostsvc/net/config_append]]          
 [[hostsvc/net/config_incremental_update]]            
 [[hostsvc/net/config_load]]     
 [[hostsvc/net/config_save]]   
 [[hostsvc/net/console_route_set]]       
 [[hostsvc/net/consolevnic_add]]          
 [[hostsvc/net/consolevnic_info]]           
 [[hostsvc/net/consolevnic_remove]]        
 [[hostsvc/net/consolevnic_set]]          
 [[hostsvc/net/dns_info]]       
 [[hostsvc/net/dns_set]]     
 [[hostsvc/net/dns_unset]]    
 [[hostsvc/net/info]]           
 [[hostsvc/net/offload_capabilities]]     
 [[hostsvc/net/pnic_info]]        
 [[hostsvc/net/pnic_setip]]    
 [[hostsvc/net/pnic_setlinkspeed]]    
 [[hostsvc/net/portgroup_add]]         
 [[hostsvc/net/portgroup_remove]]           
 [[hostsvc/net/portgroup_set]]              
 [[hostsvc/net/portgroup_unsetpolicy]]      
 [[hostsvc/net/query_networkhint]]          
 [[hostsvc/net/refresh]]                    
 [[hostsvc/net/route_info]]                 
 [[hostsvc/net/route_set]]                  
 [[hostsvc/net/vnic_add]]                   
 [[hostsvc/net/vnic_info]]                  
 [[hostsvc/net/vnic_remove]]                
 [[hostsvc/net/vnic_set]]                   
 [[hostsvc/net/vswitch_add]]                
 [[hostsvc/net/vswitch_info]]               
 [[hostsvc/net/vswitch_pnicinfo]]           
 [[hostsvc/net/vswitch_remove]]             
 [[hostsvc/net/vswitch_setautobridge]]      
 [[hostsvc/net/vswitch_setbondbridge]]      
 [[hostsvc/net/vswitch_setnumports]]        
 [[hostsvc/net/vswitch_setpolicy]]          
 [[hostsvc/net/vswitch_setsimplebridge]]    
 [[hostsvc/net/vswitch_unsetbridge]]        
       

[[Category: Vimsh]]</text>
    <sha1>b56f534764924633552efe6f59f4196900e983c5</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/info</title>
  <ns>0</ns>
  <id>98</id>
  <revision>
    <id>245</id>
    <timestamp>2008-12-15T07:36:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Vimsh hostsvc/net/info ==== Usage: info  Get the network information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="95" xml:space="preserve">==== Vimsh hostsvc/net/info ====
Usage: info

Get the network information.

[[Category: Vimsh]]</text>
    <sha1>6f7ef8b21cee9bef493e702eb3511dbd9ac5287e</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/config</title>
  <ns>0</ns>
  <id>99</id>
  <revision>
    <id>246</id>
    <timestamp>2008-12-15T07:37:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/config ==== Usage: config  Get the network configuration.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="101" xml:space="preserve">==== vimsh hostsvc/net/config ====
Usage: config

Get the network configuration.

[[Category: Vimsh]]</text>
    <sha1>53237945865c0371a7cb0c79e8f223b880b18512</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/capabilities</title>
  <ns>0</ns>
  <id>100</id>
  <revision>
    <id>247</id>
    <timestamp>2008-12-16T06:10:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/capabilities ==== Usage: capabilities  Get the network capabilities.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="112" xml:space="preserve">==== vimsh hostsvc/net/capabilities ====
Usage: capabilities

Get the network capabilities.

[[Category: Vimsh]]</text>
    <sha1>52fabcc7ffb861e34971886a36d5ba5a6efea1a1</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/config append</title>
  <ns>0</ns>
  <id>101</id>
  <revision>
    <id>248</id>
    <timestamp>2008-12-16T06:11:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/config_append ==== Usage: config_append filename  Appends a network configuration from a file and updates it.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="153" xml:space="preserve">==== vimsh hostsvc/net/config_append ====
Usage: config_append filename

Appends a network configuration from a file and updates it.

[[Category: Vimsh]]</text>
    <sha1>75bf8f8f4c7873e8389c37f3e19bc38463925680</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/config incremental update</title>
  <ns>0</ns>
  <id>102</id>
  <revision>
    <id>249</id>
    <timestamp>2008-12-16T06:13:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/config_incremental_update ==== Usage: config_incremental_update [OPTIONS]  Incremental update network configuration.  Options:    --vswitch-remove=string_list       ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="461" xml:space="preserve">==== vimsh hostsvc/net/config_incremental_update ====
Usage: config_incremental_update [OPTIONS]

Incremental update network configuration.

Options:
   --vswitch-remove=string_list
       List of vswitches to remove.

   --portgrp-remove=string_list
       List of portgroups to remove.

   --consolevnic-remove=string_list
       List of console virtual nics to remove.

   --vnic-remove=string_list
       List of virtual nics to remove.

[[Category: Vimsh]]</text>
    <sha1>94241b12d699bc0d45448891381de4788bfbbeca</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/config load</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>250</id>
    <timestamp>2008-12-16T06:14:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/config_load ==== Usage: config_load filename  Loads a network configuration from a file and updates it.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="147" xml:space="preserve">==== vimsh hostsvc/net/config_load ====
Usage: config_load filename

Loads a network configuration from a file and updates it.

[[Category: Vimsh]]</text>
    <sha1>aad43ba4921b5b7f7a5d61d827507f53cdc229ad</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/config save</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>251</id>
    <timestamp>2008-12-16T06:15:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/config_save ==== Usage: config_save filename  Get the network configuration and save it to a file.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="142" xml:space="preserve">==== vimsh hostsvc/net/config_save ====
Usage: config_save filename

Get the network configuration and save it to a file.

[[Category: Vimsh]]</text>
    <sha1>c4d1499c517311d61d84f211d07980e4046e0be0</sha1>
  </revision>
</page>
<page arvcontinue="20081215001530|203">
  <title>Hostsvc/net/console route set</title>
  <ns>0</ns>
  <id>105</id>
  <revision>
    <id>252</id>
    <timestamp>2008-12-16T06:17:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/console_route_set ==== Usage: console_route_set [OPTIONS]  Sets the console IP route configuration.  Options:    --route-gateway=string        IP address.     --rout...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="313" xml:space="preserve">==== vimsh hostsvc/net/console_route_set ====
Usage: console_route_set [OPTIONS]

Sets the console IP route configuration.

Options:
   --route-gateway=string
       IP address.

   --route-gateway-device=console_virtual_nic
       The service console NIC which is the default gateway device.

[[Category: Vimsh]]</text>
    <sha1>eb21deca8b64bf142fd6fbaa059bc55420a61ab5</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/consolevnic add</title>
  <ns>0</ns>
  <id>106</id>
  <revision>
    <id>253</id>
    <timestamp>2008-12-16T06:19:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/consolevnic_add ==== Usage: consolevnic_add [OPTIONS] portgroup  Adds a Service Console virtual NIC to the system.  Options:    --ip-dhcp=bool        Enables or disa...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="327" xml:space="preserve">==== vimsh hostsvc/net/consolevnic_add ====
Usage: consolevnic_add [OPTIONS] portgroup

Adds a Service Console virtual NIC to the system.

Options:
   --ip-dhcp=bool
       Enables or disables DHCP configuration.

   --ip-address=ip_address
       IP address.

   --ip-subnet=ip_address
       Subnet mask.

[[Category: Vimsh]]</text>
    <sha1>a44f805cd4a8f1be3d43b1829f8a6058715bf141</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/consolevnic info</title>
  <ns>0</ns>
  <id>107</id>
  <revision>
    <id>254</id>
    <timestamp>2008-12-16T06:20:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/consolevnic_info ==== Usage: consolevnic_info [consolevnic]  Gets information about Service Console virtual NICs. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="156" xml:space="preserve">==== vimsh hostsvc/net/consolevnic_info ====
Usage: consolevnic_info [consolevnic]

Gets information about Service Console virtual NICs.
[[Category: Vimsh]]</text>
    <sha1>c4dacc5d4a90ec130e4bf1cce1c4fe069a2717bf</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/consolevnic remove</title>
  <ns>0</ns>
  <id>108</id>
  <revision>
    <id>255</id>
    <timestamp>2008-12-16T06:22:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/consolevnic_remove ==== Usage: consolevnic_remove consolevnic  Removes a Service Console virtual NIC.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="145" xml:space="preserve">==== vimsh hostsvc/net/consolevnic_remove ====
Usage: consolevnic_remove consolevnic

Removes a Service Console virtual NIC.

[[Category: Vimsh]]</text>
    <sha1>537048681ecc21433856b74c89460d81e2f1607a</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/consolevnic set</title>
  <ns>0</ns>
  <id>109</id>
  <revision>
    <id>256</id>
    <timestamp>2008-12-16T06:23:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/consolevnic_set ==== Usage: consolevnic_set [OPTIONS] consolevnic  Reconfigures a Service Console virtual NIC on the system.  Options:    --vnic-mac=string        Se...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="400" xml:space="preserve">==== vimsh hostsvc/net/consolevnic_set ====
Usage: consolevnic_set [OPTIONS] consolevnic

Reconfigures a Service Console virtual NIC on the system.

Options:
   --vnic-mac=string
       Sets the mac address of this vnic.

   --ip-dhcp=bool
       Enables or disables DHCP configuration.

   --ip-address=ip_address
       IP address.

   --ip-subnet=ip_address
       Subnet mask.
[[Category: Vimsh]]</text>
    <sha1>1a46506aefea9cc404a8e48c83177dcc65fdeda6</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/dns info</title>
  <ns>0</ns>
  <id>110</id>
  <revision>
    <id>257</id>
    <timestamp>2008-12-16T06:37:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/dns_info ==== Usage: dns_info  Get the DNS configuration. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="100" xml:space="preserve">==== vimsh hostsvc/net/dns_info ====
Usage: dns_info

Get the DNS configuration.
[[Category: Vimsh]]</text>
    <sha1>d7140e7dbea9b959264e00876e8ed0a21fef5c67</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/dns set</title>
  <ns>0</ns>
  <id>111</id>
  <revision>
    <id>258</id>
    <timestamp>2008-12-16T06:38:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/dns_set ==== Usage: dns_set [OPTIONS]  Sets the DNS configuration.  Options:    --dns-dhcp=bool        Enables or disables automatic discovery of DNS configuration. ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="547" xml:space="preserve">==== vimsh hostsvc/net/dns_set ====
Usage: dns_set [OPTIONS]

Sets the DNS configuration.

Options:
   --dns-dhcp=bool
       Enables or disables automatic discovery of DNS configuration.

   --dns-dhcp-virtualnic=console_virtual_nic
       Service console NIC that overrides the system DNS.

   --dns-hostname=string
       Host name of host.

   --dns-domainname=string
       Domain name of host.

   --dns-addresses=ip_address_list
       List of DNS addresses.

   --dns-searchdomain=string_list
       DNS search domains.
[[Category: Vimsh]]</text>
    <sha1>7d202533020ae8d92512e8dd573edc65275e7d1c</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/dns unset</title>
  <ns>0</ns>
  <id>112</id>
  <revision>
    <id>259</id>
    <timestamp>2008-12-16T06:39:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/dns_unset ==== Usage: dns_unset  Unsets the DNS configuration. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="105" xml:space="preserve">==== vimsh hostsvc/net/dns_unset ====
Usage: dns_unset

Unsets the DNS configuration.
[[Category: Vimsh]]</text>
    <sha1>3a00400b86290f2a4d615a07cb80b15369b5e6d9</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/offload capabilities</title>
  <ns>0</ns>
  <id>113</id>
  <revision>
    <id>260</id>
    <timestamp>2008-12-16T06:40:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/offload_capabilities ==== Usage: offload_capabilities  Get the network offload capabilities. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="135" xml:space="preserve">==== vimsh hostsvc/net/offload_capabilities ====
Usage: offload_capabilities

Get the network offload capabilities.
[[Category: Vimsh]]</text>
    <sha1>824b9d4cc0cfd3165ff8ba0486828ee077ea169b</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/pnic info</title>
  <ns>0</ns>
  <id>114</id>
  <revision>
    <id>261</id>
    <timestamp>2008-12-16T06:41:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/pnic_info ==== Usage: pnic_info [pnic]  Sets and displays the IP configuration for a physical network.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="146" xml:space="preserve">==== vimsh hostsvc/net/pnic_info ====
Usage: pnic_info [pnic]

Sets and displays the IP configuration for a physical network.

[[Category: Vimsh]]</text>
    <sha1>a5b3bfe8ffd16ebc15a3f70a6523e757121b2d33</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/pnic setip</title>
  <ns>0</ns>
  <id>115</id>
  <revision>
    <id>262</id>
    <timestamp>2008-12-16T06:42:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/pnic_setip ==== Usage: pnic_setip [OPTIONS] [pnic]  Sets and displays the IP configuration for a physical network.  Options:    --ip-dhcp=bool        Enables or disa...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="327" xml:space="preserve">==== vimsh hostsvc/net/pnic_setip ====
Usage: pnic_setip [OPTIONS] [pnic]

Sets and displays the IP configuration for a physical network.

Options:
   --ip-dhcp=bool
       Enables or disables DHCP configuration.

   --ip-address=ip_address
       IP address.

   --ip-subnet=ip_address
       Subnet mask.

[[Category: Vimsh]]</text>
    <sha1>d902e00ed84341ea6d72c4cfa4078c9c96f443bd</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/pnic setlinkspeed</title>
  <ns>0</ns>
  <id>116</id>
  <revision>
    <id>263</id>
    <timestamp>2008-12-16T06:44:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/pnic_setlinkspeed ==== Usage: pnic_setlinkspeed [OPTIONS] pnic  Sets and unsets the link speed configuration for a physical NIC. Unsetting link speed effectively con...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="437" xml:space="preserve">==== vimsh hostsvc/net/pnic_setlinkspeed ====
Usage: pnic_setlinkspeed [OPTIONS] pnic

Sets and unsets the link speed configuration for a physical NIC.
Unsetting link speed effectively configures NIC to autonegotiate.
To unset, don't specify any options.
Options:
   --linkspeed-mb=physical_nic_mb
       The speed of the physical NIC in MB.

   --linkspeed-duplex=bool
       The duplex setting of the physical NIC.

[[Category: Vimsh]]</text>
    <sha1>365c7b55a70a88d39523566b5d71ca11041af4ed</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/portgroup add</title>
  <ns>0</ns>
  <id>117</id>
  <revision>
    <id>264</id>
    <timestamp>2008-12-16T06:46:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/portgroup_add ==== Usage: portgroup_add [OPTIONS] vswitch portgroup [vlan]  Adds a portgroup to a virtual switch.  Options:    --securepolicy-promisc=bool        All...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1913" xml:space="preserve">==== vimsh hostsvc/net/portgroup_add ====
Usage: portgroup_add [OPTIONS] vswitch portgroup [vlan]

Adds a portgroup to a virtual switch.

Options:
   --securepolicy-promisc=bool
       Allow promiscuous mode.

   --securepolicy-macchange=bool
       Allow MAC address to be changed.

   --securepolicy-forgedxmit=bool
       Allow forged transmits.

   --shapingpolicy-enabled=bool
       Enabled shaper.

   --shapingpolicy-average-bandwidth=int
       Average bandwidth.

   --shapingpolicy-peak-bandwidth=int
       Peak bandwidth.

   --shapingpolicy-burst-size=int
       Burst size.

   --nicorderpolicy-active=vmnic_list
       List of active NICs.

   --nicorderpolicy-standby=vmnic_list
       Order in which failover should occur.

   --failurecriteria-check-speed=failurecriteria-check-speed
       Detecting failover using link speed check

   --failurecriteria-speed=int
       The speed for link speed check method

   --failurecriteria-check-duplex=bool
       Detecting failover using link duplex check

   --failurecriteria-duplex=bool
       The duplexity for link duplex check method

   --failurecriteria-check-error=bool
       Detecting failover using link error percentage

   --failurecriteria-error=int
       The error percentage for link error percentage check method

   --failurecriteria-check-beacon=bool
       Detecting failover using the beacon

   --nicteaming-policy=nicteaming-policy
       Nic-Teaming policy.

   --nicteaming-reverse-policy=bool
       Apply the teaming policy to inbound frames as well.

   --nicteaming-notify-switch=bool
       Notify switches when detects a link failure.

   --nicteaming-rollingorder=bool
       Whether or not to use rolling failover.

   --offloadcaps-csum-offload=bool
       Checksum offload

   --offloadcaps-tcp-segment=bool
       TCP segment offload

   --offloadcaps-zerocopy-xmit=bool
       Scatter gather
[[Category: Vimsh]]</text>
    <sha1>74b50b59dce8f7cf22f5768acecad19b1bb842f8</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/portgroup remove</title>
  <ns>0</ns>
  <id>118</id>
  <revision>
    <id>265</id>
    <timestamp>2008-12-16T06:47:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/portgroup_remove ==== Usage: portgroup_remove vswitch portgroup  Removes a portgroup from a virtual switch.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">==== vimsh hostsvc/net/portgroup_remove ====
Usage: portgroup_remove vswitch portgroup

Removes a portgroup from a virtual switch.

[[Category: Vimsh]]</text>
    <sha1>82b42d64c083f1b361ab53120951f6793ddd6157</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/portgroup set</title>
  <ns>0</ns>
  <id>119</id>
  <revision>
    <id>266</id>
    <timestamp>2008-12-16T06:49:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/portgroup_set ==== Usage: portgroup_set [OPTIONS] vswitch portgroup  Sets the properties on a portgroup.  Options:    --securepolicy-promisc=bool        Allow promis...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2016" xml:space="preserve">==== vimsh hostsvc/net/portgroup_set ====
Usage: portgroup_set [OPTIONS] vswitch portgroup

Sets the properties on a portgroup.

Options:
   --securepolicy-promisc=bool
       Allow promiscuous mode.

   --securepolicy-macchange=bool
       Allow MAC address to be changed.

   --securepolicy-forgedxmit=bool
       Allow forged transmits.

   --shapingpolicy-enabled=bool
       Enabled shaper.

   --shapingpolicy-average-bandwidth=int
       Average bandwidth.

   --shapingpolicy-peak-bandwidth=int
       Peak bandwidth.

   --shapingpolicy-burst-size=int
       Burst size.

   --nicorderpolicy-active=vmnic_list
       List of active NICs.

   --nicorderpolicy-standby=vmnic_list
       Order in which failover should occur.

   --failurecriteria-check-speed=failurecriteria-check-speed
       Detecting failover using link speed check

   --failurecriteria-speed=int
       The speed for link speed check method

   --failurecriteria-check-duplex=bool
       Detecting failover using link duplex check

   --failurecriteria-duplex=bool
       The duplexity for link duplex check method

   --failurecriteria-check-error=bool
       Detecting failover using link error percentage

   --failurecriteria-error=int
       The error percentage for link error percentage check method

   --failurecriteria-check-beacon=bool
       Detecting failover using the beacon

   --nicteaming-policy=nicteaming-policy
       Nic-Teaming policy.

   --nicteaming-reverse-policy=bool
       Apply the teaming policy to inbound frames as well.

   --nicteaming-notify-switch=bool
       Notify switches when detects a link failure.

   --nicteaming-rollingorder=bool
       Whether or not to use rolling failover.

   --offloadcaps-csum-offload=bool
       Checksum offload

   --offloadcaps-tcp-segment=bool
       TCP segment offload

   --offloadcaps-zerocopy-xmit=bool
       Scatter gather

   --portgroup-vlanid=int
       VLAN identifier.

   --portgroup-name=string
       New portgroup identifier.
[[Category: Vimsh]]</text>
    <sha1>8380140d9e3b649dfb6166b745d9a46f42c7f497</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>VMGL</title>
  <ns>0</ns>
  <id>58</id>
  <revision>
    <id>267</id>
    <parentid>160</parentid>
    <timestamp>2008-12-16T07:09:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="440" xml:space="preserve">==== VMGL ====

OpenGL apps running inside a VM use VMGL to obtain graphics hardware acceleration. VMGL supports VMware, Xen PV and HVM, qemu, and KVM VMs; X11-based OS such as Linux, FreeBSD and OpenSolaris; and ATI, Nvidia and Intel GPUs. 

http://sourceforge.net/projects/vmgl/

==== related articles ====

* [ http://www.usenix.org/events/wiov08/tech/full_papers/dowty/dowty.pdf GPU Virtualization on VMware’s Hosted I/O Architecture]</text>
    <sha1>a205676f9ec54650fd486c2276d940884bd17ea2</sha1>
  </revision>
  <revision>
    <id>268</id>
    <parentid>267</parentid>
    <timestamp>2008-12-16T07:09:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="439" xml:space="preserve">==== VMGL ====

OpenGL apps running inside a VM use VMGL to obtain graphics hardware acceleration. VMGL supports VMware, Xen PV and HVM, qemu, and KVM VMs; X11-based OS such as Linux, FreeBSD and OpenSolaris; and ATI, Nvidia and Intel GPUs. 

http://sourceforge.net/projects/vmgl/

==== related articles ====

* [http://www.usenix.org/events/wiov08/tech/full_papers/dowty/dowty.pdf GPU Virtualization on VMware’s Hosted I/O Architecture]</text>
    <sha1>3a364e5dd868d9eb2b68abb9f773718ad1be87ab</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/portgroup unsetpolicy</title>
  <ns>0</ns>
  <id>120</id>
  <revision>
    <id>269</id>
    <timestamp>2008-12-16T07:23:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/portgroup_unsetpolicy ==== Usage: portgroup_unsetpolicy vswitch portgroup  Unset all network policies on a portgroup. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="160" xml:space="preserve">==== vimsh hostsvc/net/portgroup_unsetpolicy ====
Usage: portgroup_unsetpolicy vswitch portgroup

Unset all network policies on a portgroup.
[[Category: Vimsh]]</text>
    <sha1>29f321ab9fc036e476fac3d018cdacf2a7ca2d46</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/query networkhint</title>
  <ns>0</ns>
  <id>121</id>
  <revision>
    <id>270</id>
    <timestamp>2008-12-16T07:25:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/query_networkhint ==== Usage: query_networkhint [OPTIONS]  Request network hint information for one or more PhysicalNics.  Options:    --pnic-names=string_list      ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="242" xml:space="preserve">==== vimsh hostsvc/net/query_networkhint ====
Usage: query_networkhint [OPTIONS]

Request network hint information for one or more PhysicalNics.

Options:
   --pnic-names=string_list
       List of physical nics to query.

[[Category: Vimsh]]</text>
    <sha1>8558d4f9063276ccf4aa80b153081bb8672a5034</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/refresh</title>
  <ns>0</ns>
  <id>122</id>
  <revision>
    <id>271</id>
    <timestamp>2008-12-16T07:25:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/refresh ==== Usage: refresh  Refresh network system properties.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="107" xml:space="preserve">==== vimsh hostsvc/net/refresh ====
Usage: refresh

Refresh network system properties.

[[Category: Vimsh]]</text>
    <sha1>aa464a5f09f38e24659599d2ea649dfa11e56d23</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/route info</title>
  <ns>0</ns>
  <id>123</id>
  <revision>
    <id>272</id>
    <timestamp>2008-12-16T07:26:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/route_info ==== Usage: route_info  Get the IP route configuration. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">==== vimsh hostsvc/net/route_info ====
Usage: route_info

Get the IP route configuration.
[[Category: Vimsh]]</text>
    <sha1>df0828e5516d55b1c835424cc8d9871e998260d7</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/route set</title>
  <ns>0</ns>
  <id>124</id>
  <revision>
    <id>273</id>
    <timestamp>2008-12-16T07:27:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/route_set ==== Usage: route_set [OPTIONS]  Sets the IP route configuration.  Options:    --route-gateway=string        IP address.     --route-gateway-device=console...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="288" xml:space="preserve">==== vimsh hostsvc/net/route_set ====
Usage: route_set [OPTIONS]

Sets the IP route configuration.

Options:
   --route-gateway=string
       IP address.

   --route-gateway-device=console_virtual_nic
       The service console NIC which is the default gateway device.
[[Category: Vimsh]]</text>
    <sha1>c57851de1dba00cdc5f661e55cb4cf4f3766b330</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vnic add</title>
  <ns>0</ns>
  <id>125</id>
  <revision>
    <id>274</id>
    <timestamp>2008-12-16T07:29:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vnic_add ==== Usage: vnic_add [OPTIONS] portgroup  Adds a virtual NIC to the system.  Options:    --ip-dhcp=bool        Enables or disables DHCP configuration.     -...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="297" xml:space="preserve">==== vimsh hostsvc/net/vnic_add ====
Usage: vnic_add [OPTIONS] portgroup

Adds a virtual NIC to the system.

Options:
   --ip-dhcp=bool
       Enables or disables DHCP configuration.

   --ip-address=ip_address
       IP address.

   --ip-subnet=ip_address
       Subnet mask.

[[Category: Vimsh]]</text>
    <sha1>c773371b10d7d733351a6faf105932d097722be6</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vnic info</title>
  <ns>0</ns>
  <id>126</id>
  <revision>
    <id>275</id>
    <timestamp>2008-12-16T07:29:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vnic_info ==== Usage: vnic_info [vnic]  Gets information about virtual NICs.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="120" xml:space="preserve">==== vimsh hostsvc/net/vnic_info ====
Usage: vnic_info [vnic]

Gets information about virtual NICs.

[[Category: Vimsh]]</text>
    <sha1>7f02c233e1b59999ba8f51aa2bdbfee0a20a340b</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vnic remove</title>
  <ns>0</ns>
  <id>127</id>
  <revision>
    <id>276</id>
    <timestamp>2008-12-16T07:30:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vnic_remove ==== Usage: vnic_remove vnic  Removes a virtual NIC.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">==== vimsh hostsvc/net/vnic_remove ====
Usage: vnic_remove vnic

Removes a virtual NIC.

[[Category: Vimsh]]</text>
    <sha1>fef55781f1d6ef502c4fa7680977124b5b1d5dc3</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vnic set</title>
  <ns>0</ns>
  <id>128</id>
  <revision>
    <id>277</id>
    <timestamp>2008-12-16T07:31:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vnic_set ==== Usage: vnic_set [OPTIONS] vnic  Reconfigures a virtual NIC on the system.  Options:    --vnic-mac=string        Sets the mac address of this vnic.     ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="363" xml:space="preserve">==== vimsh hostsvc/net/vnic_set ====
Usage: vnic_set [OPTIONS] vnic

Reconfigures a virtual NIC on the system.

Options:
   --vnic-mac=string
       Sets the mac address of this vnic.

   --ip-dhcp=bool
       Enables or disables DHCP configuration.

   --ip-address=ip_address
       IP address.

   --ip-subnet=ip_address
       Subnet mask.
[[Category: Vimsh]]</text>
    <sha1>596a44939253542934b9dca7f8f102f0b64ba190</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch add</title>
  <ns>0</ns>
  <id>129</id>
  <revision>
    <id>278</id>
    <timestamp>2008-12-16T07:32:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_add ==== Usage: vswitch_add vswitch  Adds a virtual switch with the given name. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="130" xml:space="preserve">==== vimsh hostsvc/net/vswitch_add ====
Usage: vswitch_add vswitch

Adds a virtual switch with the given name.
[[Category: Vimsh]]</text>
    <sha1>625d3c59b136271a9437a8ca39b74d1657e44c40</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch info</title>
  <ns>0</ns>
  <id>130</id>
  <revision>
    <id>279</id>
    <timestamp>2008-12-16T07:33:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_info ==== Usage: vswitch_info [vswitch]  Displays information about virtual switches.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="137" xml:space="preserve">==== vimsh hostsvc/net/vswitch_info ====
Usage: vswitch_info [vswitch]

Displays information about virtual switches.

[[Category: Vimsh]]</text>
    <sha1>1746bf3ec3c87a02bab96a7e06ac1d78a462e600</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch pnicinfo</title>
  <ns>0</ns>
  <id>131</id>
  <revision>
    <id>280</id>
    <timestamp>2008-12-16T07:34:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_pnicinfo ==== Usage: vswitch_pnicinfo vswitch  Displays information about the physical NICs bridged to a virtual switch.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">==== vimsh hostsvc/net/vswitch_pnicinfo ====
Usage: vswitch_pnicinfo vswitch

Displays information about the physical NICs bridged to a virtual switch.

[[Category: Vimsh]]</text>
    <sha1>8fd5147761d49166e6fad6f9f55bbed099b04da1</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch remove</title>
  <ns>0</ns>
  <id>132</id>
  <revision>
    <id>281</id>
    <timestamp>2008-12-16T07:35:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_remove ==== Usage: vswitch_remove vswitch  Removes a virtual switch.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="120" xml:space="preserve">==== vimsh hostsvc/net/vswitch_remove ====
Usage: vswitch_remove vswitch

Removes a virtual switch.

[[Category: Vimsh]]</text>
    <sha1>e1f4f972571217d9583c31084dfeeeeeeb578c0e</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch setautobridge</title>
  <ns>0</ns>
  <id>133</id>
  <revision>
    <id>282</id>
    <timestamp>2008-12-16T07:36:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_setautobridge ==== Usage: vswitch_setautobridge vswitch  Sets the bridge for this virtual switch to be the automatic bridge.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="176" xml:space="preserve">==== vimsh hostsvc/net/vswitch_setautobridge ====
Usage: vswitch_setautobridge vswitch

Sets the bridge for this virtual switch to be the automatic bridge.

[[Category: Vimsh]]</text>
    <sha1>0fc764c0c51aa0b8fa067b08c3f09333660cb9bd</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch setbondbridge</title>
  <ns>0</ns>
  <id>134</id>
  <revision>
    <id>283</id>
    <timestamp>2008-12-16T07:37:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_setbondbridge ==== Usage: vswitch_setbondbridge [OPTIONS] vswitch  Sets the bridge for this virtual switch to be the bonded NIC bridge.  Options:    --vsbrid...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="395" xml:space="preserve">==== vimsh hostsvc/net/vswitch_setbondbridge ====
Usage: vswitch_setbondbridge [OPTIONS] vswitch

Sets the bridge for this virtual switch to be the bonded NIC bridge.

Options:
   --vsbridge-bond-pnics=physical_nic_list
       List of physical NIC to which bond bridge is configured.

   --vsbridge-bond-beacon-interval=int
       Probe interval for beacon.  Zero to disable.
[[Category: Vimsh]]</text>
    <sha1>1936099257244cbea1ab00797c20df42eab705d5</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch setnumports</title>
  <ns>0</ns>
  <id>135</id>
  <revision>
    <id>284</id>
    <timestamp>2008-12-16T07:38:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_setnumports ==== Usage: vswitch_setnumports vswitch ports  Sets the number of ports on the virtual switch. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="157" xml:space="preserve">==== vimsh hostsvc/net/vswitch_setnumports ====
Usage: vswitch_setnumports vswitch ports

Sets the number of ports on the virtual switch.
[[Category: Vimsh]]</text>
    <sha1>20b3a0516facc785caa65096e07cd84acaf9f850</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch setpolicy</title>
  <ns>0</ns>
  <id>136</id>
  <revision>
    <id>285</id>
    <timestamp>2008-12-16T07:39:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_setpolicy ====  Usage: vswitch_setpolicy [OPTIONS] vswitch  Changes the policies of a virtual switch.  Options:    --securepolicy-promisc=bool        Allow p...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1909" xml:space="preserve">==== vimsh hostsvc/net/vswitch_setpolicy ====

Usage: vswitch_setpolicy [OPTIONS] vswitch

Changes the policies of a virtual switch.

Options:
   --securepolicy-promisc=bool
       Allow promiscuous mode.

   --securepolicy-macchange=bool
       Allow MAC address to be changed.

   --securepolicy-forgedxmit=bool
       Allow forged transmits.

   --shapingpolicy-enabled=bool
       Enabled shaper.

   --shapingpolicy-average-bandwidth=int
       Average bandwidth.

   --shapingpolicy-peak-bandwidth=int
       Peak bandwidth.

   --shapingpolicy-burst-size=int
       Burst size.

   --nicorderpolicy-active=vmnic_list
       List of active NICs.

   --nicorderpolicy-standby=vmnic_list
       Order in which failover should occur.

   --failurecriteria-check-speed=failurecriteria-check-speed
       Detecting failover using link speed check

   --failurecriteria-speed=int
       The speed for link speed check method

   --failurecriteria-check-duplex=bool
       Detecting failover using link duplex check

   --failurecriteria-duplex=bool
       The duplexity for link duplex check method

   --failurecriteria-check-error=bool
       Detecting failover using link error percentage

   --failurecriteria-error=int
       The error percentage for link error percentage check method

   --failurecriteria-check-beacon=bool
       Detecting failover using the beacon

   --nicteaming-policy=nicteaming-policy
       Nic-Teaming policy.

   --nicteaming-reverse-policy=bool
       Apply the teaming policy to inbound frames as well.

   --nicteaming-notify-switch=bool
       Notify switches when detects a link failure.

   --nicteaming-rollingorder=bool
       Whether or not to use rolling failover.

   --offloadcaps-csum-offload=bool
       Checksum offload

   --offloadcaps-tcp-segment=bool
       TCP segment offload

   --offloadcaps-zerocopy-xmit=bool
       Scatter gather
[[Category: Vimsh]]</text>
    <sha1>a70e0979a56fc90e507be6576994a9f7da68b49a</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch setsimplebridge</title>
  <ns>0</ns>
  <id>137</id>
  <revision>
    <id>286</id>
    <timestamp>2008-12-16T07:41:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_setsimplebridge ==== Usage: vswitch_setsimplebridge vswitch pnic  Sets the bridge for this virtual switch to be the simple, single NIC bridge. [[Category: Vi...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="193" xml:space="preserve">==== vimsh hostsvc/net/vswitch_setsimplebridge ====
Usage: vswitch_setsimplebridge vswitch pnic

Sets the bridge for this virtual switch to be the simple, single NIC bridge.
[[Category: Vimsh]]</text>
    <sha1>3ea9a7c117cb4b98e2cd59041d4edcf63858e8cd</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/vswitch unsetbridge</title>
  <ns>0</ns>
  <id>138</id>
  <revision>
    <id>287</id>
    <timestamp>2008-12-16T07:42:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/vswitch_unsetbridge ==== Usage: vswitch_unsetbridge vswitch  Unsets the bridge for this virtual switch. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="146" xml:space="preserve">==== vimsh hostsvc/net/vswitch_unsetbridge ====
Usage: vswitch_unsetbridge vswitch

Unsets the bridge for this virtual switch.
[[Category: Vimsh]]</text>
    <sha1>dc6a3f8e8c85d73f3ff064bec2739ec99503d28c</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/mockup/</title>
  <ns>0</ns>
  <id>139</id>
  <revision>
    <id>288</id>
    <timestamp>2008-12-16T07:45:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/mockup/ ====   clear                    pnic_remove                pnic_add              pnic_setactuallinkspeed      [[hostsvc/net/mockup/clear]]                [[h...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="300" xml:space="preserve">==== vimsh hostsvc/net/mockup/ ====

 clear                    pnic_remove              
 pnic_add              pnic_setactuallinkspeed  


 [[hostsvc/net/mockup/clear]]              
 [[hostsvc/net/mockup/pnic_add]]
 [[hostsvc/net/mockup/pnic_remove]]
 [[hostsvc/net/mockup/pnic_setactuallinkspeed]]</text>
    <sha1>13597787479bafe6af83c139ff912a1e48d351cc</sha1>
  </revision>
  <revision>
    <id>289</id>
    <parentid>288</parentid>
    <timestamp>2008-12-16T07:46:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="321" xml:space="preserve">==== vimsh hostsvc/net/mockup/ ====

 clear                    pnic_remove              
 pnic_add              pnic_setactuallinkspeed  


 [[hostsvc/net/mockup/clear]]              
 [[hostsvc/net/mockup/pnic_add]]
 [[hostsvc/net/mockup/pnic_remove]]
 [[hostsvc/net/mockup/pnic_setactuallinkspeed]]

[[Category: Vimsh]]</text>
    <sha1>c27d403a9fa752b801cd305bdd8f47a33aa3afde</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/mockup/clear</title>
  <ns>0</ns>
  <id>140</id>
  <revision>
    <id>290</id>
    <timestamp>2008-12-16T07:46:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/mockup/clear ==== Usage: clear  Clears the mockup implementation for host networking. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="128" xml:space="preserve">==== vimsh hostsvc/net/mockup/clear ====
Usage: clear

Clears the mockup implementation for host networking.
[[Category: Vimsh]]</text>
    <sha1>a36304be5137104860f440dc4c57006578d2de0d</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/mockup/pnic add</title>
  <ns>0</ns>
  <id>141</id>
  <revision>
    <id>291</id>
    <timestamp>2008-12-16T07:57:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/mockup/pnic_add ==== Usage: pnic_add [OPTIONS] pnic pci_id  Adds a virtual switch with the given name.  Options:    --linkspeed-mb=physical_nic_mb        The speed o...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="309" xml:space="preserve">==== vimsh hostsvc/net/mockup/pnic_add ====
Usage: pnic_add [OPTIONS] pnic pci_id

Adds a virtual switch with the given name.

Options:
   --linkspeed-mb=physical_nic_mb
       The speed of the physical NIC in MB.

   --linkspeed-duplex=bool
       The duplex setting of the physical NIC.

[[Category: Vimsh]]</text>
    <sha1>658c917c0aa37e0cbba240fe3a0864278135e229</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/mockup/pnic remove</title>
  <ns>0</ns>
  <id>142</id>
  <revision>
    <id>292</id>
    <timestamp>2008-12-16T07:58:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/mockup/pnic_remove ==== Usage: pnic_remove pnic  Removes a physical network interface card.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="135" xml:space="preserve">==== vimsh hostsvc/net/mockup/pnic_remove ====
Usage: pnic_remove pnic

Removes a physical network interface card.

[[Category: Vimsh]]</text>
    <sha1>55e654e9640c9e9844e66c516ead14eaf4cc472a</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/mockup/pnic setactuallinkspeed</title>
  <ns>0</ns>
  <id>143</id>
  <revision>
    <id>293</id>
    <timestamp>2008-12-16T07:59:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/mockup/pnic_setactuallinkspeed ==== Usage: pnic_setactuallinkspeed [OPTIONS] pnic  Sets and unsets the physical link speed configuration for a physical NIC.  Unsetti...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="466" xml:space="preserve">==== vimsh hostsvc/net/mockup/pnic_setactuallinkspeed ====
Usage: pnic_setactuallinkspeed [OPTIONS] pnic

Sets and unsets the physical link speed configuration for a physical
NIC.  Unsetting link speed effectively disconnects network connection.

To unset, don't specify any options.

Options:
   --linkspeed-mb=physical_nic_mb
       The speed of the physical NIC in MB.

   --linkspeed-duplex=bool
       The duplex setting of the physical NIC.
[[Category: Vimsh]]</text>
    <sha1>ae23743ca86b334bdb6dbdc20498874e4e3a820b</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/provider/</title>
  <ns>0</ns>
  <id>144</id>
  <revision>
    <id>294</id>
    <timestamp>2008-12-16T08:01:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/provider/ ====   test_abort   [[hostsvc/net/provider/test_abort]]  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">==== vimsh hostsvc/net/provider/ ====

 test_abort

 [[hostsvc/net/provider/test_abort]]

[[Category: Vimsh]]</text>
    <sha1>91286487facffea4095495d58b7f48984e1a1d2e</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Hostsvc/net/provider/test abort</title>
  <ns>0</ns>
  <id>145</id>
  <revision>
    <id>295</id>
    <timestamp>2008-12-16T08:01:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/net/provider/test_abort ==== Usage: test_abort  Test the abort transactional semantics of NetworkSystemProviderTrans.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="157" xml:space="preserve">==== vimsh hostsvc/net/provider/test_abort ====
Usage: test_abort

Test the abort transactional semantics of NetworkSystemProviderTrans.

[[Category: Vimsh]]</text>
    <sha1>202342b1232205b792081aa26574542350f46b11</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Vimsh: vmsvc/</title>
  <ns>0</ns>
  <id>46</id>
  <revision>
    <id>296</id>
    <parentid>191</parentid>
    <timestamp>2008-12-16T08:18:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3815" xml:space="preserve"> [/]$ vmsvc/
 acquiremksticket          get.configoption              power.off                 
 connect                       get.datastores                 power.on                  
 convert.toTemplate      get.disabledmethods        power.reboot              
 convert.toVm               get.environment              power.reset               
 createdummyvm          get.filelayout                   power.shutdown            
 destroy                       get.guest                         power.suspend             
 device.connection         get.guestheartbeatStatus  reload                    
 device.connusbdev       get.managedentitystatus   setscreenres              
 device.disconnusbdev   get.networks                    snapshot.create           
 device.diskadd             get.runtime                      snapshot.get              
 device.diskaddexisting  get.snapshotinfo               snapshot.remove           
 device.diskremove       get.summary                    snapshot.removeall        
 device.getdevices         get.tasklist                       snapshot.revert           
 device.toolsSyncSet      getallvms                        snapshot.setoption        
 device.vmiadd              gethostconstraints            tools.cancelinstall       
 device.vmiremove         login                              tools.install             
 devices.createnic           logout                            tools.upgrade             
 get.capability                message                        unregister                
 get.config                     power.getstate                upgrade                   
 get.config.cpuidmask     power.hibernate

 [[vmsvc/acquiremksticket]]              
 [[vmsvc/connect]]                  
 [[vmsvc/convert.toTemplate]]          
 [[vmsvc/convert.toVm]]               
 [[vmsvc/createdummyvm]]        
 [[vmsvc/destroy]]             
 [[vmsvc/device.connection]]               
 [[vmsvc/device.connusbdev]]            
 [[vmsvc/device.disconnusbdev]]       
 [[vmsvc/device.diskadd]]              
 [[vmsvc/device.diskaddexisting]]          
 [[vmsvc/device.diskremove]]     
 [[vmsvc/device.getdevices]]          
 [[vmsvc/device.toolsSyncSet]]
 [[vmsvc/device.vmiadd]] 
 [[vmsvc/device.vmiremove]]             
 [[vmsvc/devices.createnic]]         
 [[vmsvc/get.capability]]         
 [[vmsvc/get.config]]                   
 [[vmsvc/get.config.cpuidmask]]
 [[vmsvc/get.configoption]]       
 [[vmsvc/get.datastores]]                
 [[vmsvc/get.disabledmethods]]       
 [[vmsvc/get.environment]]           
 [[vmsvc/get.filelayout]]       
 [[vmsvc/get.guest]]        
 [[vmsvc/get.guestheartbeatStatus]]  
 [[vmsvc/get.managedentitystatus]]       
 [[vmsvc/get.networks]]         
 [[vmsvc/get.runtime]]          
 [[vmsvc/get.snapshotinfo]]     
 [[vmsvc/get.summary]]  
 [[vmsvc/get.tasklist]]      
 [[vmsvc/getallvms]]       
 [[vmsvc/gethostconstraints]]  
 [[vmsvc/login]]        
 [[vmsvc/logout]]           
 [[vmsvc/message]]    
 [[vmsvc/power.getstate]]      
 [[vmsvc/power.hibernate]]
 [[vmsvc/power.off]]                 
 [[vmsvc/power.on]]                  
 [[vmsvc/power.reboot]]              
 [[vmsvc/power.reset]]               
 [[vmsvc/power.shutdown]]            
 [[vmsvc/power.suspend]]             
 [[vmsvc/reload]]                    
 [[vmsvc/setscreenres]]              
 [[vmsvc/snapshot.create]]           
 [[vmsvc/snapshot.get]]              
 [[vmsvc/snapshot.remove]]           
 [[vmsvc/snapshot.removeall]]        
 [[vmsvc/snapshot.revert]]           
 [[vmsvc/snapshot.setoption]]        
 [[vmsvc/tools.cancelinstall]]       
 [[vmsvc/tools.install]]             
 [[vmsvc/tools.upgrade]]             
 [[vmsvc/unregister]]                
 [[vmsvc/upgrade]]                   


[[Category: Vimsh]]</text>
    <sha1>9e38202c17c2bf5b902b75fc00ad324081de0be7</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Vmsvc/get.runtime</title>
  <ns>0</ns>
  <id>146</id>
  <revision>
    <id>297</id>
    <timestamp>2008-12-16T08:19:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.runtime ==== Usage: get.runtime vmid  Get runtime information  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="103" xml:space="preserve">==== vimsh vmsvc/get.runtime ====
Usage: get.runtime vmid

Get runtime information

[[Category: Vimsh]]</text>
    <sha1>a1c7ce61c7e354c14daf54a7640f4f937bbb93d7</sha1>
  </revision>
  <revision>
    <id>299</id>
    <parentid>297</parentid>
    <timestamp>2008-12-16T08:26:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1194" xml:space="preserve">==== vimsh vmsvc/get.runtime ====
Usage: get.runtime vmid

Get runtime information


Use [[vmsvc/getallvms]] to retrieve the vmid

==== example output when vm is off ====
 vmsvc/get.runtime 4400
 Runtime information
 (vim.vm.RuntimeInfo) {
    dynamicType = &lt;unset&gt;, 
    host = 'vim.HostSystem:ha-host', 
    connectionState = "connected", 
    powerState = "poweredOff", 
    toolsInstallerMounted = false, 
    suspendTime = &lt;unset&gt;, 
    bootTime = &lt;unset&gt;, 
    suspendInterval = 0, 
    question = (vim.vm.QuestionInfo) null, 
    memoryOverhead = 71675904, 
    maxCpuUsage = 2392, 
    maxMemoryUsage = 256, 
    numMksConnections = 0, 
 }

==== example output when vm is on ====
vmsvc/get.runtime 7584
Runtime information
(vim.vm.RuntimeInfo) {
   dynamicType = &lt;unset&gt;, 
   host = 'vim.HostSystem:ha-host', 
   connectionState = "connected", 
   powerState = "poweredOn", 
   toolsInstallerMounted = false, 
   suspendTime = &lt;unset&gt;, 
   bootTime = "2008-12-13T12:04:27.476613+01:00", 
   suspendInterval = 0, 
   question = (vim.vm.QuestionInfo) null, 
   memoryOverhead = 87277568, 
   maxCpuUsage = 4186, 
   maxMemoryUsage = 384, 
   numMksConnections = 0, 
}

[[Category: Vimsh]]</text>
    <sha1>cbcb7ce7137681a991b4fc1458a15de1125e19a6</sha1>
  </revision>
  <revision>
    <id>300</id>
    <parentid>299</parentid>
    <timestamp>2008-12-16T08:26:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1211" xml:space="preserve">==== vimsh vmsvc/get.runtime ====
Usage: get.runtime vmid

Get runtime information


Use [[vmsvc/getallvms]] to retrieve the vmid

==== example output when vm is off ====
 vmsvc/get.runtime 4400
 Runtime information
 (vim.vm.RuntimeInfo) {
    dynamicType = &lt;unset&gt;, 
    host = 'vim.HostSystem:ha-host', 
    connectionState = "connected", 
    powerState = "poweredOff", 
    toolsInstallerMounted = false, 
    suspendTime = &lt;unset&gt;, 
    bootTime = &lt;unset&gt;, 
    suspendInterval = 0, 
    question = (vim.vm.QuestionInfo) null, 
    memoryOverhead = 71675904, 
    maxCpuUsage = 2392, 
    maxMemoryUsage = 256, 
    numMksConnections = 0, 
 }

==== example output when vm is on ====
 vmsvc/get.runtime 7584 
Runtime information
 (vim.vm.RuntimeInfo) {
    dynamicType = &lt;unset&gt;, 
    host = 'vim.HostSystem:ha-host', 
    connectionState = "connected", 
    powerState = "poweredOn", 
    toolsInstallerMounted = false, 
    suspendTime = &lt;unset&gt;, 
    bootTime = "2008-12-13T12:04:27.476613+01:00", 
    suspendInterval = 0, 
    question = (vim.vm.QuestionInfo) null, 
    memoryOverhead = 87277568, 
    maxCpuUsage = 4186, 
    maxMemoryUsage = 384, 
    numMksConnections = 0, 
 }

[[Category: Vimsh]]</text>
    <sha1>60b8727badb967293254a1a31bf75f0fb2d289d7</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Vmsvc/getallvms</title>
  <ns>0</ns>
  <id>147</id>
  <revision>
    <id>298</id>
    <timestamp>2008-12-16T08:21:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/getallvms ==== Usage: getallvms  Get the list of virtual machines on the host. [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="115" xml:space="preserve">==== vimsh vmsvc/getallvms ====
Usage: getallvms

Get the list of virtual machines on the host.
[[Category: Vimsh]]</text>
    <sha1>1953a5ed9bec5ddd60bd38da8662a07a1d6014c3</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Category:Vimsh</title>
  <ns>14</ns>
  <id>148</id>
  <revision>
    <id>301</id>
    <timestamp>2008-12-16T14:30:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: The [[vimsh]] category.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23" xml:space="preserve">The [[vimsh]] category.</text>
    <sha1>8da79261a0d2c2f0066f193e5de5316ee429952a</sha1>
  </revision>
</page>
<page arvcontinue="20081216061915|253">
  <title>Vmsvc/acquiremksticket</title>
  <ns>0</ns>
  <id>149</id>
  <revision>
    <id>302</id>
    <timestamp>2008-12-17T08:02:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vmsvc/acquiremksticket ==== Usage: acquiremksticket vmid  Acquire mks ticket for the vm with id vmid  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">==== vmsvc/acquiremksticket ====
Usage: acquiremksticket vmid

Acquire mks ticket for the vm with id vmid

[[Category: Vimsh]]</text>
    <sha1>dae96e32128cb5c07bce4973fbfb00f2515de352</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/acquiremksticket</title>
  <ns>0</ns>
  <id>149</id>
  <revision>
    <id>303</id>
    <parentid>302</parentid>
    <timestamp>2008-12-17T08:03:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="180" xml:space="preserve">==== vmsvc/acquiremksticket ====
Usage: acquiremksticket vmid

Acquire mks ticket for the vm with id vmid

You can use [[vmsvc/getallvms]] to retrieve the vmid

[[Category: Vimsh]]</text>
    <sha1>bfcc6f8ca31e3d61ebd9cad2bea15d3fcc68d197</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/connect</title>
  <ns>0</ns>
  <id>150</id>
  <revision>
    <id>304</id>
    <timestamp>2008-12-17T08:04:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/connect ==== Usage: connect [hostname] [port] [key] [cert] [product]  Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and a...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="423" xml:space="preserve">==== vimsh vmsvc/connect ====
Usage: connect [hostname] [port] [key] [cert] [product]

Connects to product (solo|vpxa|vpxd) listening at hostname on
TCP port port using a private key and a certificate.
By default product is 'solo', hostname is 'localhost'.
Port is 902.
private key is at /etc/vmware/ssl/rui.key
certificate is at /etc/vmware/ssl/rui.crt
To disable SSL, use an empty key or certificate.

[[Category: Vimsh]]</text>
    <sha1>165107a2d10e049591fedd7a476c7cf951877f52</sha1>
  </revision>
  <revision>
    <id>305</id>
    <parentid>304</parentid>
    <timestamp>2008-12-17T08:05:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>formatted text</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="432" xml:space="preserve">==== vimsh vmsvc/connect ====
Usage: connect [hostname] [port] [key] [cert] [product]

Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and a certificate.

By default product is 'solo', hostname is 'localhost'.

* Port is 902.
* private key is at /etc/vmware/ssl/rui.key
* certificate is at /etc/vmware/ssl/rui.crt

To disable SSL, use an empty key or certificate.

[[Category: Vimsh]]</text>
    <sha1>c8d349397aeb8ad7a2752d8b8ca00d3b8baf4c41</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/convert.toTemplate</title>
  <ns>0</ns>
  <id>151</id>
  <revision>
    <id>306</id>
    <timestamp>2008-12-17T08:07:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/convert.toTemplate ==== Usage: convert.toTemplate vmid  Convert the virtual machine to a template.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="136" xml:space="preserve">==== vimsh vmsvc/convert.toTemplate ====
Usage: convert.toTemplate vmid

Convert the virtual machine to a template.

[[Category: Vimsh]]</text>
    <sha1>9b7f08e33f2743105aa818a69a1607aa635db95e</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/convert.toVm</title>
  <ns>0</ns>
  <id>152</id>
  <revision>
    <id>307</id>
    <timestamp>2008-12-17T08:09:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/convert.toVM ==== Usage: convert.toVm vmid  Convert the template to a virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="124" xml:space="preserve">==== vimsh vmsvc/convert.toVM ====
Usage: convert.toVm vmid

Convert the template to a virtual machine.

[[Category: Vimsh]]</text>
    <sha1>4620ac70eb56f471f7e9da9b81a49f82c320fabf</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/createdummyvm</title>
  <ns>0</ns>
  <id>153</id>
  <revision>
    <id>308</id>
    <timestamp>2008-12-17T08:10:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/createdummyvm ==== Usage: createdummyvm  Create a pre-configured dummy vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="112" xml:space="preserve">==== vimsh vmsvc/createdummyvm ====
Usage: createdummyvm

Create a pre-configured dummy vm.

[[Category: Vimsh]]</text>
    <sha1>03c0af962210b4579b9d7110f9e671d7ec55197b</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/destroy</title>
  <ns>0</ns>
  <id>154</id>
  <revision>
    <id>309</id>
    <timestamp>2008-12-17T08:11:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/destroy ==== Usage: destroy vmid  Deletes the vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="87" xml:space="preserve">==== vimsh vmsvc/destroy ====
Usage: destroy vmid

Deletes the vm.

[[Category: Vimsh]]</text>
    <sha1>b02a574bf02cdf023d681cecf8479c2dc6fee37b</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.connection</title>
  <ns>0</ns>
  <id>155</id>
  <revision>
    <id>310</id>
    <timestamp>2008-12-17T08:12:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.connection ==== Usage: device.connection vmid deviceKey connect  Connect/Disconnect the virtual device specified  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="157" xml:space="preserve">==== vimsh vmsvc/device.connection ====
Usage: device.connection vmid deviceKey connect

Connect/Disconnect the virtual device specified

[[Category: Vimsh]]</text>
    <sha1>b5b9bcf39beea10b230671f943af0b3605d97d89</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.connusbdev</title>
  <ns>0</ns>
  <id>156</id>
  <revision>
    <id>311</id>
    <timestamp>2008-12-17T08:13:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.connusbdev ==== Usage: device.connusbdev vmid usbid  Connect a USB device to this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="143" xml:space="preserve">==== vimsh vmsvc/device.connusbdev ====
Usage: device.connusbdev vmid usbid

Connect a USB device to this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>b4ea5607172f3006a09f8661ec027e5ba5263895</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.disconnusbdev</title>
  <ns>0</ns>
  <id>157</id>
  <revision>
    <id>312</id>
    <timestamp>2008-12-17T08:14:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.disconnusbdev ==== Usage: device.disconnusbdev vmid usbid  Remove a disk from this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">==== vimsh vmsvc/device.disconnusbdev ====
Usage: device.disconnusbdev vmid usbid

Remove a disk from this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>7f03207fc0d075017e5194e23ac286e4981056d8</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.diskadd</title>
  <ns>0</ns>
  <id>158</id>
  <revision>
    <id>313</id>
    <timestamp>2008-12-17T08:15:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.diskadd ==== Usage: device.diskadd vmid size controller number unit number datastore  Add a disk to this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="166" xml:space="preserve">==== vimsh vmsvc/device.diskadd ====
Usage: device.diskadd vmid size controller number unit number datastore

Add a disk to this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>e5c22e0e2a448338d7fbbe9e3b9281135a010de0</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.diskaddexisting</title>
  <ns>0</ns>
  <id>159</id>
  <revision>
    <id>314</id>
    <timestamp>2008-12-17T08:16:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.diskaddexisting ==== Usage: device.diskaddexisting vmid disk file controller number unit number  Add an existing disk to this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="187" xml:space="preserve">==== vimsh vmsvc/device.diskaddexisting ====
Usage: device.diskaddexisting vmid disk file controller number unit number

Add an existing disk to this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>e5521572d8a37e839a0b7874a2141543503afae3</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.diskremove</title>
  <ns>0</ns>
  <id>160</id>
  <revision>
    <id>315</id>
    <timestamp>2008-12-17T08:17:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.diskremove ==== Usage: device.diskremove vmid controller number unit number delete file  Remove a disk from this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="174" xml:space="preserve">==== vimsh vmsvc/device.diskremove ====
Usage: device.diskremove vmid controller number unit number delete file

Remove a disk from this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>fff57d355a5d2f80852fea4cbb745bc80c552d2a</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.getdevices</title>
  <ns>0</ns>
  <id>161</id>
  <revision>
    <id>316</id>
    <timestamp>2008-12-17T08:18:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.getdevices ==== Usage: device.getdevices vmid  Retrieves and displays the virtual devices for the vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="146" xml:space="preserve">==== vimsh vmsvc/device.getdevices ====
Usage: device.getdevices vmid

Retrieves and displays the virtual devices for the vm.

[[Category: Vimsh]]</text>
    <sha1>bba3777c616d6de9d7b1136ee34e2908f504ad8c</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.toolsSyncSet</title>
  <ns>0</ns>
  <id>162</id>
  <revision>
    <id>317</id>
    <timestamp>2008-12-17T08:19:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.toolsSyncSet ==== Usage: device.toolsSyncSet vmid new state  Set whether tools sync to host is enabled for the virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">==== vimsh vmsvc/device.toolsSyncSet ====
Usage: device.toolsSyncSet vmid new state

Set whether tools sync to host is enabled for the virtual machine.

[[Category: Vimsh]]</text>
    <sha1>b5c84280e6b31399c7b2446e4fdcab840b20f5fe</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.vmiadd</title>
  <ns>0</ns>
  <id>163</id>
  <revision>
    <id>318</id>
    <timestamp>2008-12-17T08:20:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.vmiadd ==== Usage: device.vmiadd vmid  Add the VMI ROM to the virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="123" xml:space="preserve">==== vimsh vmsvc/device.vmiadd ====
Usage: device.vmiadd vmid

Add the VMI ROM to the virtual machine.

[[Category: Vimsh]]</text>
    <sha1>3c08e4ff53e1c13e5c44595cd748ce2f5cc024a4</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/device.vmiremove</title>
  <ns>0</ns>
  <id>164</id>
  <revision>
    <id>319</id>
    <timestamp>2008-12-17T08:21:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/device.vmiremore ==== Usage: device.vmiremove vmid  Remove the VMI ROM from the virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== vimsh vmsvc/device.vmiremore ====
Usage: device.vmiremove vmid

Remove the VMI ROM from the virtual machine.

[[Category: Vimsh]]</text>
    <sha1>6246dd7da95993029fe41df7bbb088e478f787a9</sha1>
  </revision>
  <revision>
    <id>320</id>
    <parentid>319</parentid>
    <timestamp>2008-12-17T08:21:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== vimsh vmsvc/device.vmiremove ====
Usage: device.vmiremove vmid

Remove the VMI ROM from the virtual machine.

[[Category: Vimsh]]</text>
    <sha1>13f88def716086a8905052574e0f4ebbb08ad676</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/devices.createnic</title>
  <ns>0</ns>
  <id>165</id>
  <revision>
    <id>321</id>
    <timestamp>2008-12-17T08:23:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/devices.createnic ==== Usage: devices.createnic vmid unit number type network  Add a NIC to this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">==== vimsh vmsvc/devices.createnic ====
Usage: devices.createnic vmid unit number type network

Add a NIC to this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>2d042c9107ac0e652d1084bed28dc05730ef2772</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.capability</title>
  <ns>0</ns>
  <id>166</id>
  <revision>
    <id>322</id>
    <timestamp>2008-12-17T08:24:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.capability ==== Usage: get.capability vmid  Get list of capabilities for virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="131" xml:space="preserve">==== vimsh vmsvc/get.capability ====
Usage: get.capability vmid

Get list of capabilities for virtual machine.

[[Category: Vimsh]]</text>
    <sha1>dae7f7005c3641759ecbeffd069ae7598b15ca49</sha1>
  </revision>
  <revision>
    <id>343</id>
    <parentid>322</parentid>
    <timestamp>2008-12-17T10:52:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1069" xml:space="preserve">==== vimsh vmsvc/get.capability ====
Usage: get.capability vmid

Get list of capabilities for virtual machine.

==== Example output ====
 [/]$ vmsvc/get.capability 4400
 (vim.vm.Capability) {
    dynamicType = &lt;unset&gt;,
    snapshotOperationsSupported = true,
    multipleSnapshotsSupported = true,
    snapshotConfigSupported = true,
    poweredOffSnapshotsSupported = true,
    memorySnapshotsSupported = true,
    revertToSnapshotSupported = true,
    quiescedSnapshotsSupported = true,
    disableSnapshotsSupported = false,
    lockSnapshotsSupported = false,
    consolePreferencesSupported = true,
    cpuFeatureMaskSupported = true,
    s1AcpiManagementSupported = true,
    settingScreenResolutionSupported = false,
    toolsAutoUpdateSupported = true,
    vmNpivWwnSupported = true,
    npivWwnOnNonRdmVmSupported = false,
    swapPlacementSupported = true,
    toolsSyncTimeSupported = true,
    virtualMmuUsageSupported = true,
    diskSharesSupported = true,
    bootOptionsSupported = true,
    settingVideoRamSizeSupported = true,
 }


[[Category: Vimsh]]</text>
    <sha1>71e043350241882fea19c3bd65c439d109196ebf</sha1>
  </revision>
  <revision>
    <id>344</id>
    <parentid>343</parentid>
    <timestamp>2008-12-17T10:53:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1123" xml:space="preserve">==== vimsh vmsvc/get.capability ====
Usage: get.capability vmid

Get list of capabilities for virtual machine.

You can use [[vmsvc/getallvms]] to retrieve the vmid

==== Example output ====
 [/]$ vmsvc/get.capability 4400
 (vim.vm.Capability) {
    dynamicType = &lt;unset&gt;,
    snapshotOperationsSupported = true,
    multipleSnapshotsSupported = true,
    snapshotConfigSupported = true,
    poweredOffSnapshotsSupported = true,
    memorySnapshotsSupported = true,
    revertToSnapshotSupported = true,
    quiescedSnapshotsSupported = true,
    disableSnapshotsSupported = false,
    lockSnapshotsSupported = false,
    consolePreferencesSupported = true,
    cpuFeatureMaskSupported = true,
    s1AcpiManagementSupported = true,
    settingScreenResolutionSupported = false,
    toolsAutoUpdateSupported = true,
    vmNpivWwnSupported = true,
    npivWwnOnNonRdmVmSupported = false,
    swapPlacementSupported = true,
    toolsSyncTimeSupported = true,
    virtualMmuUsageSupported = true,
    diskSharesSupported = true,
    bootOptionsSupported = true,
    settingVideoRamSizeSupported = true,
 }


[[Category: Vimsh]]</text>
    <sha1>a5d07270c45dbce8728b20b5ad97e3d3cc4c4650</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.config</title>
  <ns>0</ns>
  <id>167</id>
  <revision>
    <id>323</id>
    <timestamp>2008-12-17T08:24:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.config ==== Usage: get.config vmid  Retrieves and displays the configuration object for the vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="137" xml:space="preserve">==== vimsh vmsvc/get.config ====
Usage: get.config vmid

Retrieves and displays the configuration object for the vm.

[[Category: Vimsh]]</text>
    <sha1>b7b67576d042e727bcf4ef9d5da49c36de2544c8</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.config.cpuidmask</title>
  <ns>0</ns>
  <id>168</id>
  <revision>
    <id>324</id>
    <timestamp>2008-12-17T08:25:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.config.cpuidmask ==== Usage: get.config.cpuidmask vmid  Retrieves and displays the cpu id masks for this virtual machine  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="162" xml:space="preserve">==== vimsh vmsvc/get.config.cpuidmask ====
Usage: get.config.cpuidmask vmid

Retrieves and displays the cpu id masks for this virtual machine

[[Category: Vimsh]]</text>
    <sha1>58e632f5e98e309f6c1dcccd161d42f968c52dc0</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.configoption</title>
  <ns>0</ns>
  <id>169</id>
  <revision>
    <id>325</id>
    <timestamp>2008-12-17T08:26:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.configoption ==== Usage: get.configoption vmid  Get the configuration options for this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="145" xml:space="preserve">==== vimsh vmsvc/get.configoption ====
Usage: get.configoption vmid

Get the configuration options for this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>9e02e64ec8f8eac9a374563af017f075e80747e2</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.datastores</title>
  <ns>0</ns>
  <id>170</id>
  <revision>
    <id>326</id>
    <timestamp>2008-12-17T08:27:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.datastore ==== Usage: get.datastores vmid  Show the list of datastores for this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="138" xml:space="preserve">==== vimsh vmsvc/get.datastore ====
Usage: get.datastores vmid

Show the list of datastores for this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>36c528f099e7d8cab4077d774e21e030d680db3f</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.disabledmethods</title>
  <ns>0</ns>
  <id>171</id>
  <revision>
    <id>327</id>
    <timestamp>2008-12-17T08:28:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.disabledmethods ==== Usage: get.disabledmethods vmid  Show the list of disabled methods on the virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="153" xml:space="preserve">==== vimsh vmsvc/get.disabledmethods ====
Usage: get.disabledmethods vmid

Show the list of disabled methods on the virtual machine.

[[Category: Vimsh]]</text>
    <sha1>22fae9f6d744288ebe463cb0bb8d8d1ac730d30c</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.environment</title>
  <ns>0</ns>
  <id>172</id>
  <revision>
    <id>328</id>
    <timestamp>2008-12-17T08:29:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.environment ==== Usage: get.environment vmid  Retrieves the vm's environment browser.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="127" xml:space="preserve">==== vimsh vmsvc/get.environment ====
Usage: get.environment vmid

Retrieves the vm's environment browser.

[[Category: Vimsh]]</text>
    <sha1>a99a94f1d82a84f0e4cdd06bd3a2884469c6e54e</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.filelayout</title>
  <ns>0</ns>
  <id>173</id>
  <revision>
    <id>329</id>
    <timestamp>2008-12-17T08:30:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.filelayout ==== Usage: get.filelayout vmid  Show the list of files for this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== vimsh vmsvc/get.filelayout ====
Usage: get.filelayout vmid

Show the list of files for this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>299ca8071a3ba583a9d879f2545d90ac8090df11</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.guest</title>
  <ns>0</ns>
  <id>174</id>
  <revision>
    <id>330</id>
    <timestamp>2008-12-17T08:31:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.guest ==== Usage: get.guest vmid  Get guest information  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="97" xml:space="preserve">==== vimsh vmsvc/get.guest ====
Usage: get.guest vmid

Get guest information

[[Category: Vimsh]]</text>
    <sha1>f63f0e034832c8d03845ff46d40d8076ee89b576</sha1>
  </revision>
  <revision>
    <id>347</id>
    <parentid>330</parentid>
    <timestamp>2008-12-17T10:58:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1171" xml:space="preserve">==== vimsh vmsvc/get.guest ====
Usage: get.guest vmid

Get guest information

==== Example output ====
 [/]$ vmsvc/get.guest 4400 
 Guest information:
 
 (vim.vm.GuestInfo) {
    dynamicType = &lt;unset&gt;,
    toolsStatus = "toolsOk",
    toolsVersion = "103908",
    guestId = "ubuntuGuest",
    guestFamily = "linuxGuest",
    guestFullName = "Ubuntu Linux (32-bit)",
    hostName = "vitoolkit",
    ipAddress = "10.10.10.10",
    net = (vim.vm.GuestInfo.NicInfo) [
       (vim.vm.GuestInfo.NicInfo) {
          dynamicType = &lt;unset&gt;,
          network = "Virtual Machines Network",
          ipAddress = (string) [
             "10.10.10.10"
          ],
          macAddress = "00:0c:18:4e:13:27",
          connected = true,
          deviceConfigId = 4000,
       } 
    ],
    disk = (vim.vm.GuestInfo.DiskInfo) [
       (vim.vm.GuestInfo.DiskInfo) {
          dynamicType = &lt;unset&gt;,
          diskPath = "/",
          capacity = 30027378176,
          freeSpace = 10655812096,
       }
    ], 
    screen = (vim.vm.GuestInfo.ScreenInfo) {
       dynamicType = &lt;unset&gt;,
       width = 0,
       height = 0,
    },
    guestState = "running",
 }


[[Category: Vimsh]]</text>
    <sha1>e7967066edfe5ddaef8104eeef80d9eeb3b5bffe</sha1>
  </revision>
  <revision>
    <id>348</id>
    <parentid>347</parentid>
    <timestamp>2008-12-17T10:59:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1172" xml:space="preserve">==== vimsh vmsvc/get.guest ====
Usage: get.guest vmid

Get guest information

==== Example output ====
 [/]$ vmsvc/get.guest 4400 
 Guest information:
 
 (vim.vm.GuestInfo) {
    dynamicType = &lt;unset&gt;,
    toolsStatus = "toolsOk",
    toolsVersion = "103908",
    guestId = "ubuntuGuest",
    guestFamily = "linuxGuest",
    guestFullName = "Ubuntu Linux (32-bit)",
    hostName = "vi-toolkit",
    ipAddress = "10.10.10.10",
    net = (vim.vm.GuestInfo.NicInfo) [
       (vim.vm.GuestInfo.NicInfo) {
          dynamicType = &lt;unset&gt;,
          network = "Virtual Machines Network",
          ipAddress = (string) [
             "10.10.10.10"
          ],
          macAddress = "00:0c:18:4e:13:27",
          connected = true,
          deviceConfigId = 4000,
       } 
    ],
    disk = (vim.vm.GuestInfo.DiskInfo) [
       (vim.vm.GuestInfo.DiskInfo) {
          dynamicType = &lt;unset&gt;,
          diskPath = "/",
          capacity = 30027378176,
          freeSpace = 10655812096,
       }
    ], 
    screen = (vim.vm.GuestInfo.ScreenInfo) {
       dynamicType = &lt;unset&gt;,
       width = 0,
       height = 0,
    },
    guestState = "running",
 }


[[Category: Vimsh]]</text>
    <sha1>8897d043399fcbad842ad1cdf10d3222e7c2e3a6</sha1>
  </revision>
  <revision>
    <id>349</id>
    <parentid>348</parentid>
    <timestamp>2008-12-17T11:00:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1226" xml:space="preserve">==== vimsh vmsvc/get.guest ====
Usage: get.guest vmid

Get guest information

You can use [[vmsvc/getallvms]] to retrieve the vmid

==== Example output ====
 [/]$ vmsvc/get.guest 4400 
 Guest information:
 
 (vim.vm.GuestInfo) {
    dynamicType = &lt;unset&gt;,
    toolsStatus = "toolsOk",
    toolsVersion = "103908",
    guestId = "ubuntuGuest",
    guestFamily = "linuxGuest",
    guestFullName = "Ubuntu Linux (32-bit)",
    hostName = "vi-toolkit",
    ipAddress = "10.10.10.10",
    net = (vim.vm.GuestInfo.NicInfo) [
       (vim.vm.GuestInfo.NicInfo) {
          dynamicType = &lt;unset&gt;,
          network = "Virtual Machines Network",
          ipAddress = (string) [
             "10.10.10.10"
          ],
          macAddress = "00:0c:18:4e:13:27",
          connected = true,
          deviceConfigId = 4000,
       } 
    ],
    disk = (vim.vm.GuestInfo.DiskInfo) [
       (vim.vm.GuestInfo.DiskInfo) {
          dynamicType = &lt;unset&gt;,
          diskPath = "/",
          capacity = 30027378176,
          freeSpace = 10655812096,
       }
    ], 
    screen = (vim.vm.GuestInfo.ScreenInfo) {
       dynamicType = &lt;unset&gt;,
       width = 0,
       height = 0,
    },
    guestState = "running",
 }


[[Category: Vimsh]]</text>
    <sha1>d879cb3d2601bcf7059daa5d5e6f7dbbdd1d8a17</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.guestheartbeatStatus</title>
  <ns>0</ns>
  <id>175</id>
  <revision>
    <id>331</id>
    <timestamp>2008-12-17T08:32:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.guestheartbeatStatus ==== Usage: get.guestheartbeatStatus vmid  Show the guest heartbeat status for this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">==== vimsh vmsvc/get.guestheartbeatStatus ====
Usage: get.guestheartbeatStatus vmid

Show the guest heartbeat status for this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>ccea90bac76b30b148f5b9822b230aa4a6834094</sha1>
  </revision>
  <revision>
    <id>339</id>
    <parentid>331</parentid>
    <timestamp>2008-12-17T09:57:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="240" xml:space="preserve">==== vimsh vmsvc/get.guestheartbeatStatus ====
Usage: get.guestheartbeatStatus vmid

Show the guest heartbeat status for this virtual machine.


==== example output ====
 [/]$ vmsvc/get.guestheartbeatStatus 4400
 green


[[Category: Vimsh]]</text>
    <sha1>a81ffaaf3b35f6af633d859cb83663e2280aa358</sha1>
  </revision>
  <revision>
    <id>346</id>
    <parentid>339</parentid>
    <timestamp>2008-12-17T10:54:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="293" xml:space="preserve">==== vimsh vmsvc/get.guestheartbeatStatus ====
Usage: get.guestheartbeatStatus vmid

Show the guest heartbeat status for this virtual machine.

You can use [[vmsvc/getallvms]] to retrieve the vmid

==== example output ====
 [/]$ vmsvc/get.guestheartbeatStatus 4400
 green


[[Category: Vimsh]]</text>
    <sha1>e6a2f6045ad5ab3077401d4196b229c0f965e7c3</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.managedentitystatus</title>
  <ns>0</ns>
  <id>176</id>
  <revision>
    <id>332</id>
    <timestamp>2008-12-17T08:33:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.managedentitystatus ==== Usage: get.managedentitystatus vmid  Show the status for the virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">==== vimsh vmsvc/get.managedentitystatus ====
Usage: get.managedentitystatus vmid

Show the status for the virtual machine.

[[Category: Vimsh]]</text>
    <sha1>e7620bd1efe108f5386c68f8e51fc2e2e6dbc54d</sha1>
  </revision>
  <revision>
    <id>342</id>
    <parentid>332</parentid>
    <timestamp>2008-12-17T10:48:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="220" xml:space="preserve">==== vimsh vmsvc/get.managedentitystatus ====
Usage: get.managedentitystatus vmid

Show the status for the virtual machine.

==== example output ====
 [/]$ vmsvc/get.managedentitystatus 4400
 green


[[Category: Vimsh]]</text>
    <sha1>22bad2ea5487572a36621cc894802503a9164369</sha1>
  </revision>
  <revision>
    <id>345</id>
    <parentid>342</parentid>
    <timestamp>2008-12-17T10:54:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="274" xml:space="preserve">==== vimsh vmsvc/get.managedentitystatus ====
Usage: get.managedentitystatus vmid

Show the status for the virtual machine.

You can use [[vmsvc/getallvms]] to retrieve the vmid

==== example output ====
 [/]$ vmsvc/get.managedentitystatus 4400
 green


[[Category: Vimsh]]</text>
    <sha1>7ceeea4b9a2c8927f65a5edbda8b20ad6bf06581</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.networks</title>
  <ns>0</ns>
  <id>177</id>
  <revision>
    <id>333</id>
    <timestamp>2008-12-17T08:34:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.networks ==== Usage: get.networks vmid  Show the list of networks for this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="133" xml:space="preserve">==== vimsh vmsvc/get.networks ====
Usage: get.networks vmid

Show the list of networks for this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>16c6b87b1812bdb5e8440c760b126f5945cb41a1</sha1>
  </revision>
  <revision>
    <id>340</id>
    <parentid>333</parentid>
    <timestamp>2008-12-17T10:00:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="384" xml:space="preserve">==== vimsh vmsvc/get.networks ====
Usage: get.networks vmid

Show the list of networks for this virtual machine.

==== example output ====
 [/]$ vmsvc/get.networks 4400
 Networks:
 
 (vim.Network.Summary) {
    dynamicType = &lt;unset&gt;,
    network = 'vim.Network:HaNetwork-Virtual Machines Network',
    name = "Virtual Machines Network",
    accessible = true,
 }


[[Category: Vimsh]]</text>
    <sha1>feac1f6e8366cc07615e44b2ba2528ec12b61294</sha1>
  </revision>
  <revision>
    <id>341</id>
    <parentid>340</parentid>
    <timestamp>2008-12-17T10:02:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="439" xml:space="preserve">==== vimsh vmsvc/get.networks ====
Usage: get.networks vmid

Show the list of networks for this virtual machine.

You can use [[vmsvc/getallvms]] to retrieve the vmid


==== example output ====
 [/]$ vmsvc/get.networks 4400
 Networks:
 
 (vim.Network.Summary) {
    dynamicType = &lt;unset&gt;,
    network = 'vim.Network:HaNetwork-Virtual Machines Network',
    name = "Virtual Machines Network",
    accessible = true,
 }


[[Category: Vimsh]]</text>
    <sha1>a3ea8f18def6979bbe28ef12d6450e37d85398fb</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.snapshotinfo</title>
  <ns>0</ns>
  <id>178</id>
  <revision>
    <id>334</id>
    <timestamp>2008-12-17T08:35:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.snapshotinfo ==== Usage: get.snapshotinfo vmid  Show the snapshot information for this virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="145" xml:space="preserve">==== vimsh vmsvc/get.snapshotinfo ====
Usage: get.snapshotinfo vmid

Show the snapshot information for this virtual machine.

[[Category: Vimsh]]</text>
    <sha1>948b509196f65d52f4d69cfdb9ee3b2ef8cc4915</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.summary</title>
  <ns>0</ns>
  <id>179</id>
  <revision>
    <id>335</id>
    <timestamp>2008-12-17T08:41:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.summary ==== Usage: get.summary vmid  Retrieves and displays the listsummary status from the vm.  ==== example output ==== [/]$ vmsvc/get.summary 2200  Listsummary:   ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1913" xml:space="preserve">==== vimsh vmsvc/get.summary ====
Usage: get.summary vmid

Retrieves and displays the listsummary status from the vm.

==== example output ====
[/]$ vmsvc/get.summary 2200
 Listsummary: 
 
 (vim.vm.Summary) {
    dynamicType = &lt;unset&gt;,
    vm = 'vim.VirtualMachine:2200',
    runtime = (vim.vm.RuntimeInfo) {
       dynamicType = &lt;unset&gt;,
       host = 'vim.HostSystem:ha-host',
       connectionState = "connected",
       powerState = "poweredOn",
       toolsInstallerMounted = false,
       suspendTime = &lt;unset&gt;,
       bootTime = "2008-12-13T12:04:27.476613+01:00",
       suspendInterval = 0,
       question = (vim.vm.QuestionInfo) null,
       memoryOverhead = 87203840,
       maxCpuUsage = 4186,
       maxMemoryUsage = 384,
       numMksConnections = 0,
    },
    guest = (vim.vm.Summary.GuestSummary) {
       dynamicType = &lt;unset&gt;,
       guestId = "ubuntuGuest",
       guestFullName = "Ubuntu Linux (32-bit)",
       toolsStatus = "toolsOk",
       hostName = "vi-toolkit",
       ipAddress = "10.10.10.10",
    },
    config = (vim.vm.Summary.ConfigSummary) {
       dynamicType = &lt;unset&gt;,
       name = "vi-toolkit",
       template = false,
       vmPathName = "[store] vi-toolkit/vi-toolkit.vmx",
       memorySizeMB = 384,
       cpuReservation = &lt;unset&gt;,
       memoryReservation = &lt;unset&gt;,
       numCpu = 1,
       numEthernetCards = 0,
       numVirtualDisks = 1,
       uuid = "262dfea0-9489-424c-ab13-2307e87d5253",
       guestId = "ubuntuGuest",
       guestFullName = "Ubuntu Linux (32-bit)",
       annotation = "",
    },
    quickStats = (vim.vm.Summary.QuickStats) {
       dynamicType = &lt;unset&gt;,
       overallCpuUsage = 90,
       guestMemoryUsage = 115,
       hostMemoryUsage = 208,
       guestHeartbeatStatus = "green",
       distributedCpuEntitlement = &lt;unset&gt;,
       distributedMemoryEntitlement = &lt;unset&gt;,
    },
    overallStatus = "green",
 }


[[Category: Vimsh]]</text>
    <sha1>42dd256d927251780f5e24124887e210f964b789</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.tasklist</title>
  <ns>0</ns>
  <id>180</id>
  <revision>
    <id>336</id>
    <timestamp>2008-12-17T08:42:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/get.tasklist ==== Usage: get.tasklist vmid  Get list of recent tasks on virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">==== vimsh vmsvc/get.tasklist ====
Usage: get.tasklist vmid

Get list of recent tasks on virtual machine.

[[Category: Vimsh]]</text>
    <sha1>bbb6f730b59644959a94e84221162a4c8a85999d</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vimsh: vmsvc/</title>
  <ns>0</ns>
  <id>46</id>
  <revision>
    <id>337</id>
    <parentid>296</parentid>
    <timestamp>2008-12-17T08:44:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3978" xml:space="preserve">Get or set virtual machine specific options such as hardware configuration of the vm or perform virtual machine operations such as shutdown or taking a snapshot.

 [/]$ vmsvc/
 acquiremksticket          get.configoption              power.off                 
 connect                       get.datastores                 power.on                  
 convert.toTemplate      get.disabledmethods        power.reboot              
 convert.toVm               get.environment              power.reset               
 createdummyvm          get.filelayout                   power.shutdown            
 destroy                       get.guest                         power.suspend             
 device.connection         get.guestheartbeatStatus  reload                    
 device.connusbdev       get.managedentitystatus   setscreenres              
 device.disconnusbdev   get.networks                    snapshot.create           
 device.diskadd             get.runtime                      snapshot.get              
 device.diskaddexisting  get.snapshotinfo               snapshot.remove           
 device.diskremove       get.summary                    snapshot.removeall        
 device.getdevices         get.tasklist                       snapshot.revert           
 device.toolsSyncSet      getallvms                        snapshot.setoption        
 device.vmiadd              gethostconstraints            tools.cancelinstall       
 device.vmiremove         login                              tools.install             
 devices.createnic           logout                            tools.upgrade             
 get.capability                message                        unregister                
 get.config                     power.getstate                upgrade                   
 get.config.cpuidmask     power.hibernate

 [[vmsvc/acquiremksticket]]              
 [[vmsvc/connect]]                  
 [[vmsvc/convert.toTemplate]]          
 [[vmsvc/convert.toVm]]               
 [[vmsvc/createdummyvm]]        
 [[vmsvc/destroy]]             
 [[vmsvc/device.connection]]               
 [[vmsvc/device.connusbdev]]            
 [[vmsvc/device.disconnusbdev]]       
 [[vmsvc/device.diskadd]]              
 [[vmsvc/device.diskaddexisting]]          
 [[vmsvc/device.diskremove]]     
 [[vmsvc/device.getdevices]]          
 [[vmsvc/device.toolsSyncSet]]
 [[vmsvc/device.vmiadd]] 
 [[vmsvc/device.vmiremove]]             
 [[vmsvc/devices.createnic]]         
 [[vmsvc/get.capability]]         
 [[vmsvc/get.config]]                   
 [[vmsvc/get.config.cpuidmask]]
 [[vmsvc/get.configoption]]       
 [[vmsvc/get.datastores]]                
 [[vmsvc/get.disabledmethods]]       
 [[vmsvc/get.environment]]           
 [[vmsvc/get.filelayout]]       
 [[vmsvc/get.guest]]        
 [[vmsvc/get.guestheartbeatStatus]]  
 [[vmsvc/get.managedentitystatus]]       
 [[vmsvc/get.networks]]         
 [[vmsvc/get.runtime]]          
 [[vmsvc/get.snapshotinfo]]     
 [[vmsvc/get.summary]]  
 [[vmsvc/get.tasklist]]      
 [[vmsvc/getallvms]]       
 [[vmsvc/gethostconstraints]]  
 [[vmsvc/login]]        
 [[vmsvc/logout]]           
 [[vmsvc/message]]    
 [[vmsvc/power.getstate]]      
 [[vmsvc/power.hibernate]]
 [[vmsvc/power.off]]                 
 [[vmsvc/power.on]]                  
 [[vmsvc/power.reboot]]              
 [[vmsvc/power.reset]]               
 [[vmsvc/power.shutdown]]            
 [[vmsvc/power.suspend]]             
 [[vmsvc/reload]]                    
 [[vmsvc/setscreenres]]              
 [[vmsvc/snapshot.create]]           
 [[vmsvc/snapshot.get]]              
 [[vmsvc/snapshot.remove]]           
 [[vmsvc/snapshot.removeall]]        
 [[vmsvc/snapshot.revert]]           
 [[vmsvc/snapshot.setoption]]        
 [[vmsvc/tools.cancelinstall]]       
 [[vmsvc/tools.install]]             
 [[vmsvc/tools.upgrade]]             
 [[vmsvc/unregister]]                
 [[vmsvc/upgrade]]                   


[[Category: Vimsh]]</text>
    <sha1>4d1a2095dffeeabac554ee1ee990f2f10aee2070</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vmsvc/get.runtime</title>
  <ns>0</ns>
  <id>146</id>
  <revision>
    <id>338</id>
    <parentid>300</parentid>
    <timestamp>2008-12-17T08:45:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1220" xml:space="preserve">==== vimsh vmsvc/get.runtime ====
Usage: get.runtime vmid

Get runtime information


You can use [[vmsvc/getallvms]] to retrieve the vmid

==== example output when vm is off ====
 vmsvc/get.runtime 4400
 Runtime information
 (vim.vm.RuntimeInfo) {
    dynamicType = &lt;unset&gt;, 
    host = 'vim.HostSystem:ha-host', 
    connectionState = "connected", 
    powerState = "poweredOff", 
    toolsInstallerMounted = false, 
    suspendTime = &lt;unset&gt;, 
    bootTime = &lt;unset&gt;, 
    suspendInterval = 0, 
    question = (vim.vm.QuestionInfo) null, 
    memoryOverhead = 71675904, 
    maxCpuUsage = 2392, 
    maxMemoryUsage = 256, 
    numMksConnections = 0, 
 }

==== example output when vm is on ====
 vmsvc/get.runtime 2200 
 Runtime information
 (vim.vm.RuntimeInfo) {
    dynamicType = &lt;unset&gt;, 
    host = 'vim.HostSystem:ha-host', 
    connectionState = "connected", 
    powerState = "poweredOn", 
    toolsInstallerMounted = false, 
    suspendTime = &lt;unset&gt;, 
    bootTime = "2008-12-13T12:04:27.476613+01:00", 
    suspendInterval = 0, 
    question = (vim.vm.QuestionInfo) null, 
    memoryOverhead = 87277568, 
    maxCpuUsage = 4186, 
    maxMemoryUsage = 384, 
    numMksConnections = 0, 
 }

[[Category: Vimsh]]</text>
    <sha1>ba3c785d943b9dea132b44964a111c2a7552a026</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Vimsh: solo/</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>350</id>
    <parentid>189</parentid>
    <timestamp>2008-12-17T11:03:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="299" xml:space="preserve"> [/]$ solo/ 
 connect          login             querycfgopt         registervm       
 environment   logout           querycfgoptdesc

 [[solo/connect]]
 [[solo/environment]]
 [[solo/login]]
 [[solo/logout]]
 [[solo/querycfgopt]] 
 [[solo/querycfgoptdesc]]
 [[solo/registervm]]

[[Category: Vimsh]]</text>
    <sha1>f2804b7c42c4eedf2c431fcdbd2be446a4d22861</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Solo/connect</title>
  <ns>0</ns>
  <id>181</id>
  <revision>
    <id>351</id>
    <timestamp>2008-12-17T11:07:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh solo/connect ==== Usage: connect [hostname] [port] [key] [cert] [product]  Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and a ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="431" xml:space="preserve">==== vimsh solo/connect ====
Usage: connect [hostname] [port] [key] [cert] [product]

Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and a certificate.

By default product is 'solo', hostname is 'localhost'.

* Port is 902.
* private key is at /etc/vmware/ssl/rui.key
* certificate is at /etc/vmware/ssl/rui.crt

To disable SSL, use an empty key or certificate.

[[Category: Vimsh]]</text>
    <sha1>80fd5cb1fa4fa97a20c9e04d2a15fa4cb7838de9</sha1>
  </revision>
</page>
<page arvcontinue="20081217080326|303">
  <title>Solo/environment</title>
  <ns>0</ns>
  <id>182</id>
  <revision>
    <id>352</id>
    <timestamp>2008-12-17T11:08:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh solo/environment ==== Usage: environment  Display the default vm environment on this host.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">==== vimsh solo/environment ====
Usage: environment

Display the default vm environment on this host.

[[Category: Vimsh]]</text>
    <sha1>e78fb7f456c1e80c687657b69ac4022204f6b232</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Solo/login</title>
  <ns>0</ns>
  <id>183</id>
  <revision>
    <id>353</id>
    <timestamp>2008-12-17T11:09:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh solo/login ==== Usage: login [username] [password]  Logs in to host, creating a new session.  If no password is specified, will use a local authentication mechanism.  [[Category...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="197" xml:space="preserve">==== vimsh solo/login ====
Usage: login [username] [password]

Logs in to host, creating a new session.  If no password is specified, will
use a local authentication mechanism.

[[Category: Vimsh]]</text>
    <sha1>a31c8bd682fbe22e5a50da23636245e3dc5f90ce</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Solo/logout</title>
  <ns>0</ns>
  <id>184</id>
  <revision>
    <id>354</id>
    <timestamp>2008-12-17T11:09:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh solo/logout ==== Usage: logout  Logs out from host, destroying existing session.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="112" xml:space="preserve">==== vimsh solo/logout ====
Usage: logout

Logs out from host, destroying existing session.

[[Category: Vimsh]]</text>
    <sha1>563e1aac06bccaccc8de5f1a63323c1f5511d5cd</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Solo/querycfgopt</title>
  <ns>0</ns>
  <id>185</id>
  <revision>
    <id>355</id>
    <timestamp>2008-12-17T11:10:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh solo/querycfgopt ==== Usage: querycfgopt [key]  Display the environment config option specified.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="128" xml:space="preserve">==== vimsh solo/querycfgopt ====
Usage: querycfgopt [key]

Display the environment config option specified.

[[Category: Vimsh]]</text>
    <sha1>689501bed7268585c2631279aece9126d4b68a60</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Solo/querycfgoptdesc</title>
  <ns>0</ns>
  <id>186</id>
  <revision>
    <id>356</id>
    <timestamp>2008-12-17T11:11:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh solo/querycfgoptdesc ==== Usage: querycfgoptdesc  Display the environment descriptors available on this host.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="141" xml:space="preserve">==== vimsh solo/querycfgoptdesc ====
Usage: querycfgoptdesc

Display the environment descriptors available on this host.

[[Category: Vimsh]]</text>
    <sha1>ceb0f7a296ddb92b047f1584f5698418fdcd262e</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Solo/registervm</title>
  <ns>0</ns>
  <id>187</id>
  <revision>
    <id>357</id>
    <timestamp>2008-12-17T11:12:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh solo/registervm ==== Usage: registervm vm path [name] [resourcepool]  registervm [cfg path] [name(optional)] [resourcepool(optional)]  Register the vm  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">==== vimsh solo/registervm ====
Usage: registervm vm path [name] [resourcepool]

registervm [cfg path] [name(optional)] [resourcepool(optional)]

Register the vm

[[Category: Vimsh]]</text>
    <sha1>2d2290b4591109bd8e775162f1edcfcbc5adfffd</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Hostsvc/firmware/</title>
  <ns>0</ns>
  <id>188</id>
  <revision>
    <id>358</id>
    <timestamp>2008-12-17T11:16:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/firmware/ ====   backup_config   reset_config    restore_config  sync_config   [[hostsvc/firmware/backup_config]]  [[hostsvc/firmware/reset_config]]  [[hostsvc/firmware/...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="238" xml:space="preserve">==== vimsh hostsvc/firmware/ ====

 backup_config   reset_config    restore_config  sync_config

 [[hostsvc/firmware/backup_config]]
 [[hostsvc/firmware/reset_config]]
 [[hostsvc/firmware/restore_config]]
 [[hostsvc/firmware/sync_config]]</text>
    <sha1>c55b96e4701c3ba61055c71432f705d00c1884d3</sha1>
  </revision>
  <revision>
    <id>359</id>
    <parentid>358</parentid>
    <timestamp>2008-12-17T11:16:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="259" xml:space="preserve">==== vimsh hostsvc/firmware/ ====

 backup_config   reset_config    restore_config  sync_config

 [[hostsvc/firmware/backup_config]]
 [[hostsvc/firmware/reset_config]]
 [[hostsvc/firmware/restore_config]]
 [[hostsvc/firmware/sync_config]]

[[Category: Vimsh]]</text>
    <sha1>2f30574d9a83ac14ba77ae5ba135e3d12035ba8b</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Hostsvc/firmware/backup config</title>
  <ns>0</ns>
  <id>189</id>
  <revision>
    <id>360</id>
    <timestamp>2008-12-17T11:17:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/firmware/backup_config ==== Usage: Backup the firmware configuration  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">==== vimsh hostsvc/firmware/backup_config ====
Usage: Backup the firmware configuration

[[Category: Vimsh]]</text>
    <sha1>56737b1bede8d0f2a53bad4ab8c691103cdd80f7</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Hostsvc/firmware/reset config</title>
  <ns>0</ns>
  <id>190</id>
  <revision>
    <id>361</id>
    <timestamp>2008-12-17T11:18:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/firmware/reset_config ==== Usage: Reset the configuration to factory defaults  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="117" xml:space="preserve">==== vimsh hostsvc/firmware/reset_config ====
Usage: Reset the configuration to factory defaults

[[Category: Vimsh]]</text>
    <sha1>4c2e3964c79fd6bbc72f864cd05ca1080bf3a328</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Hostsvc/firmware/restore config</title>
  <ns>0</ns>
  <id>191</id>
  <revision>
    <id>362</id>
    <timestamp>2008-12-17T11:19:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/firmware/restore_config ==== Usage: restore_config force  Restore the firmware configuration  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== vimsh hostsvc/firmware/restore_config ====
Usage: restore_config force

Restore the firmware configuration

[[Category: Vimsh]]</text>
    <sha1>d74d53d724724a6a14954dbbde5ec3ede427f45c</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Hostsvc/firmware/sync config</title>
  <ns>0</ns>
  <id>192</id>
  <revision>
    <id>363</id>
    <timestamp>2008-12-17T11:20:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/firmware/sync_config ==== Usage: sync_config  Sync the firmware configuration to persistent storage.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="140" xml:space="preserve">==== vimsh hostsvc/firmware/sync_config ====
Usage: sync_config

Sync the firmware configuration to persistent storage.

[[Category: Vimsh]]</text>
    <sha1>90995862576841192f62cf9bee2a4af4a01b2db0</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/get.runtime</title>
  <ns>0</ns>
  <id>146</id>
  <revision>
    <id>364</id>
    <parentid>338</parentid>
    <timestamp>2008-12-17T11:24:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1268" xml:space="preserve">==== vimsh vmsvc/get.runtime ====
Usage: get.runtime vmid

Get runtime information for the selected machine identified by its vmid.

You can use [[vmsvc/getallvms]] to retrieve the vmid

==== Example output when vm is off ====
 vmsvc/get.runtime 4400
 Runtime information
 (vim.vm.RuntimeInfo) {
    dynamicType = &lt;unset&gt;, 
    host = 'vim.HostSystem:ha-host', 
    connectionState = "connected", 
    powerState = "poweredOff", 
    toolsInstallerMounted = false, 
    suspendTime = &lt;unset&gt;, 
    bootTime = &lt;unset&gt;, 
    suspendInterval = 0, 
    question = (vim.vm.QuestionInfo) null, 
    memoryOverhead = 71675904, 
    maxCpuUsage = 2392, 
    maxMemoryUsage = 256, 
    numMksConnections = 0, 
 }

==== Example output when vm is on ====
 vmsvc/get.runtime 2200 
 Runtime information
 (vim.vm.RuntimeInfo) {
    dynamicType = &lt;unset&gt;, 
    host = 'vim.HostSystem:ha-host', 
    connectionState = "connected", 
    powerState = "poweredOn", 
    toolsInstallerMounted = false, 
    suspendTime = &lt;unset&gt;, 
    bootTime = "2008-12-13T12:04:27.476613+01:00", 
    suspendInterval = 0, 
    question = (vim.vm.QuestionInfo) null, 
    memoryOverhead = 87277568, 
    maxCpuUsage = 4186, 
    maxMemoryUsage = 384, 
    numMksConnections = 0, 
 }

[[Category: Vimsh]]</text>
    <sha1>b4943b5a583ea07dbc25e3f1d5652580add3b0f9</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>365</id>
    <parentid>151</parentid>
    <timestamp>2008-12-17T11:36:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1071" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://teckinfo.blogspot.com Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.astroarch.com/ Edward Haletky's site]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]</text>
    <sha1>0188c34bac46d6bab729d61a153d1e485fbeaa3b</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/gethostconstraints</title>
  <ns>0</ns>
  <id>193</id>
  <revision>
    <id>366</id>
    <timestamp>2008-12-18T17:39:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/gethostconstraints ==== Usage: vmconstraints  Retrieves and displays the constraints object for the host.  ??  ====Example output ====   [/]$ vmsvc/gethostconstraints   Da...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="267" xml:space="preserve">==== vimsh vmsvc/gethostconstraints ====
Usage: vmconstraints

Retrieves and displays the constraints object for the host.

??

====Example output ====

 [/]$ vmsvc/gethostconstraints 
 Datastores:
 
  
 Networks:
 
  
 Guest os descriptions:
 
 
[[Category: Vimsh]]</text>
    <sha1>81b4ab666a522a12c71c6c86f1803d50df30e2c8</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/login</title>
  <ns>0</ns>
  <id>194</id>
  <revision>
    <id>367</id>
    <timestamp>2008-12-18T17:40:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/login ==== Usage: login [username] [password]  Logs in to host, creating a new session.  If no password is specified, will use a local authentication mechanism.  [[Categor...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="198" xml:space="preserve">==== vimsh vmsvc/login ====
Usage: login [username] [password]

Logs in to host, creating a new session.  If no password is specified, will
use a local authentication mechanism.

[[Category: Vimsh]]</text>
    <sha1>60d3e2a7fcc5a5eae7c5e95728b77b3c65fcd38b</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/logout</title>
  <ns>0</ns>
  <id>195</id>
  <revision>
    <id>368</id>
    <timestamp>2008-12-18T17:41:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/logout ==== Usage: logout  Logs out from host, destroying existing session.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="113" xml:space="preserve">==== vimsh vmsvc/logout ====
Usage: logout

Logs out from host, destroying existing session.

[[Category: Vimsh]]</text>
    <sha1>09e31fc33947cd8d2ad62f9b56645262f4b2064b</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/message</title>
  <ns>0</ns>
  <id>196</id>
  <revision>
    <id>369</id>
    <timestamp>2008-12-18T17:42:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/message ==== Usage: message vmid [messageId] [messageChoice]  Replies to the current pending question on the vm.    [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="152" xml:space="preserve">==== vimsh vmsvc/message ====
Usage: message vmid [messageId] [messageChoice]

Replies to the current pending question on the vm.


[[Category: Vimsh]]</text>
    <sha1>be28911676a0da7bd65e9c85c2edd1e4f378a8c4</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/power.getstate</title>
  <ns>0</ns>
  <id>197</id>
  <revision>
    <id>370</id>
    <timestamp>2008-12-18T17:47:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/power.getstate ==== Usage: power.getstate vmid  Retrieves the power state of the specified virtual machine.  ====Example output==== For a machine that is powered on:  [/]$...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="622" xml:space="preserve">==== vimsh vmsvc/power.getstate ====
Usage: power.getstate vmid

Retrieves the power state of the specified virtual machine.

====Example output====
For a machine that is powered on:
 [/]$ vmsvc/power.getstate 4400
 Retrieved runtime info
 Powered on

For a non existing machine:
 [/]$ vmsvc/power.getstate 123
 (vim.fault.NotFound) {
    dynamicType = &lt;unset&gt;,
    msg = "Unable to find a VM corresponding to "123""
 }

For a suspended machine:
 [/]$ vmsvc/power.getstate 4414
 Retrieved runtime info 
 Suspended

and powered off:
 [/]$ vmsvc/power.getstate 4400
 Retrieved runtime info
 Powered off


[[Category: Vimsh]]</text>
    <sha1>1445763d97ad7289b3583bb82f29e69acebcd035</sha1>
  </revision>
  <revision>
    <id>371</id>
    <parentid>370</parentid>
    <timestamp>2008-12-18T17:48:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="676" xml:space="preserve">==== vimsh vmsvc/power.getstate ====
Usage: power.getstate vmid

Retrieves the power state of the specified virtual machine.

You can use [[vmsvc/getallvms]] to retrieve the vmid

====Example output====
For a machine that is powered on:
 [/]$ vmsvc/power.getstate 4400
 Retrieved runtime info
 Powered on

For a non existing machine:
 [/]$ vmsvc/power.getstate 123
 (vim.fault.NotFound) {
    dynamicType = &lt;unset&gt;,
    msg = "Unable to find a VM corresponding to "123""
 }

For a suspended machine:
 [/]$ vmsvc/power.getstate 4414
 Retrieved runtime info 
 Suspended

and powered off:
 [/]$ vmsvc/power.getstate 4400
 Retrieved runtime info
 Powered off


[[Category: Vimsh]]</text>
    <sha1>eba8087a46d4b1ff8f6186c7c6430092fc69de33</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/power.hibernate</title>
  <ns>0</ns>
  <id>198</id>
  <revision>
    <id>372</id>
    <timestamp>2008-12-18T17:49:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/power.hibernate ==== Usage: power.hibernate vmid  Cause guest to go into standby/hibernate and suspend.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="141" xml:space="preserve">==== vimsh vmsvc/power.hibernate ====
Usage: power.hibernate vmid

Cause guest to go into standby/hibernate and suspend.

[[Category: Vimsh]]</text>
    <sha1>ab3748e8534d06dccc56f2c369cb71d80ea87041</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/power.off</title>
  <ns>0</ns>
  <id>199</id>
  <revision>
    <id>373</id>
    <timestamp>2008-12-18T17:50:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/power.off ==== Usage: power.off vmid  Power off the specified virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="116" xml:space="preserve">==== vimsh vmsvc/power.off ====
Usage: power.off vmid

Power off the specified virtual machine.

[[Category: Vimsh]]</text>
    <sha1>ea01436f49839107788044aae97a874a5f257254</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/power.on</title>
  <ns>0</ns>
  <id>200</id>
  <revision>
    <id>374</id>
    <timestamp>2008-12-18T17:51:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/power.on ==== Usage: power.on vmid  Power on the specified virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="113" xml:space="preserve">==== vimsh vmsvc/power.on ====
Usage: power.on vmid

Power on the specified virtual machine.

[[Category: Vimsh]]</text>
    <sha1>0d65df15de89fc070ab9e1ef4b46875b49b79002</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/power.reboot</title>
  <ns>0</ns>
  <id>201</id>
  <revision>
    <id>375</id>
    <timestamp>2008-12-19T04:38:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/power.reboot ==== Usage: power.reboot vmid  Reboot the guest OS if tools is running.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">==== vimsh vmsvc/power.reboot ====
Usage: power.reboot vmid

Reboot the guest OS if tools is running.

[[Category: Vimsh]]</text>
    <sha1>8cf3ca0cf52477908c94a976b29bb80aafe5e676</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/power.reset</title>
  <ns>0</ns>
  <id>202</id>
  <revision>
    <id>376</id>
    <timestamp>2008-12-19T04:39:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/power.reset ==== Usage: power.reset vmid  Reset the specified virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="116" xml:space="preserve">==== vimsh vmsvc/power.reset ====
Usage: power.reset vmid

Reset the specified virtual machine.

[[Category: Vimsh]]</text>
    <sha1>ee07cb755838e4669daf644e57410025de11f647</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/power.shutdown</title>
  <ns>0</ns>
  <id>203</id>
  <revision>
    <id>377</id>
    <timestamp>2008-12-19T04:40:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/power.shutdown ==== Usage: power.shutdown vmid  Shutdown the guest OS  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="107" xml:space="preserve">==== vimsh vmsvc/power.shutdown ====
Usage: power.shutdown vmid

Shutdown the guest OS

[[Category: Vimsh]]</text>
    <sha1>d95506dd40fb8ff9f9c1d5981a05a1f18e5660fb</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/power.suspend</title>
  <ns>0</ns>
  <id>204</id>
  <revision>
    <id>378</id>
    <timestamp>2008-12-19T04:41:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/power.suspend ==== Usage: power.suspend vmid  Suspend the specified virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">==== vimsh vmsvc/power.suspend ====
Usage: power.suspend vmid

Suspend the specified virtual machine.

[[Category: Vimsh]]</text>
    <sha1>61b1939b6301489eeb6955214852c067b8911106</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/reload</title>
  <ns>0</ns>
  <id>205</id>
  <revision>
    <id>379</id>
    <timestamp>2008-12-19T04:42:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/reload ==== Usage: reload vmid  Reload the virtual machine state from afresh.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="115" xml:space="preserve">==== vimsh vmsvc/reload ====
Usage: reload vmid

Reload the virtual machine state from afresh.

[[Category: Vimsh]]</text>
    <sha1>81d67341e326cce0c8ac6299d2e7274bff5a09d8</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/setscreenres</title>
  <ns>0</ns>
  <id>206</id>
  <revision>
    <id>380</id>
    <timestamp>2008-12-19T04:43:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/setscreenres ==== Usage: setscreenres vmid width height  Sets the Console window's resolution.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== vimsh vmsvc/setscreenres ====
Usage: setscreenres vmid width height

Sets the Console window's resolution.

[[Category: vimsh]]</text>
    <sha1>39d9fd8ec451afc0cb8a4189718063af79ab8d89</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/snapshot.create</title>
  <ns>0</ns>
  <id>207</id>
  <revision>
    <id>381</id>
    <timestamp>2008-12-19T04:43:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/snapshot.create ==== Usage: snapshot.create vmid [snapshotName] [snapshotDescription] [includeMemory]  Creates a snapshot for the vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="171" xml:space="preserve">==== vimsh vmsvc/snapshot.create ====
Usage: snapshot.create vmid [snapshotName] [snapshotDescription] [includeMemory]

Creates a snapshot for the vm.

[[Category: Vimsh]]</text>
    <sha1>375ba9f0725b32d160b6458049b33b6e5f4c582b</sha1>
  </revision>
  <revision>
    <id>383</id>
    <parentid>381</parentid>
    <timestamp>2008-12-19T04:46:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="357" xml:space="preserve">==== vimsh vmsvc/snapshot.create ====
Usage: snapshot.create vmid [snapshotName] [snapshotDescription] [includeMemory]

Creates a snapshot for the vm.

See also:  [[vmsvc/snapshot.create]] | [[vmsvc/snapshot.get]] | [[vmsvc/snapshot.remove]] |  [[vmsvc/snapshot.removeall]] | [[vmsvc/snapshot.revert]] |  [[vmsvc/snapshot.setoption]]   

[[Category: Vimsh]]</text>
    <sha1>8919e9a027367a962ea099fb876685d0d31df728</sha1>
  </revision>
  <revision>
    <id>384</id>
    <parentid>383</parentid>
    <timestamp>2008-12-19T04:46:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="330" xml:space="preserve">==== vimsh vmsvc/snapshot.create ====
Usage: snapshot.create vmid [snapshotName] [snapshotDescription] [includeMemory]

Creates a snapshot for the vm.

See also:  
[[vmsvc/snapshot.get]] | [[vmsvc/snapshot.remove]] |  [[vmsvc/snapshot.removeall]] | [[vmsvc/snapshot.revert]] |  [[vmsvc/snapshot.setoption]]   

[[Category: Vimsh]]</text>
    <sha1>4bff28092451e9701bd4924b023ac63801a5fd35</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/snapshot.get</title>
  <ns>0</ns>
  <id>208</id>
  <revision>
    <id>382</id>
    <timestamp>2008-12-19T04:44:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/snapshot.get ==== Usage: snapshot.get vmid  gets the snapshot info for the vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="116" xml:space="preserve">==== vimsh vmsvc/snapshot.get ====
Usage: snapshot.get vmid

gets the snapshot info for the vm.

[[Category: Vimsh]]</text>
    <sha1>7508c5e619b7141d4a86e38f801494201958c59d</sha1>
  </revision>
  <revision>
    <id>385</id>
    <parentid>382</parentid>
    <timestamp>2008-12-19T04:47:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="304" xml:space="preserve">==== vimsh vmsvc/snapshot.get ====
Usage: snapshot.get vmid

gets the snapshot info for the vm.


See also:  [[vmsvc/snapshot.create]] | [[vmsvc/snapshot.get]] | [[vmsvc/snapshot.remove]] |  [[vmsvc/snapshot.removeall]] | [[vmsvc/snapshot.revert]] |  [[vmsvc/snapshot.setoption]]   


[[Category: Vimsh]]</text>
    <sha1>c0994442c778bb3a20d03e06a6390afcaf22bf6f</sha1>
  </revision>
  <revision>
    <id>390</id>
    <parentid>385</parentid>
    <timestamp>2008-12-19T04:51:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="279" xml:space="preserve">==== vimsh vmsvc/snapshot.get ====
Usage: snapshot.get vmid

gets the snapshot info for the vm.


See also:  [[vmsvc/snapshot.create]] | [[vmsvc/snapshot.remove]] |  [[vmsvc/snapshot.removeall]] | [[vmsvc/snapshot.revert]] |  [[vmsvc/snapshot.setoption]]   


[[Category: Vimsh]]</text>
    <sha1>ca607c4197d486943be5abd72e038920d01dc7ba</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/snapshot.remove</title>
  <ns>0</ns>
  <id>209</id>
  <revision>
    <id>386</id>
    <timestamp>2008-12-19T04:48:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/snapshot.remove ====  Usage: snapshot.remove vmid [removeChildren] [snapshotLevel] [snapshotIndex]  Remove a snapshot on the vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="166" xml:space="preserve">==== vimsh vmsvc/snapshot.remove ====

Usage: snapshot.remove vmid [removeChildren] [snapshotLevel] [snapshotIndex]

Remove a snapshot on the vm.

[[Category: Vimsh]]</text>
    <sha1>c2162f869c8da40954e4d653e1cda9cc9104f61b</sha1>
  </revision>
  <revision>
    <id>391</id>
    <parentid>386</parentid>
    <timestamp>2008-12-19T04:52:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="324" xml:space="preserve">==== vimsh vmsvc/snapshot.remove ====

Usage: snapshot.remove vmid [removeChildren] [snapshotLevel] [snapshotIndex]

Remove a snapshot on the vm.

See also:  [[vmsvc/snapshot.create]] | [[vmsvc/snapshot.get]] |  [[vmsvc/snapshot.removeall]] | [[vmsvc/snapshot.revert]] |  [[vmsvc/snapshot.setoption]]   

[[Category: Vimsh]]</text>
    <sha1>b6946f2a821c4d88f8f7fc157b300779cc17a746</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/snapshot.removeall</title>
  <ns>0</ns>
  <id>210</id>
  <revision>
    <id>387</id>
    <timestamp>2008-12-19T04:49:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/snapshot.removeall ==== Usage: snapshot.removeall vmid  Removes all the snapshots on the vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="130" xml:space="preserve">==== vimsh vmsvc/snapshot.removeall ====
Usage: snapshot.removeall vmid

Removes all the snapshots on the vm.

[[Category: Vimsh]]</text>
    <sha1>042082e0279f34c3cabed949dfc8a5779f10ed25</sha1>
  </revision>
  <revision>
    <id>392</id>
    <parentid>387</parentid>
    <timestamp>2008-12-19T04:52:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="285" xml:space="preserve">==== vimsh vmsvc/snapshot.removeall ====
Usage: snapshot.removeall vmid

Removes all the snapshots on the vm.

See also:  [[vmsvc/snapshot.create]] | [[vmsvc/snapshot.get]] | [[vmsvc/snapshot.remove]] | [[vmsvc/snapshot.revert]] |  [[vmsvc/snapshot.setoption]]   


[[Category: Vimsh]]</text>
    <sha1>653a58dc58cf510b59417a80ba45b75a9fb80710</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/snapshot.revert</title>
  <ns>0</ns>
  <id>211</id>
  <revision>
    <id>388</id>
    <timestamp>2008-12-19T04:50:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/snapshot.revert ==== Usage: snapshot.revert vmid [snapshotLevel] [snapshotIndex]  Revert to a snapshot on the vm.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">==== vimsh vmsvc/snapshot.revert ====
Usage: snapshot.revert vmid [snapshotLevel] [snapshotIndex]

Revert to a snapshot on the vm.

[[Category: Vimsh]]</text>
    <sha1>0ae2d719b083ea4c6aefdeff6184fc7ca6b81241</sha1>
  </revision>
  <revision>
    <id>393</id>
    <parentid>388</parentid>
    <timestamp>2008-12-19T04:53:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="311" xml:space="preserve">==== vimsh vmsvc/snapshot.revert ====
Usage: snapshot.revert vmid [snapshotLevel] [snapshotIndex]

Revert to a snapshot on the vm.

See also:  [[vmsvc/snapshot.create]] | [[vmsvc/snapshot.get]] | [[vmsvc/snapshot.remove]] |  [[vmsvc/snapshot.removeall]] |   [[vmsvc/snapshot.setoption]]   


[[Category: Vimsh]]</text>
    <sha1>7de7d80d4d82c33ad9489cfa14719913ba04633b</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/snapshot.setoption</title>
  <ns>0</ns>
  <id>212</id>
  <revision>
    <id>389</id>
    <timestamp>2008-12-19T04:51:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/snapshot.setoption ==== Usage: snapshot.setoption [OPTIONS] vmid  Config snapshot behavior on the vm.  Options:    --locked=bool        Whether to lock the snapshot      -...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="318" xml:space="preserve">==== vimsh vmsvc/snapshot.setoption ====
Usage: snapshot.setoption [OPTIONS] vmid

Config snapshot behavior on the vm.

Options:
   --locked=bool
       Whether to lock the snapshot
 
   --disabled=bool
       whether to disable snapshot
 
   --action=string
       The snapshot power-off behavior

[[Category: Vimsh]]</text>
    <sha1>8d192377386f9ce1a2fbb4a9fabfa018240faf63</sha1>
  </revision>
  <revision>
    <id>394</id>
    <parentid>389</parentid>
    <timestamp>2008-12-19T04:53:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="471" xml:space="preserve">==== vimsh vmsvc/snapshot.setoption ====
Usage: snapshot.setoption [OPTIONS] vmid

Config snapshot behavior on the vm.

Options:
   --locked=bool
       Whether to lock the snapshot
 
   --disabled=bool
       whether to disable snapshot
 
   --action=string
       The snapshot power-off behavior

See also:  [[vmsvc/snapshot.create]] | [[vmsvc/snapshot.get]] | [[vmsvc/snapshot.remove]] |  [[vmsvc/snapshot.removeall]] | [[vmsvc/snapshot.revert]] 


[[Category: Vimsh]]</text>
    <sha1>75ed0c09e098bd50b7b5f3e6d72c80fb8d6c5b4f</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/tools.cancelinstall</title>
  <ns>0</ns>
  <id>213</id>
  <revision>
    <id>395</id>
    <timestamp>2008-12-19T04:56:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/tools.cancelinstall ====  Usage: tools.cancelinstall vmid  Cancel the tools installation process   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="135" xml:space="preserve">==== vimsh vmsvc/tools.cancelinstall ====

Usage: tools.cancelinstall vmid

Cancel the tools installation process


[[Category: Vimsh]]</text>
    <sha1>ab6be32a6b1562e998d4d8aec23a60d0c76be3b7</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/tools.install</title>
  <ns>0</ns>
  <id>214</id>
  <revision>
    <id>396</id>
    <timestamp>2008-12-19T04:57:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/tools.install ==== Usage: tools.install vmid  Start the tools installation process  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="120" xml:space="preserve">==== vimsh vmsvc/tools.install ====
Usage: tools.install vmid

Start the tools installation process

[[Category: Vimsh]]</text>
    <sha1>8398005cbe4b3777993c85f06e1595ca0fd87f30</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/tools.upgrade</title>
  <ns>0</ns>
  <id>215</id>
  <revision>
    <id>397</id>
    <timestamp>2008-12-19T04:58:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/tools.upgrade ==== Usage: tools.upgrade vmid [args]  Upgrade VMware Tools in the virtual machine  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== vimsh vmsvc/tools.upgrade ====
Usage: tools.upgrade vmid [args]

Upgrade VMware Tools in the virtual machine

[[Category: Vimsh]]</text>
    <sha1>a3e1beb5349f3296b78ff6f9f29072e40db377cd</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/unregister</title>
  <ns>0</ns>
  <id>216</id>
  <revision>
    <id>398</id>
    <timestamp>2008-12-19T04:59:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/unregister ==== Usage: unregister vmid  Unregister the virtual machine  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">==== vimsh vmsvc/unregister ====
Usage: unregister vmid

Unregister the virtual machine

[[Category: Vimsh]]</text>
    <sha1>91d5f60f3b1110e96f5d956bfc1cf427422d1891</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vmsvc/upgrade</title>
  <ns>0</ns>
  <id>217</id>
  <revision>
    <id>399</id>
    <timestamp>2008-12-19T04:59:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/upgrade ==== Usage: upgrade vmid [vm_hwversion]  Upgrade the virtual hardware of the VM if possible.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="138" xml:space="preserve">==== vimsh vmsvc/upgrade ====
Usage: upgrade vmid [vm_hwversion]

Upgrade the virtual hardware of the VM if possible.

[[Category: Vimsh]]</text>
    <sha1>801008fd50efa1cd7de0a63349c4fdcff85400e5</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vimsh: vimsvc/</title>
  <ns>0</ns>
  <id>50</id>
  <revision>
    <id>400</id>
    <parentid>190</parentid>
    <timestamp>2008-12-19T05:03:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="447" xml:space="preserve"> [/]$ vimsvc/  
 auth/              login                    task_cancel         task_list         
 connect           logout                 task_description  
 license            property_dump    task_info

 [[vimsvc/auth/]]
 [[vimsvc/connect]]
 [[vimsvc/license]]
 [[vimsvc/login]]
 [[vimsvc/logout]]
 [[vimsvc/property_dump]]
 [[vimsvc/task_cancel]]
 [[vimsvc/task_description]]
 [[vimsvc/task_info]]
 [[vimsvc/task_list]]

[[Category: Vimsh]]</text>
    <sha1>48378cdab0e266e3cfd7e9befb9c6bc4402e8128</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vimsvc/connect</title>
  <ns>0</ns>
  <id>218</id>
  <revision>
    <id>401</id>
    <timestamp>2008-12-19T05:04:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/connect ====  Usage: connect [hostname] [port] [key] [cert] [product]  Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="435" xml:space="preserve">==== vimsh vimsvc/connect ====

Usage: connect [hostname] [port] [key] [cert] [product]

Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and a certificate.

By default product is 'solo', hostname is 'localhost'.
 
* Port is 902.
* private key is at /etc/vmware/ssl/rui.key
* certificate is at /etc/vmware/ssl/rui.crt

To disable SSL, use an empty key or certificate.

[[Category: Vimsh]]</text>
    <sha1>8d7e298b972936bb3cd6d457a71c2947754b7dfa</sha1>
  </revision>
</page>
<page arvcontinue="20081217110911|353">
  <title>Vimsvc/license</title>
  <ns>0</ns>
  <id>219</id>
  <revision>
    <id>402</id>
    <timestamp>2008-12-19T05:05:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/license ==== Usage: license [OPTIONS]  Control License Subsystem. Options:    --show        Display license info.      --diagnostics        Display subsystem status.     ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="651" xml:space="preserve">==== vimsh vimsvc/license ====
Usage: license [OPTIONS]

Control License Subsystem.
Options:
   --show
       Display license info.
 
   --diagnostics
       Display subsystem status.
 
   --edition=lic_editions
       Set license edition. To disable use 'none' options. License editions allocated per cpu.
 
   --source=lic_source
       Set license data source location to a license file (optionally specify an ascii license to upload) or specify the IPv4 or resolveable domain name running License Server.
 
   --addons=lic_addons
       Specify additional features to this license. Presently full edition supports backup only.

[[Category: Vimsh]]</text>
    <sha1>a1d8a702c7fa387e6b0a27036b5e747dc7e4ac34</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/license</title>
  <ns>0</ns>
  <id>219</id>
  <revision>
    <id>403</id>
    <parentid>402</parentid>
    <timestamp>2008-12-19T05:05:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="652" xml:space="preserve">==== vimsh vimsvc/license ====
Usage: license [OPTIONS]

Control License Subsystem.

Options:
   --show
       Display license info.
 
   --diagnostics
       Display subsystem status.
 
   --edition=lic_editions
       Set license edition. To disable use 'none' options. License editions allocated per cpu.
 
   --source=lic_source
       Set license data source location to a license file (optionally specify an ascii license to upload) or specify the IPv4 or resolveable domain name running License Server.
 
   --addons=lic_addons
       Specify additional features to this license. Presently full edition supports backup only.

[[Category: Vimsh]]</text>
    <sha1>9751fcabcbc82a83ce28c69107e36a67f8cc98ac</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/login</title>
  <ns>0</ns>
  <id>220</id>
  <revision>
    <id>404</id>
    <timestamp>2008-12-19T05:06:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/login ==== Usage: login [username] [password]  Logs in to host, creating a new session.  If no password is specified, will use a local authentication mechanism.  [[Catego...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="199" xml:space="preserve">==== vimsh vimsvc/login ====
Usage: login [username] [password]

Logs in to host, creating a new session.  If no password is specified, will
use a local authentication mechanism.

[[Category: Vimsh]]</text>
    <sha1>5f99e97e667ebb797159ad5dd5f5d32fff71e1e6</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/logout</title>
  <ns>0</ns>
  <id>221</id>
  <revision>
    <id>405</id>
    <timestamp>2008-12-19T05:07:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vmsvc/logout ==== Usage: logout  Logs out from host, destroying existing session.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="113" xml:space="preserve">==== vimsh vmsvc/logout ====
Usage: logout

Logs out from host, destroying existing session.

[[Category: Vimsh]]</text>
    <sha1>09e31fc33947cd8d2ad62f9b56645262f4b2064b</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/property dump</title>
  <ns>0</ns>
  <id>222</id>
  <revision>
    <id>406</id>
    <timestamp>2008-12-19T05:08:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/property_dump ==== Usage: property_dump [file] [filteronly]  Gathers a dump of properties from the property collector.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="157" xml:space="preserve">==== vimsh vimsvc/property_dump ====
Usage: property_dump [file] [filteronly]

Gathers a dump of properties from the property collector.

[[Category: Vimsh]]</text>
    <sha1>b9178731b958a9f96327689650dae143b305f739</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/task cancel</title>
  <ns>0</ns>
  <id>223</id>
  <revision>
    <id>407</id>
    <timestamp>2008-12-19T05:08:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/task_cancel ====  Usage: task_cancel id  Cancel a task.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="94" xml:space="preserve">==== vimsh vimsvc/task_cancel ====

Usage: task_cancel id

Cancel a task.

[[Category: Vimsh]]</text>
    <sha1>c47fff51a433710ed7924d5f7ca1f98e6047bf10</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/task description</title>
  <ns>0</ns>
  <id>224</id>
  <revision>
    <id>408</id>
    <timestamp>2008-12-19T05:09:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/task_description ==== Usage: task_description  Get task descriptions.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">==== vimsh vimsvc/task_description ====
Usage: task_description

Get task descriptions.

[[Category: Vimsh]]</text>
    <sha1>d659cf12b3857fead29883a10fcfe19c3adc3770</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/task info</title>
  <ns>0</ns>
  <id>225</id>
  <revision>
    <id>409</id>
    <timestamp>2008-12-19T05:10:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/task_info ==== Usage: task_info id  Get information about a task.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="104" xml:space="preserve">==== vimsh vimsvc/task_info ====
Usage: task_info id

Get information about a task.

[[Category: Vimsh]]</text>
    <sha1>4e98e684171c03658f24087bba42135425462b6a</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/task list</title>
  <ns>0</ns>
  <id>226</id>
  <revision>
    <id>410</id>
    <timestamp>2008-12-19T05:11:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/task_list ==== Usage: task_list  Get list of recent tasks.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="97" xml:space="preserve">==== vimsh vimsvc/task_list ====
Usage: task_list

Get list of recent tasks.

[[Category: Vimsh]]</text>
    <sha1>8e393b8f2e2cd6d1d5b8251df1f384568d9b2a8f</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>411</id>
    <parentid>53</parentid>
    <timestamp>2008-12-20T15:43:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="421" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]

==== Scripts on other locations =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/thread/156302 HBA Load Balancer]</text>
    <sha1>a2c2353be8aa62abbf615dbfa90bb87bc172af16</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>VI-Toolkit:Community Portal</title>
  <ns>4</ns>
  <id>6</id>
  <revision>
    <id>412</id>
    <parentid>108</parentid>
    <timestamp>2008-12-20T17:00:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2222" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

==== Management Virtual Machines  =====
VMware ESX 3.5 and earlier had the management console, a stripped down linux console which was could be used for automating and managing your virtual machines. As of ESX 3.5i this is no longer available and the future is to move away from the fat hypervisor. In order to manage your virtual machines in a similar way as before, we now have special virtual machines that come with management software pre-installed. VMware delivers 2 appliances for this, the VIMA and the RCLI.

* [http://www.vmware.com/support/developer/vima/index.html VMware Infrastructure Management Assistant (VIMA)]

This is a 64bits virtual machine based on RHEL. 

Features that VIMA has over the RCLI:
    * component for caching authentication 
    * component for collecting ESX log files (remote logging)
    * Designed to host agents that will be released by some 3rd party developers
    * Includes a mechanism for VMware to provide updates
    * Supported for production use

* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on Ubuntu JEOS
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not)
# There is also a windows installed.

The appliance has the VI perl toolkit pre-installed, but beware of the following note: 
'' This version of the VMware Infrastructure Remote CLI is incompatible with VI Perl Toolkit. These two products should be installed on different machines. The next refresh of the Remote CLI will fix this incompatibility.  ''
Unfortunately that was released on december 2007, so I'm not sure we will see an update on this.</text>
    <sha1>9dc604b5f73d8d6d26e49da55e0c907613e0a2c3</sha1>
  </revision>
  <revision>
    <id>413</id>
    <parentid>412</parentid>
    <timestamp>2008-12-20T17:01:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2213" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

==== Management Virtual Machines  =====
VMware ESX 3.5 and earlier had the management console, a stripped down linux console which was could be used for automating and managing your virtual machines. As of ESX 3.5i this is no longer available and the future is to move away from the fat hypervisor. In order to manage your virtual machines in a similar way as before, we now have special virtual machines that come with management software pre-installed. VMware delivers 2 appliances for this, the VIMA and the RCLI.

* [http://www.vmware.com/support/developer/vima/index.html VMware Infrastructure Management Assistant (VIMA)]

This is a 64bits virtual machine based on RHEL. 

Features that VIMA has over the RCLI:
* component for caching authentication 
* component for collecting ESX log files (remote logging)
* Designed to host agents that will be released by some 3rd party developers
* Includes a mechanism for VMware to provide updates
* Supported for production use

* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on Ubuntu JEOS
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not)
# There is also a windows installed.

The appliance has the VI perl toolkit pre-installed, but beware of the following note: 

'' This version of the VMware Infrastructure Remote CLI is incompatible with VI Perl Toolkit. These two products should be installed on different machines. The next refresh of the Remote CLI will fix this incompatibility.  ''

Unfortunately the last RCLI was released on december 2007, so I'm not sure we will see an update on this.</text>
    <sha1>ed7bfc2350d1ca8f65bd76e4f0a11ad240dd37f6</sha1>
  </revision>
  <revision>
    <id>414</id>
    <parentid>413</parentid>
    <timestamp>2008-12-20T17:02:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2212" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management console, a stripped down linux console which was could be used for automating and managing your virtual machines. As of ESX 3.5i this is no longer available and the future is to move away from the fat hypervisor. In order to manage your virtual machines in a similar way as before, we now have special virtual machines that come with management software pre-installed. VMware delivers 2 appliances for this, the VIMA and the RCLI.

* [http://www.vmware.com/support/developer/vima/index.html VMware Infrastructure Management Assistant (VIMA)]

This is a 64bits virtual machine based on RHEL. 

Features that VIMA has over the RCLI:
* component for caching authentication 
* component for collecting ESX log files (remote logging)
* Designed to host agents that will be released by some 3rd party developers
* Includes a mechanism for VMware to provide updates
* Supported for production use

* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on Ubuntu JEOS
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not)
# There is also a windows installed.

The appliance has the VI perl toolkit pre-installed, but beware of the following note: 

'' This version of the VMware Infrastructure Remote CLI is incompatible with VI Perl Toolkit. These two products should be installed on different machines. The next refresh of the Remote CLI will fix this incompatibility.  ''

Unfortunately the last RCLI was released on december 2007, so I'm not sure we will see an update on this.</text>
    <sha1>54c26ce1d74c4cacb9e422903818a7385706ac8c</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>415</id>
    <parentid>156</parentid>
    <timestamp>2008-12-20T17:59:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1508" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages
* Add "what's new" to the main page
* Add # of articles/pages to the main page

* Fix css for code snippets, it doesn't look like the current font is monospaced
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)
* Do email notifications work? (I think not)

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?

[[Category: VI-Toolkit]]</text>
    <sha1>1c92a697e19ee0d854aebea25fb4254f899dfbb1</sha1>
  </revision>
  <revision>
    <id>429</id>
    <parentid>415</parentid>
    <timestamp>2008-12-20T18:50:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>better category again</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1505" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages
* Add "what's new" to the main page
* Add # of articles/pages to the main page

* Fix css for code snippets, it doesn't look like the current font is monospaced
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)
* Do email notifications work? (I think not)

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?

[[Category: website]]</text>
    <sha1>37d8ead98b522eea89ff6dd002d17d415b77c636</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>416</id>
    <parentid>117</parentid>
    <timestamp>2008-12-20T18:00:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1037" xml:space="preserve">== VI Toolkit ==
'' December 11, 2008 ''

Welcome at our new site which will contain information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

Right now it is much closer to being a collection of hyperlinks to code found on the net.

This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: VI-Toolkit]]</text>
    <sha1>8fd53bb4f67c1eb0bda7006abaf46e2f318253c9</sha1>
  </revision>
  <revision>
    <id>426</id>
    <parentid>416</parentid>
    <timestamp>2008-12-20T18:28:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1031" xml:space="preserve">== VI Toolkit ==
'' December 11, 2008 ''

Welcome at our new site which will contain information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

Right now it is much closer to being a collection of hyperlinks to code found on the net.

This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: site]]</text>
    <sha1>c526869fd1ff2c77162275c9c6d76b6ae8c9bb51</sha1>
  </revision>
  <revision>
    <id>427</id>
    <parentid>426</parentid>
    <timestamp>2008-12-20T18:28:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1034" xml:space="preserve">== VI Toolkit ==
'' December 11, 2008 ''

Welcome at our new site which will contain information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

Right now it is much closer to being a collection of hyperlinks to code found on the net.

This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>36734edfb9ed94c638abf75b4fa8b8abd1c649d3</sha1>
  </revision>
  <revision>
    <id>433</id>
    <parentid>427</parentid>
    <timestamp>2008-12-20T19:05:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added statistics info and a tip on navigation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1314" xml:space="preserve">== VI Toolkit ==
'' December 11, 2008 ''

Welcome at our new site which will contain information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

Right now it is much closer to being a collection of hyperlinks to code found on the net.

This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you.

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>4d08abc0ffd161ea0c9405ff5d1bde6d7be355f6</sha1>
  </revision>
  <revision>
    <id>437</id>
    <parentid>433</parentid>
    <timestamp>2008-12-20T19:23:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>making it easier to read...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1398" xml:space="preserve">== VI Toolkit ==
'' December 11, 2008 ''
==== Welcome ====
Welcome at our new site which will contain information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

Right now it is much closer to being a collection of hyperlinks to code found on the net.
==== Contribute / help out ====
This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you.

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>477f637fa29e646787bcd9ab2914b15c87635c50</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vmrun batch file execution</title>
  <ns>0</ns>
  <id>36</id>
  <revision>
    <id>417</id>
    <parentid>88</parentid>
    <timestamp>2008-12-20T18:02:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="417" xml:space="preserve">In order to use vmrun to run a batch file on a Windows guest, you can use RunProgramInGuest and explicity call cmd.exe with the /c switch.

 vmrun -T ws -gu USERNAME -gp PASSWORD runProgramInGuest "C:\Virtual Machines\WinXP2\WinXP2.vmx" %COMSPEC% "/c C:\batch.bat"

This command will issue %COMSPEC%, which is a pointer to cmd.exe, to run the batch file C:\batch.bat on the WinXP2 virtual machine.


[[Category: VIX]]</text>
    <sha1>e4aa4cb98d218d52a668da30a28300d0822822ef</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vmrun return all IPs for running VMs</title>
  <ns>0</ns>
  <id>38</id>
  <revision>
    <id>418</id>
    <parentid>97</parentid>
    <timestamp>2008-12-20T18:02:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="857" xml:space="preserve">==== Return all IPs for running VMs ====

If you want to do this through vmrun on VMware Server 2, then you can do the following:

 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd runProgramInGuest "[standard] test/SLES10sp1.vmx" /bin/sh "/sbin/ifconfig &gt; /tmp/ip-info.txt"
 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd copyFileFromGuestToHost "[standard] test/SLES10sp1.vmx" /tmp/ip-info.txt /host/path/ip-info.txt"
 vmrun -T server -h https://myserver/sdk -u root -p passwd -gu root -gp passwd deleteFileInGuest "[standard] test/SLES10sp1.vmx" /tmp/ip-info.txt

This will redirect the output of ifconfig to a file on the guest, then copy that file to the host. It also cleans up the file, just to be tidy.


See also:

http://communities.vmware.com/message/1087204#1087204


[[Category: VIX]]</text>
    <sha1>c37491258c381fe59774d6f202beec76243d428a</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>419</id>
    <parentid>114</parentid>
    <timestamp>2008-12-20T18:03:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="293" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]


[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>4661f0affb18a70dc14ece9cb91396e8d644746a</sha1>
  </revision>
  <revision>
    <id>420</id>
    <parentid>419</parentid>
    <timestamp>2008-12-20T18:07:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="366" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VIX API referene Guide]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]


[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>5831f7b8d74248198f67045e447375eff33b22ab</sha1>
  </revision>
  <revision>
    <id>421</id>
    <parentid>420</parentid>
    <timestamp>2008-12-20T18:09:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="425" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX API referene Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]


[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>2991d0a8d35de387468ad89a62d0dab67c34e9e8</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>SDK</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>422</id>
    <parentid>123</parentid>
    <timestamp>2008-12-20T18:20:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="258" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

==== External links ====

[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's</text>
    <sha1>bb0e461b03fb158b7af611b6f990a0c6603c707a</sha1>
  </revision>
  <revision>
    <id>423</id>
    <parentid>422</parentid>
    <timestamp>2008-12-20T18:22:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="278" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

==== External links ====

[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's


[[Category: SDK]]</text>
    <sha1>7f339ac82b438c1c2ef235e1856aff5654c78cc9</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>VI Toolkit</title>
  <ns>0</ns>
  <id>19</id>
  <revision>
    <id>424</id>
    <parentid>93</parentid>
    <timestamp>2008-12-20T18:24:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="317" xml:space="preserve">The VMware Infrastructure Toolkit is the interface to the VMware Infrastructure API (VI API) for administering your virtual machines and hosts.

[[VI Toolkit for windows]]

[[VI Toolkit for perl]]

[[VMware Infrastructure Java API]]

===3rd party ===

* [[Vitforjava]] merged with the above project

[[Category: SDK]]</text>
    <sha1>887f8bc7d89cbaa2a0e5d76df2b74e3fe417730c</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Category:SDK</title>
  <ns>14</ns>
  <id>227</id>
  <revision>
    <id>425</id>
    <timestamp>2008-12-20T18:26:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Software Development Kits (SDK) and Application Programming Interfaces (API's) for managing VMware virtual machines and hosts.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">Software Development Kits (SDK) and Application Programming Interfaces (API's) for managing VMware virtual machines and hosts.</text>
    <sha1>a2341f5a38408f8fd3712163ad02c0a165998373</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Help:Contents</title>
  <ns>12</ns>
  <id>34</id>
  <revision>
    <id>428</id>
    <parentid>87</parentid>
    <timestamp>2008-12-20T18:49:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>changed to a more appropriate category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2767" xml:space="preserve">The VI-Toolkit site is a place for all to contribute their knowledge for the greater good.  Anyone who visits this website is invited to make a contribution.  This page contains a few tips for those who are new to the world of wikis.

Don't be afraid to have a go at something.  The worst that can happen is that someone else will either revert your contribution, or tidy it up to meet some standards of the site.

If you want to experiment with the wiki, then use the [[WikiPlayGround]] page.

==Getting started contributing content==

===Editing===
The wiki allows you to edit any page by clicking the 'edit' link at the bottom of the page.

===Adding a new page===
To add a new page you need to find an existing page and place a link to a new page on that .

You can create a link using

&lt;pre&gt;
[[&lt;link name&gt;]]
&lt;/pre&gt;

When trying to link to an existing page, remember that the links are case sensitive, so ''VMWARE'' doesn't equal ''VMware''.

If the link name isn't descriptive enough, then you can make it more so by adding some more text:

&lt;pre&gt;
[[&lt;link name&gt;|&lt;description&gt;]]
&lt;/pre&gt;

Links that are blue already exist, while red ones are pages that haven't been created.  If you click on a red link, you are taken to the edit screen where you can start writing.

So when you add to the wiki, you first create a link to the page and then you add the page (not the other way around which is the normal way in most systems).

===Adding source code===
Formatting source code works by inserting a single space in front of the source:

 vmkfstools -i /vmfs/volumes/templates/gold-master.vmdk /vmfs/volumes/myVMFS/myOS.vmdk


===External links===
An external link looks like this, the link and description are separated by a single space character.
&lt;pre&gt;
[&lt;link name&gt; &lt;description&gt;]
&lt;/pre&gt;

[http://www.google.com The google site]

You can also just put the link there, the wiki software will automatically change it into a clickable link

http://www.google.com

===Adding lists===

# This is a numbered list
# with several items
# added to it

and here's a list with bullet items
* item 1
* item 2
* item 3

== More advanced things ==
=== using categories ===
Use categories to sort items. Put Category tags at the end of the page.

For example (again, without spaces)
&lt;pre&gt;
[[Category:&lt;some category&gt;]] [[Category:&lt;some other category&gt;]]
&lt;/pre&gt;

To mark that one category is a subcategory of another, click on the link to go to your category page, and in there edit the category page itself to add a 'category' tag to where it should point.

[http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet More details on the wiki style formatting used (cheatsheet) in wikipedia web sites.]


Remember to put your category at the bottom of the edited text.

[[Category: website]]</text>
    <sha1>1d350afca369147ad7d890c53cfaa34b082093ed</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Category:Website</title>
  <ns>14</ns>
  <id>228</id>
  <revision>
    <id>430</id>
    <timestamp>2008-12-20T18:51:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Pages about the website itself, how to use it and how to navigate for example.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="78" xml:space="preserve">Pages about the website itself, how to use it and how to navigate for example.</text>
    <sha1>d9f92f1d8f0e49366fe04f349e86b0269834ff9d</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>431</id>
    <parentid>365</parentid>
    <timestamp>2008-12-20T18:52:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1094" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://teckinfo.blogspot.com Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.astroarch.com/ Edward Haletky's site]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>f504845b72af2a8c4f91b200a829232392395499</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>WikiPlayGround</title>
  <ns>0</ns>
  <id>35</id>
  <revision>
    <id>432</id>
    <parentid>85</parentid>
    <timestamp>2008-12-20T18:53:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="683" xml:space="preserve">==== Wiki Playground ====

You are ''' welcome ''' to make any changes in here and test out how a wiki works.

Click on the EDIT link at the bottom of the page to make changes or to have a look how this formatting works

# This is a numbered list
# with several items
# added to it

and here's a list with bullet items
* item 1
* item 2
* item 3

An external link looks like this

[http://www.google.com The google site]

Formatting source code works by inserting a single space in front of the script:

 vmkfstools -i /vmfs/volumes/templates/gold-master.vmdk /vmfs/volumes/myVMFS/myOS.vmdk

and if you want to put something in a category then do it like this:

[[Category: website]]</text>
    <sha1>4a67b5bd8814a25c5349c5439e9e158e835621bf</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>VI-Toolkit:About</title>
  <ns>4</ns>
  <id>4</id>
  <revision>
    <id>434</id>
    <parentid>155</parentid>
    <timestamp>2008-12-20T19:13:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1117" xml:space="preserve">==== About ====

This site is created in order to be able to store knowledge about Virtual Infrastructure and related VMware products.

At start, the site this will contain lots of links to information on the internet and have general information about how-to solve particular problems, but over time the intention is to move the focus slightly over to managing your Virtual Infrastructure using the toolkits available from VMware.

There are many ways in which you can manage your Virtual environment and it is intended that the way in which you can do this is documented on this site.

The site is initiated by [http://communities.vmware.com/people/wila Wil van Antwerpen] but everyone is welcome to add his or her notes and/or ideas. If you want to contact me then do so via my profile above or send me an email to wila at .... the domain name of the site here.

Hopefully this site will contribute to the general knowledge on managing your Virtualisation journey and help out on enjoying this journey as much as I do.

Below is a list of things completed for our site:
[[Vitoolkit: Status]]

[[Category: website]]</text>
    <sha1>6f52479f2f82c08ed4a3b041fce33dd6ee012fad</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>User:Wila</title>
  <ns>2</ns>
  <id>229</id>
  <revision>
    <id>435</id>
    <timestamp>2008-12-20T19:15:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>New page: See the [VI-Toolkit:About about page] if you want to know more about me :)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="74" xml:space="preserve">See the [VI-Toolkit:About about page] if you want to know more about me :)</text>
    <sha1>8a9f5694ca092827203ac50147901c2144d79b41</sha1>
  </revision>
  <revision>
    <id>436</id>
    <parentid>435</parentid>
    <timestamp>2008-12-20T19:16:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">See the [[VI-Toolkit:About |about page]] if you want to know more about me :)</text>
    <sha1>5394a3862188603d110a9c32f87a23147cb52eca</sha1>
  </revision>
  <revision>
    <id>439</id>
    <parentid>436</parentid>
    <timestamp>2008-12-20T19:37:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="173" xml:space="preserve">See the [[VI-Toolkit:About |about page]] if you want to know more about me :)

You can reach me by email by using my username here and sending it to the domain of this site.</text>
    <sha1>a9cbcd4de23c19c2c70ac503e42878fd8469c4cf</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>VI-Toolkit:Users</title>
  <ns>4</ns>
  <id>2</id>
  <revision>
    <id>438</id>
    <parentid>7</parentid>
    <timestamp>2008-12-20T19:31:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>improving the text</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1078" xml:space="preserve">=== Anonymous access ===
We do not allow anonymous edits on this web site. 
The sole reason for this is to combat spam. It would be awesome to allow completely anonymous edits, but I currently do not see how.
Please do ''' not let you stop that '''... getting an account for the site is about 2 minutes of ''work''.

=== Join Us! ===
You are welcome to add/edit content to the site after signing up for a user account.
Joining the site only requires a working email address and a name. We will under no circumstance abuse your email address or give it to someone else, it is only used for the initial sign up.

You can sign up [[Special:UserLogin| here]]

=== New content rules ===
When adding content there is a restriction that the subject must be about VMware related products, problems or solutions.
For the moment we do not welcome posts with a clear commercial intent where a user is endorsing his or her product.
This rule might change in the future, it is not cast in stone. 

If you have a question about that then send [[User:wila|me]] an email.

[[Category: website]]</text>
    <sha1>cca2365f42f5aebd461724b90d592530ed3b48f0</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsh: csinfo</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>440</id>
    <parentid>196</parentid>
    <timestamp>2008-12-20T19:44:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1729" xml:space="preserve">==== vimsh csinfo command ====
Usage: csinfo commandset

Displays information about a command set.


[/]$ csinfo plugin

===== Plugin commands =====

A plugin is a dynamic module that provides additional commands that can be
used to extend the capabilities of the shell.  A plugin is loaded by using
either puse or pload and specifying the file path of the plugin.  The file
path can be specified by an absolute path.  Relative paths may be used if a
list of search paths is provided using the ploadpath command.  A plugin is
named.  The names of loaded plugins can be determined using the [[vimsh: pls|pls]] command.
Plugins can be unloaded using the name.

The commands provided by a plugin are grouped into one or more command sets.
Each command set represents a logical grouping of commands that can be added
to the shell.  Like plugins, a command set is also named.  This name is used
for operations to manage command sets.  The list of available command sets
and the commands in each command set can be found using [[vimsh: csls|csls]].

To add commands to the shell, use [[vimsh: csimport|csimport]] to import a command set at a
particular place in the command namespace.  Each command set contains a
default location in the namespace, so no import point needs to be specified.
Command sets may be imported into existing command namespace folders so long
as the command names in the command set do not conflict with a name already
in the folder.  A command namespace folder is defined when commands exist
under the namespace and undefined when no commands exist.

The default import folder is '/'.

For more information about this command set:
  use '[[Vimsh: csls|csls plugin]]' to list its commands.

[[Category: Vimsh]]</text>
    <sha1>60a01bc336561c490f4a6babf61ba77847402737</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vmsvc/device.getdevices</title>
  <ns>0</ns>
  <id>161</id>
  <revision>
    <id>441</id>
    <parentid>316</parentid>
    <timestamp>2008-12-21T23:59:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9373" xml:space="preserve">==== vimsh vmsvc/device.getdevices ====
Usage: device.getdevices vmid

Retrieves and displays the virtual devices for the vm.

You can use [[vmsvc/getallvms]] to retrieve the vmid

==== Example output ====

 [/]$ vmsvc/device.getdevices 4404 
 Devices:
 
 (vim.vm.VirtualHardware) {
   dynamicType = &lt;unset&gt;,
   numCPU = 1,
   memoryMB = 512,
   device = (vim.vm.device.VirtualDevice) [
      (vim.vm.device.VirtualIDEController) {
         dynamicType = &lt;unset&gt;,
         key = 200,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "IDE 0",
            summary = "IDE 0",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = &lt;unset&gt;,
         unitNumber = &lt;unset&gt;,
         busNumber = 0,
         device = (int) [
            3000
         ],
      },
      (vim.vm.device.VirtualIDEController) {
         dynamicType = &lt;unset&gt;,
         key = 201,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "IDE 1",
            summary = "IDE 1",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = &lt;unset&gt;,
         unitNumber = &lt;unset&gt;,
         busNumber = 1,
      },
      (vim.vm.device.VirtualPS2Controller) {
         dynamicType = &lt;unset&gt;,
         key = 300,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "PS2 Controller ",
            summary = "PS2 Controller",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = &lt;unset&gt;,
         unitNumber = &lt;unset&gt;,
         busNumber = 0,
         device = (int) [
            600,
            700
         ],
      },
      (vim.vm.device.VirtualPCIController) {
         dynamicType = &lt;unset&gt;,
         key = 100,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "PCI Controller ",
            summary = "PCI Controller",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = &lt;unset&gt;,
         unitNumber = &lt;unset&gt;,
         busNumber = 0,
         device = (int) [
            500,
            4000,
            1000,
            11000
         ],
      },
      (vim.vm.device.VirtualSIOController) {
         dynamicType = &lt;unset&gt;,
         key = 400,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "SIO Controller ",
            summary = "SIO Controller",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = &lt;unset&gt;,
         unitNumber = &lt;unset&gt;,
         busNumber = 0,
         device = (int) [
            8000
         ],
      },
      (vim.vm.device.VirtualKeyboard) {
         dynamicType = &lt;unset&gt;,
         key = 600,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "Keyboard ",
            summary = "Keyboard",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = 300,
         unitNumber = 0,
      },
      (vim.vm.device.VirtualPointingDevice) {
         dynamicType = &lt;unset&gt;,
         key = 700,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "Pointing Device",
            summary = "Pointing device; Device",
         },
         backing = (vim.vm.device.VirtualPointingDevice.DeviceBackingInfo) {
            dynamicType = &lt;unset&gt;,
            deviceName = "",
            useAutoDetect = false,
            hostPointingDevice = "autodetect",
         },
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = 300,
         unitNumber = 1,
      },
      (vim.vm.device.VirtualVideoCard) {
         dynamicType = &lt;unset&gt;,
         key = 500,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "Video Card ",
            summary = "Video Card",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = 100,
         unitNumber = 0,
         videoRamSizeInKB = 4096,
      },
      (vim.vm.device.VirtualFloppy) {
         dynamicType = &lt;unset&gt;,
         key = 8000,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "Floppy Drive 1",
            summary = "Remote /dev/fd0",
         },
         backing = (vim.vm.device.VirtualFloppy.RemoteDeviceBackingInfo) {
            dynamicType = &lt;unset&gt;,
            deviceName = "/dev/fd0",
            useAutoDetect = false,
         },
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) {
            dynamicType = &lt;unset&gt;,
            startConnected = false,
            allowGuestControl = true,
            connected = false,
         },
         controllerKey = 400,
         unitNumber = 0,
      },
      (vim.vm.device.VirtualCdrom) {
         dynamicType = &lt;unset&gt;,
         key = 3000,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "CD/DVD Drive 1",
            summary = "ISO [] /iso-store/vmimages/jeos-i386.iso",
         },
         backing = (vim.vm.device.VirtualCdrom.IsoBackingInfo) {
            dynamicType = &lt;unset&gt;,
            fileName = "[] /iso-store/vmimages/jeos-i386.iso",
            datastore = &lt;unset&gt;,
         },
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) {
            dynamicType = &lt;unset&gt;,
            startConnected = false,
            allowGuestControl = true,
            connected = false,
         },
         controllerKey = 200,
         unitNumber = 0,
      },
      (vim.vm.device.VirtualPCNet32) {
         dynamicType = &lt;unset&gt;,
         key = 4000,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "Network Adapter 1",
            summary = "Virtual Machine Network",
         },
         backing = (vim.vm.device.VirtualEthernetCard.NetworkBackingInfo) {
            dynamicType = &lt;unset&gt;,
            deviceName = "Virtual Machine Network",
            useAutoDetect = false,
            network = 'vim.Network:HaNetwork-Virtual Machine Network',
         },
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) {
            dynamicType = &lt;unset&gt;,
            startConnected = true,
            allowGuestControl = true,
            connected = true,
         },
         controllerKey = 100,
         unitNumber = 7,
         addressType = "generated",
         macAddress = "00:0c:29:e2:84:2f",
         wakeOnLanEnabled = true,
      },
      (vim.vm.device.VirtualLsiLogicController) {
         dynamicType = &lt;unset&gt;,
         key = 1000,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "SCSI Controller 0",
            summary = "LSI Logic",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = 100,
         unitNumber = 3,
         busNumber = 0,
         device = (int) [
            2000
         ],
         hotAddRemove = true,
         sharedBus = "noSharing",
         scsiCtlrUnitNumber = 7,
      },
      (vim.vm.device.VirtualDisk) {
         dynamicType = &lt;unset&gt;,
         key = 2000,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "Hard Disk 1",
            summary = "14,194,304 KB",
         },
         backing = (vim.vm.device.VirtualDisk.FlatVer2BackingInfo) {
            dynamicType = &lt;unset&gt;,
            fileName = "[store] jeos/jeos.vmdk",
            datastore = 'vim.Datastore:1613fe4a-049423b7-0248-00026308922c',
            diskMode = "persistent",
            split = false,
            writeThrough = false,
            thinProvisioned = false,
            uuid = "3000D126-a0ce-3223-c32b-80e7e78180ef",
         },
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = 1000,
         unitNumber = 0,
         capacityInKB = 4194304,
         shares = (vim.SharesInfo) {
            dynamicType = &lt;unset&gt;,
            shares = 1000,
            level = "normal",
         },
      },
      (vim.vm.device.VirtualVMIROM) {
         dynamicType = &lt;unset&gt;,
         key = 11000,
         deviceInfo = (vim.Description) {
            dynamicType = &lt;unset&gt;,
            label = "Virtual Machine ROM",
            summary = "ROM on the virtual machine PCI bus that provides support for VMI",
         },
         backing = (vim.vm.device.VirtualDevice.BackingInfo) null,
         connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
         controllerKey = 100,
         unitNumber = 1,
      }
   ],
 }


[[Category: Vimsh]]</text>
    <sha1>e1d071a10ed824a2020d36bda207d1dcc97635c7</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/</title>
  <ns>0</ns>
  <id>230</id>
  <revision>
    <id>442</id>
    <timestamp>2008-12-22T00:03:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth ====   [[vimsvc/auth/admin_account_disable]]  [[vimsvc/auth/admin_account_enable]]  [[vimsvc/auth/admin_account_is_enabled]]  [[vimsvc/auth/entity_permission_add]]  ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="454" xml:space="preserve">==== vimsh vimsvc/auth ====

 [[vimsvc/auth/admin_account_disable]]
 [[vimsvc/auth/admin_account_enable]]
 [[vimsvc/auth/admin_account_is_enabled]]
 [[vimsvc/auth/entity_permission_add]]
 [[vimsvc/auth/entity_permission_remove]]
 [[vimsvc/auth/entity_permissions]]
 [[vimsvc/auth/permissions]]
 [[vimsvc/auth/privileges]]
 [[vimsvc/auth/role_add]]
 [[vimsvc/auth/role_permissions]]
 [[vimsvc/auth/role_remove]]
 [[vimsvc/auth/roles]]

[[Category: Vimsh]]</text>
    <sha1>fe8a448e0534a09e83623331041a3fcdc2569736</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/admin account disable</title>
  <ns>0</ns>
  <id>231</id>
  <revision>
    <id>443</id>
    <timestamp>2008-12-22T00:22:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/admin_account_disable ==== Usage: admin_account_disable  Disable admin account access.    [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== vimsh vimsvc/auth/admin_account_disable ====
Usage: admin_account_disable

Disable admin account access.


[[Category: Vimsh]]</text>
    <sha1>568fe6a84199c357bb0ffdd6d7915fe6ba44a5ac</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/admin account enable</title>
  <ns>0</ns>
  <id>232</id>
  <revision>
    <id>444</id>
    <timestamp>2008-12-22T00:23:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>New page: ==== vimsh vimsvc/auth/admin_account_enable ==== Usage: admin_account_enable  Enable admin account access.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="127" xml:space="preserve">==== vimsh vimsvc/auth/admin_account_enable ====
Usage: admin_account_enable

Enable admin account access.

[[Category: Vimsh]]</text>
    <sha1>3729a58055fa4e29da82d77ccf65b60f9d2e3a58</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/admin account is enabled</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>445</id>
    <timestamp>2008-12-22T00:25:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/admin_account_is_enabled ==== Usage: admin_account_is_enabled  Checks if admin account is enabled.  ==== Example output ====  [/]$ vimsvc/auth/admin_account_is_enabl...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="217" xml:space="preserve">==== vimsh vimsvc/auth/admin_account_is_enabled ====
Usage: admin_account_is_enabled

Checks if admin account is enabled.

==== Example output ====
 [/]$ vimsvc/auth/admin_account_is_enabled
 true

[[Category: Vimsh]]</text>
    <sha1>ee8ccf32418c8dce13e2d1af673db60f9ef6a0c4</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/entity permission add</title>
  <ns>0</ns>
  <id>234</id>
  <revision>
    <id>446</id>
    <timestamp>2008-12-26T14:23:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/entity_permission_add ==== Usage: entity_permission_add managed_entity user isGroup roleName propagate  Add permission rule for an entity.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">==== vimsh vimsvc/auth/entity_permission_add ====
Usage: entity_permission_add managed_entity user isGroup roleName propagate

Add permission rule for an entity.

[[Category: vimsh]]</text>
    <sha1>633c17e44d19f4e51ae34cbf1d4d4241cc6f6731</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/entity permission remove</title>
  <ns>0</ns>
  <id>235</id>
  <revision>
    <id>447</id>
    <timestamp>2008-12-26T14:24:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/entity_permission_remove ==== Usage: entity_permission_remove managed_entity user [isGroup]  Remove a permission rule from an entity.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="177" xml:space="preserve">==== vimsh vimsvc/auth/entity_permission_remove ====
Usage: entity_permission_remove managed_entity user [isGroup]

Remove a permission rule from an entity.

[[Category: vimsh]]</text>
    <sha1>5dc41fc102854d20068ae3859b685ff188244711</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/entity permissions</title>
  <ns>0</ns>
  <id>236</id>
  <revision>
    <id>448</id>
    <timestamp>2008-12-26T14:26:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/entity_permissions ==== Usage: entity_permissions managed_entity [effective]  Gets defined or effective permissions for an entity.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="174" xml:space="preserve">==== vimsh vimsvc/auth/entity_permissions ====
Usage: entity_permissions managed_entity [effective]

Gets defined or effective permissions for an entity.

[[Category: Vimsh]]</text>
    <sha1>6c0e6d22b652347187d5875e9293a8f180bb5b66</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/permissions</title>
  <ns>0</ns>
  <id>237</id>
  <revision>
    <id>449</id>
    <timestamp>2008-12-26T14:28:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/permissions ==== Usage: permissions  Get all the permissions defined in the system. This will list all the users and roles defined on your ESX host.  [[Category: vim...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="192" xml:space="preserve">==== vimsh vimsvc/auth/permissions ====
Usage: permissions

Get all the permissions defined in the system.
This will list all the users and roles defined on your ESX host.

[[Category: vimsh]]</text>
    <sha1>07263f928cd8be80ae4cf7bec1b15fc103e5e6ae</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/privileges</title>
  <ns>0</ns>
  <id>238</id>
  <revision>
    <id>450</id>
    <timestamp>2008-12-26T14:30:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/privileges ==== Usage: privileges  Get the list of system-defined privileges.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="121" xml:space="preserve">==== vimsh vimsvc/auth/privileges ====
Usage: privileges

Get the list of system-defined privileges.

[[Category: vimsh]]</text>
    <sha1>4ff85d1bfaef4b28dd24ac49d8467bf24e2f425a</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/role add</title>
  <ns>0</ns>
  <id>239</id>
  <revision>
    <id>451</id>
    <timestamp>2008-12-26T14:32:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/role_add ==== Usage: role_add roleName [priv0] [priv1] [priv2] [priv3] [priv4]  Add a named role with the following privileges.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="171" xml:space="preserve">==== vimsh vimsvc/auth/role_add ====
Usage: role_add roleName [priv0] [priv1] [priv2] [priv3] [priv4]

Add a named role with the following privileges.

[[Category: vimsh]]</text>
    <sha1>758119f34d4f5b57aead92cf6101db60719a1a36</sha1>
  </revision>
</page>
<page arvcontinue="20081219050558|403">
  <title>Vimsvc/auth/role permissions</title>
  <ns>0</ns>
  <id>240</id>
  <revision>
    <id>452</id>
    <timestamp>2008-12-26T14:33:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/role_permissions ==== Usage: role_permissions roleName  Gets defined permissions associated with a role.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="148" xml:space="preserve">==== vimsh vimsvc/auth/role_permissions ====
Usage: role_permissions roleName

Gets defined permissions associated with a role.

[[Category: Vimsh]]</text>
    <sha1>a4a69739ded726a40650f18b2e7a41c46b979ea5</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Vimsvc/auth/role remove</title>
  <ns>0</ns>
  <id>241</id>
  <revision>
    <id>453</id>
    <timestamp>2008-12-26T14:34:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/role_remove ==== Usage: role_remove roleName [failIfUsed]  Remove a named role.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="123" xml:space="preserve">==== vimsh vimsvc/auth/role_remove ====
Usage: role_remove roleName [failIfUsed]

Remove a named role.

[[Category: Vimsh]]</text>
    <sha1>741280f64694ba9dd8ad3050d51c99add3c91a84</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Vimsvc/auth/roles</title>
  <ns>0</ns>
  <id>242</id>
  <revision>
    <id>454</id>
    <timestamp>2008-12-26T14:35:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh vimsvc/auth/roles ==== Usage: roles  Get the list of currently defined roles.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">==== vimsh vimsvc/auth/roles ====
Usage: roles

Get the list of currently defined roles.

[[Category: Vimsh]]</text>
    <sha1>7af7f5425541fc15a4c93c4febc5293b838a91c7</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Vimsh: proxysvc/</title>
  <ns>0</ns>
  <id>49</id>
  <revision>
    <id>455</id>
    <parentid>188</parentid>
    <timestamp>2008-12-26T14:41:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="391" xml:space="preserve"> [/]$ proxysvc/   
 add_np_service   connect          logout           remove_service   
 add_tcp_service  login              port_info        service_list


 [[proxysvc/add_np_service]]  
 [[proxysvc/add_tcp_service]] 
 [[proxysvc/connect]]    
 [[proxysvc/login]]
 [[proxysvc/logout]]
 [[proxysvc/port_info]]
 [[proxysvc/remove_service]]   
 [[proxysvc/service_list]]


[[Category: Vimsh]]</text>
    <sha1>d8fd73ab8519413e82c322cceab084d6271fa316</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Proxysvc/add np service</title>
  <ns>0</ns>
  <id>243</id>
  <revision>
    <id>456</id>
    <timestamp>2008-12-26T14:42:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh proxysvc/add_np_service ==== Usage: add_np_service namespace accessMode pipeName  Adds a given Named Pipe service to the proxy service list.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">==== vimsh proxysvc/add_np_service ====
Usage: add_np_service namespace accessMode pipeName

Adds a given Named Pipe service to the proxy service list.

[[Category: Vimsh]]</text>
    <sha1>8590a685ad7c5ccead18c1a0354bc734c8df5147</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Proxysvc/add tcp service</title>
  <ns>0</ns>
  <id>244</id>
  <revision>
    <id>457</id>
    <timestamp>2008-12-26T15:17:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh proxysvc/add_tcp_service ==== Usage: add_tcp_service namespace accessMode hostName port  Adds a given TCP service to the proxy service list.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">==== vimsh proxysvc/add_tcp_service ====
Usage: add_tcp_service namespace accessMode hostName port

Adds a given TCP service to the proxy service list.

[[Category: Vimsh]]</text>
    <sha1>a6d47fb00278552dc8f285514fd9883de5b389ac</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Proxysvc/connect</title>
  <ns>0</ns>
  <id>245</id>
  <revision>
    <id>458</id>
    <timestamp>2008-12-26T15:21:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh proxysvc/connect ==== Usage: connect [hostname] [port] [key] [cert] [product]  Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key an...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="435" xml:space="preserve">==== vimsh proxysvc/connect ====
Usage: connect [hostname] [port] [key] [cert] [product]

Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and a certificate.

By default product is 'solo', hostname is 'localhost'.

* Port is 902.
* private key is at /etc/vmware/ssl/rui.key
* certificate is at /etc/vmware/ssl/rui.crt

To disable SSL, use an empty key or certificate.

[[Category: vimsh]]</text>
    <sha1>21e7dd693e2b275ada14f67c12db681a095c92b3</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Proxysvc/login</title>
  <ns>0</ns>
  <id>246</id>
  <revision>
    <id>459</id>
    <timestamp>2008-12-26T15:22:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh proxysvc/login ==== Usage: login [username] [password]  Logs in to host, creating a new session.  If no password is specified, will use a local authentication mechanism.  [[Cate...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="202" xml:space="preserve">==== vimsh proxysvc/login ====
Usage: login [username] [password]

Logs in to host, creating a new session.  If no password is specified, will
use a local authentication mechanism.

[[Category: Vimsh ]]</text>
    <sha1>ce12d62971017ed36b11c312ddc900452c97b935</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Proxysvc/logout</title>
  <ns>0</ns>
  <id>247</id>
  <revision>
    <id>460</id>
    <timestamp>2008-12-26T15:23:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh proxysvc/logout ==== Usage: logout  Logs out from host, destroying existing session.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="116" xml:space="preserve">==== vimsh proxysvc/logout ====
Usage: logout

Logs out from host, destroying existing session.

[[Category: Vimsh]]</text>
    <sha1>c33f1d39715e2e85875e3a9a2de926506c273a2c</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Proxysvc/port info</title>
  <ns>0</ns>
  <id>248</id>
  <revision>
    <id>461</id>
    <timestamp>2008-12-26T15:24:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh proxysvc/port_info ==== Usage: port_info  Display the ports that the proxy is listening on.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="123" xml:space="preserve">==== vimsh proxysvc/port_info ====
Usage: port_info

Display the ports that the proxy is listening on.

[[Category: Vimsh]]</text>
    <sha1>5d5abaac1e1bbd549f25359f06bd1123eb141b82</sha1>
  </revision>
  <revision>
    <id>462</id>
    <parentid>461</parentid>
    <timestamp>2008-12-26T15:26:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="247" xml:space="preserve">==== vimsh proxysvc/port_info ====
Usage: port_info

Display the ports that the proxy is listening on.

==== Example output ====
Here's the output of a default setup:
 [/]$ proxysvc/port_info   
 Http Port: 80
 Https Port: 443

[[Category: Vimsh]]</text>
    <sha1>1ecbecf1ef32379b2ade36a40240aaeb3bb37792</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Proxysvc/remove service</title>
  <ns>0</ns>
  <id>249</id>
  <revision>
    <id>463</id>
    <timestamp>2008-12-26T15:27:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh proxysvc/remove_service ==== Usage: remove_service namespace accessMode  Removes a specified service from the Proxy service list..  [[Category: Vimsh ]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">==== vimsh proxysvc/remove_service ====
Usage: remove_service namespace accessMode

Removes a specified service from the Proxy service list..

[[Category: Vimsh ]]</text>
    <sha1>fc0c7427c3d83a0961e029c227bfd91558b18c5c</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Proxysvc/service list</title>
  <ns>0</ns>
  <id>250</id>
  <revision>
    <id>464</id>
    <timestamp>2008-12-26T15:28:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh proxysvc/service_list ==== Usage: service_list  Get the list of services being proxied.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="120" xml:space="preserve">==== vimsh proxysvc/service_list ====
Usage: service_list

Get the list of services being proxied.


[[Category: Vimsh]]</text>
    <sha1>7a4a3acfe80192fcf58134085e419e93d01f431e</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Vimsh: internalsvc/</title>
  <ns>0</ns>
  <id>48</id>
  <revision>
    <id>465</id>
    <parentid>187</parentid>
    <timestamp>2008-12-26T15:36:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1286" xml:space="preserve"> [/]$ internalsvc/
 perfcount/              redirect_stderr           refresh_pnic            
 access_address      redirect_stdout           set_exception_variable  
 connect                  refresh                      set_log_level           
 host_mode_lock     refresh_consolenic      shutdown                
 login                     refresh_datastores      throw_exception         
 loglist                    refresh_gateway         use_fds                 
 logout                   refresh_network


 [[internalsvc/perfcount/]]       
 [[internalsvc/access_address]]
 [[internalsvc/connect]]           
 [[internalsvc/host_mode_lock]]            
 [[internalsvc/login]]     
 [[internalsvc/loglist]]             
 [[internalsvc/logout]]   
 [[internalsvc/redirect_stderr]]      
 [[internalsvc/redirect_stdout]]
 [[internalsvc/refresh]]       
 [[internalsvc/refresh_consolenic]]            
 [[internalsvc/refresh_datastores]]      
 [[internalsvc/refresh_gateway]]               
 [[internalsvc/refresh_network]]
 [[internalsvc/refresh_pnic]]            
 [[internalsvc/set_exception_variable]]  
 [[internalsvc/set_log_level]]           
 [[internalsvc/shutdown]]                
 [[internalsvc/throw_exception]]         
 [[internalsvc/use_fds]]


[[Category: Vimsh]]</text>
    <sha1>2324a986f98da6591255fe3a98453a3ffe4bbdd5</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/access address</title>
  <ns>0</ns>
  <id>251</id>
  <revision>
    <id>466</id>
    <timestamp>2008-12-27T11:21:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/access_address ==== Usage: access_address [address]  Throw a general purpose exception  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="130" xml:space="preserve">==== vimsh internalsvc/access_address ====
Usage: access_address [address]

Throw a general purpose exception

[[Category: vimsh]]</text>
    <sha1>f9e56b773caa0fa0fbb5d2a8340f405d06b91219</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/connect</title>
  <ns>0</ns>
  <id>252</id>
  <revision>
    <id>467</id>
    <timestamp>2008-12-27T11:22:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== internalsvc/connect ==== Usage: connect [hostname] [port] [key] [cert] [product]  Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and a...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="432" xml:space="preserve">==== internalsvc/connect ====
Usage: connect [hostname] [port] [key] [cert] [product]

Connects to product (solo|vpxa|vpxd) listening at hostname on TCP port port using a private key and a certificate.

By default product is 'solo', hostname is 'localhost'.

* Port is 902.
* private key is at /etc/vmware/ssl/rui.key
* certificate is at /etc/vmware/ssl/rui.crt

To disable SSL, use an empty key or certificate.

[[Category: Vimsh]]</text>
    <sha1>618c7357faefab44b26496fbd17bbaa2a99dfd2e</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/host mode lock</title>
  <ns>0</ns>
  <id>253</id>
  <revision>
    <id>468</id>
    <timestamp>2008-12-27T11:23:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/host_mode_lock ====  Usage: host_mode_lock lock mode  Acquires or releases a mode lock on the host system.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">==== vimsh internalsvc/host_mode_lock ====

Usage: host_mode_lock lock mode

Acquires or releases a mode lock on the host system.


[[Category: Vimsh]]</text>
    <sha1>67c6b9773779aecd8dba540a74f54f9760919563</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/login</title>
  <ns>0</ns>
  <id>254</id>
  <revision>
    <id>469</id>
    <timestamp>2008-12-27T11:25:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/login ==== Usage: login [username] [password]  Logs in to host, creating a new session.  If no password is specified, will use a local authentication mechanism.  [[C...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="204" xml:space="preserve">==== vimsh internalsvc/login ====
Usage: login [username] [password]

Logs in to host, creating a new session.  If no password is specified, will
use a local authentication mechanism.

[[Category: Vimsh]]</text>
    <sha1>00f35aa1df01c44aacca3de9263b9df6474e054f</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/loglist</title>
  <ns>0</ns>
  <id>255</id>
  <revision>
    <id>470</id>
    <timestamp>2008-12-27T11:26:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/loglist ==== Usage: loglist [prefix]  Get the list of loggers that can be configured  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="128" xml:space="preserve">==== vimsh internalsvc/loglist ====
Usage: loglist [prefix]

Get the list of loggers that can be configured

[[Category: Vimsh]]</text>
    <sha1>2e7eb239a1a7f91ef44c5a42a1ee1d63a5f7e4d5</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/logout</title>
  <ns>0</ns>
  <id>256</id>
  <revision>
    <id>471</id>
    <timestamp>2008-12-27T11:27:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/logout ====  Usage: logout  Logs out from host, destroying existing session.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="120" xml:space="preserve">==== vimsh internalsvc/logout ====

Usage: logout

Logs out from host, destroying existing session.

[[Category: Vimsh]]</text>
    <sha1>31224c2cf89ffe48d9003a65b28c26330a9b7f39</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/redirect stderr</title>
  <ns>0</ns>
  <id>257</id>
  <revision>
    <id>472</id>
    <timestamp>2008-12-27T11:28:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/redirect_stderr ==== Usage: redirect_stderr file path  Redirects stderr for hostd to a file.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="136" xml:space="preserve">==== vimsh internalsvc/redirect_stderr ====
Usage: redirect_stderr file path

Redirects stderr for hostd to a file.

[[Category: Vimsh]]</text>
    <sha1>2c520e7097aea0879ea9115636bf635954d8c153</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/redirect stdout</title>
  <ns>0</ns>
  <id>258</id>
  <revision>
    <id>473</id>
    <timestamp>2008-12-27T11:30:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/redirect_stdout ==== Usage: redirect_stdout file_path [redirect_stderr]  Redirects stdout for hostd to a file.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="154" xml:space="preserve">==== vimsh internalsvc/redirect_stdout ====
Usage: redirect_stdout file_path [redirect_stderr]

Redirects stdout for hostd to a file.

[[Category: Vimsh]]</text>
    <sha1>9b111a32b95480a9c81cfc7608a2576c624be16a</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/refresh</title>
  <ns>0</ns>
  <id>259</id>
  <revision>
    <id>474</id>
    <timestamp>2008-12-27T11:30:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/refresh ==== Usage: refresh [name]  Refreshes the system.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="102" xml:space="preserve">==== vimsh internalsvc/refresh ====
Usage: refresh [name]

Refreshes the system.


[[Category: Vimsh]]</text>
    <sha1>5804f1cd01bbf028b060c225ba025866b8448f1d</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/refresh consolenic</title>
  <ns>0</ns>
  <id>260</id>
  <revision>
    <id>475</id>
    <timestamp>2008-12-27T11:31:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/refresh_consolenic ==== Usage: refresh_consolenic  Refreshes the service console nic on the host system.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="148" xml:space="preserve">==== vimsh internalsvc/refresh_consolenic ====
Usage: refresh_consolenic

Refreshes the service console nic on the host system.

[[Category: Vimsh]]</text>
    <sha1>95e6e558c7b64b0c4176557755c176ead978510a</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/refresh datastores</title>
  <ns>0</ns>
  <id>261</id>
  <revision>
    <id>476</id>
    <timestamp>2008-12-27T12:07:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/refresh_datastores ==== Usage: refresh_datastores  Refreshes the datastore inventory on the host system.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="148" xml:space="preserve">==== vimsh internalsvc/refresh_datastores ====
Usage: refresh_datastores

Refreshes the datastore inventory on the host system.

[[Category: Vimsh]]</text>
    <sha1>744c0746972a36fd085d30fd0a08c08f993c1465</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/refresh gateway</title>
  <ns>0</ns>
  <id>262</id>
  <revision>
    <id>477</id>
    <timestamp>2008-12-27T12:08:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/refresh_gateway ==== Usage: refresh_gateway  Refreshes the vmkernel default gateway.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="128" xml:space="preserve">==== vimsh internalsvc/refresh_gateway ====
Usage: refresh_gateway

Refreshes the vmkernel default gateway.

[[Category: Vimsh]]</text>
    <sha1>3b8577b0d507f80d8be49d76fa6e31a30f40d301</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/refresh network</title>
  <ns>0</ns>
  <id>263</id>
  <revision>
    <id>478</id>
    <timestamp>2008-12-27T12:08:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/refresh_network ==== Usage: refresh_network  Refreshes the network configuration on the host system.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">==== vimsh internalsvc/refresh_network ====
Usage: refresh_network

Refreshes the network configuration on the host system.

[[Category: Vimsh]]</text>
    <sha1>11dd950246df63ec6b4af2d36f370658ff09330b</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/refresh pnic</title>
  <ns>0</ns>
  <id>264</id>
  <revision>
    <id>479</id>
    <timestamp>2008-12-27T12:09:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/refresh_pnic ==== Usage: refresh_pnic pnic  Refreshes the service console nic on the host system.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="141" xml:space="preserve">==== vimsh internalsvc/refresh_pnic ====
Usage: refresh_pnic pnic

Refreshes the service console nic on the host system.

[[Category: Vimsh]]</text>
    <sha1>34d609c1be9748d4d68e08cc9f0093cd233bf3cf</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/set exception variable</title>
  <ns>0</ns>
  <id>265</id>
  <revision>
    <id>480</id>
    <timestamp>2008-12-27T12:10:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/set_exception_variable ==== Usage: set_exception_variable variable value  Sets an exception variable for hostd  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="154" xml:space="preserve">==== vimsh internalsvc/set_exception_variable ====
Usage: set_exception_variable variable value

Sets an exception variable for hostd

[[Category: Vimsh]]</text>
    <sha1>5755d406809e6905ec052b1b1701072fc6404380</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/set log level</title>
  <ns>0</ns>
  <id>266</id>
  <revision>
    <id>481</id>
    <timestamp>2008-12-27T12:11:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== internalsvc/set_log_level ==== Usage: set_log_level name logLevel recurse  Set the level for a logger  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="127" xml:space="preserve">==== internalsvc/set_log_level ====
Usage: set_log_level name logLevel recurse

Set the level for a logger

[[Category: Vimsh]]</text>
    <sha1>c8532698db18a0d09b92a2094bf371de4dacb951</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/shutdown</title>
  <ns>0</ns>
  <id>267</id>
  <revision>
    <id>482</id>
    <timestamp>2008-12-27T12:12:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/shutdown ==== Usage: shutdown  Shutdown hostd service  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="97" xml:space="preserve">==== vimsh internalsvc/shutdown ====
Usage: shutdown

Shutdown hostd service

[[Category: Vimsh]]</text>
    <sha1>94ed5d4473c8d8c4f985fb15020ee8aced8a0e8e</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/throw exception</title>
  <ns>0</ns>
  <id>268</id>
  <revision>
    <id>483</id>
    <timestamp>2008-12-27T12:12:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/throw_exception ====  Usage: throw_exception message  Throw a general purpose exception   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== vimsh internalsvc/throw_exception ====

Usage: throw_exception message

Throw a general purpose exception


[[Category: Vimsh]]</text>
    <sha1>12fb30fcacae605fcaec3f7bd818c65db279cdea</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/use fds</title>
  <ns>0</ns>
  <id>269</id>
  <revision>
    <id>484</id>
    <timestamp>2008-12-27T12:13:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/use_fds ====  Usage: use_fds [numFds]  Use up a certain number of fds (or decrement the fds in use)  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="143" xml:space="preserve">==== vimsh internalsvc/use_fds ====

Usage: use_fds [numFds]

Use up a certain number of fds (or decrement the fds in use)

[[Category: Vimsh]]</text>
    <sha1>5a0756b8f20d1d3b4e4240637ac98f2c66d5598a</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/perfcount/</title>
  <ns>0</ns>
  <id>270</id>
  <revision>
    <id>485</id>
    <timestamp>2008-12-27T12:17:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/perfcount/ ====  Performance counters   [[internalsvc/perfcount/enumerate]]  [[internalsvc/perfcount/query_destroy]]  [[internalsvc/perfcount/query_execute]]  [[inte...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="393" xml:space="preserve">==== vimsh internalsvc/perfcount/ ====

Performance counters

 [[internalsvc/perfcount/enumerate]]
 [[internalsvc/perfcount/query_destroy]]
 [[internalsvc/perfcount/query_execute]]
 [[internalsvc/perfcount/query_info]]
 [[internalsvc/perfcount/query_list]]
 [[internalsvc/perfcount/query_names]]
 [[internalsvc/perfcount/query_regex]]
 [[internalsvc/perfcount/scoreboard]]

[[Category: Vimsh]]</text>
    <sha1>bdd733e435406be74a52bdb402e981af951b2065</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>VI-Toolkit:Community Portal</title>
  <ns>4</ns>
  <id>6</id>
  <revision>
    <id>486</id>
    <parentid>414</parentid>
    <timestamp>2008-12-27T12:42:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Corrected download link VI-RCLI to VI-RCLI-U2.. there _is_ an update woohoo :)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1792" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management console, a stripped down linux console which was could be used for automating and managing your virtual machines. As of ESX 3.5i this is no longer available and the future is to move away from the fat hypervisor. In order to manage your virtual machines in a similar way as before, we now have special virtual machines that come with management software pre-installed. VMware delivers 2 appliances for this, the VIMA and the RCLI.

* [http://www.vmware.com/support/developer/vima/index.html VMware Infrastructure Management Assistant (VIMA)]

This is a 64bits virtual machine based on RHEL. 

Features that VIMA has over the RCLI:
* component for caching authentication 
* component for collecting ESX log files (remote logging)
* Designed to host agents that will be released by some 3rd party developers
* Includes a mechanism for VMware to provide updates
* Supported for production use

* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on Ubuntu JEOS
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not)
# There is also a windows installed.</text>
    <sha1>c231dda87c842e0966d9b6d37074076b816f25aa</sha1>
  </revision>
  <revision>
    <id>487</id>
    <parentid>486</parentid>
    <timestamp>2008-12-28T18:22:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>moving VIMA to its own page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1342" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management console, a stripped down linux console which was could be used for automating and managing your virtual machines. As of ESX 3.5i this is no longer available and the future is to move away from the fat hypervisor. In order to manage your virtual machines in a similar way as before, we now have special virtual machines that come with management software pre-installed. VMware delivers 2 appliances for this, the [[VIMA]] and the [[RCLI]].


* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on Ubuntu JEOS
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not)
# There is also a windows installed.</text>
    <sha1>f7397ceaec50e407ec9bee2a7dd925e21af2baf6</sha1>
  </revision>
  <revision>
    <id>489</id>
    <parentid>487</parentid>
    <timestamp>2008-12-28T18:24:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Moving RCLI to its own page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="948" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management console, a stripped down linux console which was could be used for automating and managing your virtual machines. As of ESX 3.5i this is no longer available and the future is to move away from the fat hypervisor. In order to manage your virtual machines in a similar way as before, we now have special virtual machines that come with management software pre-installed. VMware delivers 2 appliances for this, the [[VIMA]] and the [[RCLI]].</text>
    <sha1>233619b1fdadb5ee41fd217cfc022177ccdcdae2</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>VIMA</title>
  <ns>0</ns>
  <id>271</id>
  <revision>
    <id>488</id>
    <timestamp>2008-12-28T18:23:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: * [http://www.vmware.com/support/developer/vima/index.html VMware Infrastructure Management Assistant (VIMA)]  This is a 64bits virtual machine based on RHEL.   Features that VIMA has over...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="480" xml:space="preserve">* [http://www.vmware.com/support/developer/vima/index.html VMware Infrastructure Management Assistant (VIMA)]

This is a 64bits virtual machine based on RHEL. 

Features that VIMA has over the [[RCLI]]:
* component for caching authentication 
* component for collecting ESX log files (remote logging)
* Designed to host agents that will be released by 3rd party developers
* Includes a mechanism for VMware to provide updates
* The appliance itself is supported for production use</text>
    <sha1>6c49d49a9e9f7ddf762c5234fab9f2c942be7eb8</sha1>
  </revision>
  <revision>
    <id>493</id>
    <parentid>488</parentid>
    <timestamp>2008-12-28T18:31:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="624" xml:space="preserve">====VMware Infrastructure Management Assistant (VIMA)====

This is a 64bits virtual machine based on RHEL. 

Features that VIMA has over the [[RCLI]]:
* component for caching authentication 
* component for collecting ESX log files (remote logging)
* Designed to host agents that will be released by 3rd party developers
* Includes a mechanism for VMware to provide updates
* The appliance itself is supported for production use

=====links=====
* [http://www.vmware.com/support/developer/vima/index.html VMware Infrastructure Management Assistant (VIMA)]

* [[ESX3i_Remote_CLI_documentation|ESX3i Remote CLI documentation]]</text>
    <sha1>fa0d06431cc8aeae6c78f0100e8872fb463a0b3f</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>RCLI</title>
  <ns>0</ns>
  <id>272</id>
  <revision>
    <id>490</id>
    <timestamp>2008-12-28T18:27:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ====VI Remote Commandline Interface====  This comes in  several flavors. # You can download it as a small 32 bit virtual machine based on Ubuntu JEOS  # There is a separate linux setup so ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="613" xml:space="preserve">====VI Remote Commandline Interface====

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on Ubuntu JEOS 
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not)
# There is also a windows installable version.

At the moment of writing only the installable versions are supported for production use. 
The appliance isn't yet supported in a production environment.

=====links=====
* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]</text>
    <sha1>1330ed4de31557d4e961925adf03c38ad1ef2190</sha1>
  </revision>
  <revision>
    <id>491</id>
    <parentid>490</parentid>
    <timestamp>2008-12-28T18:29:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="650" xml:space="preserve">====VI Remote Commandline Interface====

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on Ubuntu JEOS 
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not)
# There is also a windows installable version.

At the moment of writing only the installable versions are supported for production use. 
The appliance isn't yet supported in a production environment.

=====links=====
* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]
* [[ESX3i_Remote_CLI_documentation]]</text>
    <sha1>0df3498ad26b613cbead21885a3185e8228db810</sha1>
  </revision>
  <revision>
    <id>492</id>
    <parentid>491</parentid>
    <timestamp>2008-12-28T18:30:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added link to doc</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="681" xml:space="preserve">====VI Remote Commandline Interface====

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on Ubuntu JEOS 
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not)
# There is also a windows installable version.

At the moment of writing only the installable versions are supported for production use. 
The appliance isn't yet supported in a production environment.

=====links=====
* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]
* [[ESX3i_Remote_CLI_documentation|ESX3i Remote CLI documentation]]</text>
    <sha1>ea2f749f296ebd8b47876590c7a01c488d9ab20b</sha1>
  </revision>
  <revision>
    <id>494</id>
    <parentid>492</parentid>
    <timestamp>2008-12-28T18:55:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="910" xml:space="preserve">====VI Remote Commandline Interface====

This comes in  several flavors.
# You can download it as a small 32 bit virtual machine based on debian sarge 3.1 kernel 2.4.27 (the documentation says its a centOS version, but why then does it support apt-get and not yum and what's the /etc/debian_version file doing there..)
# There is a separate linux setup so that you can install it in your own linux machine (virtual or not). Supported environments are Ubuntu Desktop 7.1 and RHEL 5.1.
# There is also a windows installable version.

At the moment of writing only the installable versions are supported for production use. 
The appliance isn't yet supported in a production environment.

=====links=====
* [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 Virtual Infrastructure Remote Commandline Interface appliance (RCLI)]
* [[ESX3i_Remote_CLI_documentation|ESX3i Remote CLI documentation]]</text>
    <sha1>c5e9eaa83e85148add0890fde7eafcfb5220fec0</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>495</id>
    <parentid>421</parentid>
    <timestamp>2008-12-28T19:04:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added links to VMWareTasks and vixCOMWrapper</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="461" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>8fa40aba33a09faf9bee38495dc37be5362a523a</sha1>
  </revision>
  <revision>
    <id>500</id>
    <parentid>495</parentid>
    <timestamp>2008-12-28T21:01:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="560" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>7043d34e048faff40fd11673f7dadd849a3d3b46</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>VMWareTasks</title>
  <ns>0</ns>
  <id>273</id>
  <revision>
    <id>496</id>
    <timestamp>2008-12-28T19:07:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ====VMWareTasks====  VMWareTasks is a C# library on top of the VIX API. It exposes a better programming model for the 99% of those synchronous VMWare scenarios where you don't want to deal...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="485" xml:space="preserve">====VMWareTasks====

VMWareTasks is a C# library on top of the VIX API. It exposes a better programming model for the 99% of those synchronous VMWare scenarios where you don't want to deal with jobs or other more complex constructs.


* http://www.codeproject.com/KB/library/VMWareTasks.aspx

* http://code.dblock.org/ShowPost.aspx?id=25

* [http://communities.vmware.com/thread/186164 VMWareTasks: A VIX API C# Library (let's reinvent less wheels)]

[[Category: VIX]][[Category: SDK]]</text>
    <sha1>1f4c285d89440ff1d9498d8f6f24eb4ebd20eb7e</sha1>
  </revision>
  <revision>
    <id>498</id>
    <parentid>496</parentid>
    <timestamp>2008-12-28T19:12:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="518" xml:space="preserve">====VMWareTasks====

VMWareTasks is a C# library on top of the VIX API. It exposes a better programming model for the 99% of those synchronous VMWare scenarios where you don't want to deal with jobs or other more complex constructs.

====Project====
* http://www.codeproject.com/KB/library/VMWareTasks.aspx

* http://code.dblock.org/ShowPost.aspx?id=25

====See also====
* [http://communities.vmware.com/thread/186164 VMWareTasks: A VIX API C# Library (let's reinvent less wheels)]


[[Category: VIX]][[Category: SDK]]</text>
    <sha1>4abe6d5be5d1744b8460755be09b03cb0a5e290d</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>VixCOMWrapper</title>
  <ns>0</ns>
  <id>274</id>
  <revision>
    <id>497</id>
    <timestamp>2008-12-28T19:12:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ====vixCOMWrapper==== Simplify dealing with the VIX API when using C# and make common tasks (powering on/off, copying files) a lot easier.   ====Project==== * http://www.codeplex.com/VixCO...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="362" xml:space="preserve">====vixCOMWrapper====
Simplify dealing with the VIX API when using C# and make common tasks (powering on/off, copying files) a lot easier. 

====Project====
* http://www.codeplex.com/VixCOMWrapper

====See also====
* [http://communities.vmware.com/thread/186164 VMWareTasks: A VIX API C# Library (let's reinvent less wheels)]


[[Category: VIX]][[Category: SDK]]</text>
    <sha1>108c220aa9dc06b48a89990ddd12e21440c88b29</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Category:VIX</title>
  <ns>14</ns>
  <id>275</id>
  <revision>
    <id>499</id>
    <timestamp>2008-12-28T19:14:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Virtual Machine Automation API category.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="40" xml:space="preserve">Virtual Machine Automation API category.</text>
    <sha1>76458b0c18f4703d771f4ced00ceec625f690d00</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Internalsvc/perfcount/enumerate</title>
  <ns>0</ns>
  <id>276</id>
  <revision>
    <id>501</id>
    <timestamp>2008-12-28T21:30:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/perfcount/enumerate ====  Usage: enumerate registry_path  Enumerate paths in the registry.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== vimsh internalsvc/perfcount/enumerate ====

Usage: enumerate registry_path

Enumerate paths in the registry.

[[Category: Vimsh]]</text>
    <sha1>8f0569681339417b863b05b792ede3f4e1cf3d4d</sha1>
  </revision>
</page>
<page arvcontinue="20081226143416|453">
  <title>Vmware-vim-cmd</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>502</id>
    <parentid>128</parentid>
    <timestamp>2008-12-28T21:33:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="807" xml:space="preserve">==== Vmware-vim-cmd ====

The command line version of the [[vimsh]] command.
This can be used in your scripts and replaces the alternative 
 vimsh -n -e &lt;command&gt;

so now you can use:
 vmware-vim-cmd &lt;command&gt;

 Usage: /usr/lib/vmware/hostd/vmware-vim-cmd [options]... command [cmd_arg1] [cmd_arg2] ...
 
 Options:
   -h           Display this help message and exit
   -v           Display version information and exit
   -H &lt;host&gt;    Host name to connect
   -O &lt;port&gt;    Port number to connect
   -U &lt;user&gt;    User name to use for login
   -P &lt;pass&gt;    Password to use for login
   -d &lt;level&gt;   Show verbose debug output. (info, verbose, trivia)

Use the help command to get information on the commands available.

   /usr/lib/vmware/hostd/vmware-vim-cmd help [command]


[[Category: ESX]][[Category: SDK]]</text>
    <sha1>eceb732f9da03269f2d730c4935adfb0e02826bc</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/loglist</title>
  <ns>0</ns>
  <id>255</id>
  <revision>
    <id>503</id>
    <parentid>470</parentid>
    <timestamp>2008-12-28T21:44:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13582" xml:space="preserve">==== vimsh internalsvc/loglist ====
Usage: loglist [prefix]

Get the list of loggers that can be configured

==== example output ====
Here is an example of the output on a pristine ESX3.5i setup that has only one VM called trustix.

# vmware-vim-cmd -H 10.10.10.10 -U root -P password internalsvc/loglist
 (hostd.LogsvcManager.LogInfo) [
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "AgentMgr",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "AnnotationProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "App",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "BaseLibs",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "BlklistsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Cimsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ComputeResource",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DateTimeSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DebugBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DebugManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DictionaryOptionsProvider(Config.Defaults.)",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DictionaryOptionsProvider(Config.GlobalSettings.)",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DirectorysvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "EnvironmentBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "EnvironmentBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "FSVolumeProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "FirmwareSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Fixed Datacenter",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HTTP server /folder",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HTTP server /host",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HTTP server /tmp",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HTTP server /usr/lib/vmware/hostd/docroot/",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HaUserManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HealthStatusSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Host agent service",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::AutoStartManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::Datastore",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::Datastore",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::DatastoreSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::HostEventProcessor",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::PatchManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HostsvcDebugManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HostsvcManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HostsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HttpSvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "InternalServiceInstance",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "InternalsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "KernelModuleSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "KernelOptionsProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "LLPM",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Locale",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Memory checker",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "NetworkProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Nfc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Partitionsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PerfCounter::Registry",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PerfCounterManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PerfCounterRegistry",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Poller",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PropertyCollector",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PropertyJournal",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PropertyProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Proxysvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Proxysvc Req00002",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Proxysvc Req00260",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "RDMManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ResourcePool ha-root-pool",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SOAP",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SOAP",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SOAP",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ScratchOptionProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ScreenHandler",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SearchIndex",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ServiceSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Snmpsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SoapAdapter",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Solo",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Statssvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "StorageSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SupportsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SyslogConfigProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "TaskManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ThreadPool",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "UserDirectory",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VMotion",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VMotionJournal",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VMotionSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VcsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VdisksvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VersionValidator",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vimsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmMisc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmWwn",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vmacore::Tester",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmdbAdapter",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmdbSvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vmfs2UpgradeModeLock",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmkEventSource",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vmomi",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vmsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "WelcomePageCustomizer",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ha-eventmgr",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ha-folder-vm",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ha-host",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ha-license-manager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "session pool",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "vm:/vmfs/volumes/15b85cb7-227e3434-7b44-0104c3c0a336/Trustix/Trustix.vmx",
      logLevel = "info",
   }
 ]


[[Category: Vimsh]]</text>
    <sha1>35c8c2681f336f3ef28630676658b6bb2355afcf</sha1>
  </revision>
  <revision>
    <id>504</id>
    <parentid>503</parentid>
    <timestamp>2008-12-28T21:45:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13583" xml:space="preserve">==== vimsh internalsvc/loglist ====
Usage: loglist [prefix]

Get the list of loggers that can be configured

==== example output ====
Here is an example of the output on a pristine ESX3.5i setup that has only one VM called trustix.

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password internalsvc/loglist
 (hostd.LogsvcManager.LogInfo) [
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "AgentMgr",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "AnnotationProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "App",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "BaseLibs",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "BlklistsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Cimsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ComputeResource",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DatastoreBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DateTimeSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DebugBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DebugManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DictionaryOptionsProvider(Config.Defaults.)",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DictionaryOptionsProvider(Config.GlobalSettings.)",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "DirectorysvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "EnvironmentBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "EnvironmentBrowser",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "FSVolumeProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "FirmwareSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Fixed Datacenter",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HTTP server /folder",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HTTP server /host",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HTTP server /tmp",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HTTP server /usr/lib/vmware/hostd/docroot/",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HaUserManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HealthStatusSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Host agent service",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::AutoStartManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::Datastore",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::Datastore",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::DatastoreSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::HostEventProcessor",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Hostsvc::PatchManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HostsvcDebugManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HostsvcManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HostsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "HttpSvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "InternalServiceInstance",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "InternalsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "KernelModuleSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "KernelOptionsProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "LLPM",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Locale",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Memory checker",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "NetworkProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Nfc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Partitionsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PerfCounter::Registry",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PerfCounterManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PerfCounterRegistry",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Poller",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PropertyCollector",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PropertyJournal",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "PropertyProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Proxysvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Proxysvc Req00002",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Proxysvc Req00260",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "RDMManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ResourcePool ha-root-pool",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SOAP",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SOAP",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SOAP",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ScratchOptionProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ScreenHandler",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SearchIndex",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ServiceSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Snmpsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SoapAdapter",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Solo",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Statssvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "StorageSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SupportsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "SyslogConfigProvider",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "TaskManager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ThreadPool",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "UserDirectory",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VMotion",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VMotionJournal",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VMotionSystem",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VcsvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VdisksvcPlugin",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VersionValidator",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vimsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmMisc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmWwn",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vmacore::Tester",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmdbAdapter",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmdbSvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vmfs2UpgradeModeLock",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "VmkEventSource",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vmomi",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "Vmsvc",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "WelcomePageCustomizer",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ha-eventmgr",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ha-folder-vm",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ha-host",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "ha-license-manager",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "session pool",
      logLevel = "info",
   },
   (hostd.LogsvcManager.LogInfo) {
      dynamicType = &lt;unset&gt;,
      name = "vm:/vmfs/volumes/15b85cb7-227e3434-7b44-0104c3c0a336/Trustix/Trustix.vmx",
      logLevel = "info",
   }
 ]


[[Category: Vimsh]]</text>
    <sha1>21619fd3d691744587dde175ecff5b60735aad3d</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsvc/auth/roles</title>
  <ns>0</ns>
  <id>242</id>
  <revision>
    <id>505</id>
    <parentid>454</parentid>
    <timestamp>2008-12-28T21:50:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7567" xml:space="preserve">==== vimsh vimsvc/auth/roles ====
Usage: roles

Get the list of currently defined roles.

==== example output ====
Here's example output of a pristine ESX3.5i host with no additional roles defined or customized.
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/roles
 (vim.AuthorizationManager.Role) [
   (vim.AuthorizationManager.Role) {
      dynamicType = &lt;unset&gt;,
      roleId = -5,
      system = true,
      name = "NoAccess",
      info = (vim.Description) {
         dynamicType = &lt;unset&gt;,
         label = "No Access",
         summary = "Used for restricting granted access",
      },
   },
   (vim.AuthorizationManager.Role) {
      dynamicType = &lt;unset&gt;,
      roleId = -4,
      system = true,
      name = "Anonymous",
      info = (vim.Description) {
         dynamicType = &lt;unset&gt;,
         label = "Anonymous",
         summary = "Not logged-in user (cannot be granted)",
      },
      privilege = (string) [
         "System.Anonymous"
      ],
   },
   (vim.AuthorizationManager.Role) {
      dynamicType = &lt;unset&gt;,
      roleId = -3,
      system = true,
      name = "View",
      info = (vim.Description) {
         dynamicType = &lt;unset&gt;,
         label = "View",
         summary = "Visibility access (cannot be granted)",
      },
      privilege = (string) [
         "System.Anonymous",
         "System.View"
      ],
   },
   (vim.AuthorizationManager.Role) {
      dynamicType = &lt;unset&gt;,
      roleId = -2,
      system = true,
      name = "ReadOnly",
      info = (vim.Description) {
         dynamicType = &lt;unset&gt;,
         label = "Read-Only",
         summary = "See details of objects, but not make changes",
      },
      privilege = (string) [
         "System.Anonymous",
         "System.Read",
         "System.View"
      ],
   },
   (vim.AuthorizationManager.Role) {
      dynamicType = &lt;unset&gt;,
      roleId = -1,
      system = true,
      name = "Admin",
      info = (vim.Description) {
         dynamicType = &lt;unset&gt;,
         label = "Administrator",
         summary = "Full access rights",
      },
      privilege = (string) [
         "Alarm.Create",
         "Alarm.Delete",
         "Alarm.Edit",
         "Authorization.ModifyPermissions",
         "Authorization.ModifyRoles",
         "Authorization.ReassignRolePermissions",
         "Datacenter.Create",
         "Datacenter.Delete",
         "Datacenter.Move",
         "Datacenter.Rename",
         "Datastore.Browse",
         "Datastore.Delete",
         "Datastore.DeleteFile",
         "Datastore.FileManagement",
         "Datastore.Rename",
         "Extension.Register",
         "Extension.Unregister",
         "Extension.Update",
         "Folder.Create",
         "Folder.Delete",
         "Folder.Move",
         "Folder.Rename",
         "Global.CancelTask",
         "Global.CapacityPlanning",
         "Global.Diagnostics",
         "Global.DisableMethods",
         "Global.EnableMethods",
         "Global.Licenses",
         "Global.LogEvent",
         "Global.ManageCustomFields",
         "Global.Proxy",
         "Global.ScriptAction",
         "Global.ServiceManagers",
         "Global.SetCustomField",
         "Global.Settings",
         "Global.VCServer",
         "Host.Cim.CimInteraction",
         "Host.Config.AdvancedConfig",
         "Host.Config.AutoStart",
         "Host.Config.Connection",
         "Host.Config.DateTime",
         "Host.Config.Firmware",
         "Host.Config.HyperThreading",
         "Host.Config.Maintenance",
         "Host.Config.Memory",
         "Host.Config.NetService",
         "Host.Config.Network",
         "Host.Config.Patch",
         "Host.Config.Resources",
         "Host.Config.Settings",
         "Host.Config.Snmp",
         "Host.Config.Storage",
         "Host.Config.SystemManagement",
         "Host.Inventory.AddHostToCluster",
         "Host.Inventory.AddStandaloneHost",
         "Host.Inventory.CreateCluster",
         "Host.Inventory.DeleteCluster",
         "Host.Inventory.EditCluster",
         "Host.Inventory.MoveCluster",
         "Host.Inventory.MoveHost",
         "Host.Inventory.RemoveHostFromCluster",
         "Host.Inventory.RenameCluster",
         "Host.Local.CreateVM",
         "Host.Local.DeleteVM",
         "Host.Local.InstallAgent",
         "Host.Local.ManageUserGroups",
         "Network.Delete",
         "Performance.ModifyIntervals",
         "Resource.ApplyRecommendation",
         "Resource.AssignVMToPool",
         "Resource.ColdMigrate",
         "Resource.CreatePool",
         "Resource.DeletePool",
         "Resource.EditPool",
         "Resource.HotMigrate",
         "Resource.MovePool",
         "Resource.QueryVMotion",
         "Resource.RenamePool",
         "ScheduledTask.Create",
         "ScheduledTask.Delete",
         "ScheduledTask.Edit",
         "ScheduledTask.Run",
         "Sessions.GlobalMessage",
         "Sessions.ImpersonateUser",
         "Sessions.TerminateSession",
         "Sessions.ValidateSession",
         "System.Anonymous",
         "System.Read",
         "System.View",
         "Task.Create",
         "Task.Update",
         "VirtualMachine.Config.AddExistingDisk",
         "VirtualMachine.Config.AddNewDisk",
         "VirtualMachine.Config.AddRemoveDevice",
         "VirtualMachine.Config.AdvancedConfig",
         "VirtualMachine.Config.CPUCount",
         "VirtualMachine.Config.DiskExtend",
         "VirtualMachine.Config.DiskLease",
         "VirtualMachine.Config.EditDevice",
         "VirtualMachine.Config.HostUSBDevice",
         "VirtualMachine.Config.Memory",
         "VirtualMachine.Config.RawDevice",
         "VirtualMachine.Config.RemoveDisk",
         "VirtualMachine.Config.Rename",
         "VirtualMachine.Config.ResetGuestInfo",
         "VirtualMachine.Config.Resource",
         "VirtualMachine.Config.Settings",
         "VirtualMachine.Config.SwapPlacement",
         "VirtualMachine.Config.UpgradeVirtualHardware",
         "VirtualMachine.Interact.AnswerQuestion",
         "VirtualMachine.Interact.Backup",
         "VirtualMachine.Interact.ConsoleInteract",
         "VirtualMachine.Interact.DefragmentAllDisks",
         "VirtualMachine.Interact.DeviceConnection",
         "VirtualMachine.Interact.PowerOff",
         "VirtualMachine.Interact.PowerOn",
         "VirtualMachine.Interact.Reset",
         "VirtualMachine.Interact.SetCDMedia",
         "VirtualMachine.Interact.SetFloppyMedia",
         "VirtualMachine.Interact.Suspend",
         "VirtualMachine.Interact.ToolsInstall",
         "VirtualMachine.Inventory.Create",
         "VirtualMachine.Inventory.Delete",
         "VirtualMachine.Inventory.Move",
         "VirtualMachine.Provisioning.Clone",
         "VirtualMachine.Provisioning.CloneTemplate",
         "VirtualMachine.Provisioning.CreateTemplateFromVM",
         "VirtualMachine.Provisioning.Customize",
         "VirtualMachine.Provisioning.DeployTemplate",
         "VirtualMachine.Provisioning.DiskRandomAccess",
         "VirtualMachine.Provisioning.DiskRandomRead",
         "VirtualMachine.Provisioning.GetVmFiles",
         "VirtualMachine.Provisioning.MarkAsTemplate",
         "VirtualMachine.Provisioning.MarkAsVM",
         "VirtualMachine.Provisioning.ModifyCustSpecs",
         "VirtualMachine.Provisioning.PutVmFiles",
         "VirtualMachine.Provisioning.ReadCustSpecs",
         "VirtualMachine.State.CreateSnapshot",
         "VirtualMachine.State.RemoveSnapshot",
         "VirtualMachine.State.RenameSnapshot",
         "VirtualMachine.State.RevertToSnapshot"
      ],
   }
 ]


[[Category: Vimsh]]</text>
    <sha1>b78e2afbfe085839ff511fc056e111a1df87b412</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsvc/auth/role permissions</title>
  <ns>0</ns>
  <id>240</id>
  <revision>
    <id>506</id>
    <parentid>452</parentid>
    <timestamp>2008-12-28T22:26:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1140" xml:space="preserve">==== vimsh vimsvc/auth/role_permissions ====
Usage: role_permissions roleName

Gets defined permissions associated with a role.
The roleName is case sensitive.

====example output====
Here's the output of the command when executed against a default setup on an ESX3.5iU3 host.

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/role_permissions Anonymous
 (vim.AuthorizationManager.Permission) []
 
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/role_permissions ReadOnly
 (vim.AuthorizationManager.Permission) []

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/role_permissions Admin
 (vim.AuthorizationManager.Permission) [
    (vim.AuthorizationManager.Permission) {
       dynamicType = &lt;unset&gt;,
       entity = 'vim.Folder:ha-folder-root',
       principal = "dcui",
       group = false,
       roleId = -1,
       propagate = true,
    },
    (vim.AuthorizationManager.Permission) {
       dynamicType = &lt;unset&gt;,
       entity = 'vim.Folder:ha-folder-root',
       principal = "root",
       group = false,
       roleId = -1,
       propagate = true,
    }
 ]


[[Category: Vimsh]]</text>
    <sha1>41390c75eff6f9103f71e1eca4b77884a27fd818</sha1>
  </revision>
  <revision>
    <id>507</id>
    <parentid>506</parentid>
    <timestamp>2008-12-28T22:26:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1141" xml:space="preserve">==== vimsh vimsvc/auth/role_permissions ====
Usage: role_permissions roleName

Gets defined permissions associated with a role.
The roleName is case sensitive.

====example output====
Here's the output of the command when executed against a default setup on an ESX3.5iU3 host.

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/role_permissions Anonymous
 (vim.AuthorizationManager.Permission) []
 
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/role_permissions ReadOnly
 (vim.AuthorizationManager.Permission) []
 
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/role_permissions Admin
 (vim.AuthorizationManager.Permission) [
    (vim.AuthorizationManager.Permission) {
       dynamicType = &lt;unset&gt;,
       entity = 'vim.Folder:ha-folder-root',
       principal = "dcui",
       group = false,
       roleId = -1,
       propagate = true,
    },
    (vim.AuthorizationManager.Permission) {
       dynamicType = &lt;unset&gt;,
       entity = 'vim.Folder:ha-folder-root',
       principal = "root",
       group = false,
       roleId = -1,
       propagate = true,
    }
 ]


[[Category: Vimsh]]</text>
    <sha1>a44c01458fb9c63aec1b76f211a30c52846e5c56</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsvc/auth/privileges</title>
  <ns>0</ns>
  <id>238</id>
  <revision>
    <id>508</id>
    <parentid>450</parentid>
    <timestamp>2008-12-28T22:31:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="30349" xml:space="preserve">==== vimsh vimsvc/auth/privileges ====
Usage: privileges

Get the list of system-defined privileges.

====example output====
Example output against a pristine ESX3.5i host.
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/privileges
 (vim.AuthorizationManager.Privilege) [
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "System.Anonymous",
      onParent = false,
      name = "Anonymous",
      privGroupName = "System",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "System.View",
      onParent = false,
      name = "View",
      privGroupName = "System",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "System.Read",
      onParent = false,
      name = "Read",
      privGroupName = "System",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.ManageCustomFields",
      onParent = false,
      name = "ManageCustomFields",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.SetCustomField",
      onParent = false,
      name = "SetCustomField",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.LogEvent",
      onParent = false,
      name = "LogEvent",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.CancelTask",
      onParent = false,
      name = "CancelTask",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.Licenses",
      onParent = false,
      name = "Licenses",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.Diagnostics",
      onParent = false,
      name = "Diagnostics",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.Settings",
      onParent = false,
      name = "Settings",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.VCServer",
      onParent = false,
      name = "VCServer",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.CapacityPlanning",
      onParent = false,
      name = "CapacityPlanning",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.ScriptAction",
      onParent = false,
      name = "ScriptAction",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.Proxy",
      onParent = false,
      name = "Proxy",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.DisableMethods",
      onParent = false,
      name = "DisableMethods",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.EnableMethods",
      onParent = false,
      name = "EnableMethods",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Global.ServiceManagers",
      onParent = false,
      name = "ServiceManagers",
      privGroupName = "Global",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Folder.Create",
      onParent = false,
      name = "Create",
      privGroupName = "Folder",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Folder.Delete",
      onParent = true,
      name = "Delete",
      privGroupName = "Folder",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Folder.Rename",
      onParent = false,
      name = "Rename",
      privGroupName = "Folder",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Folder.Move",
      onParent = false,
      name = "Move",
      privGroupName = "Folder",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datacenter.Create",
      onParent = false,
      name = "Create",
      privGroupName = "Datacenter",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datacenter.Delete",
      onParent = true,
      name = "Delete",
      privGroupName = "Datacenter",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datacenter.Rename",
      onParent = false,
      name = "Rename",
      privGroupName = "Datacenter",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datacenter.Move",
      onParent = false,
      name = "Move",
      privGroupName = "Datacenter",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datastore.Rename",
      onParent = false,
      name = "Rename",
      privGroupName = "Datastore",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datastore.Delete",
      onParent = false,
      name = "Delete",
      privGroupName = "Datastore",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datastore.Browse",
      onParent = false,
      name = "Browse",
      privGroupName = "Datastore",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datastore.DeleteFile",
      onParent = false,
      name = "DeleteFile",
      privGroupName = "Datastore",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Datastore.FileManagement",
      onParent = false,
      name = "FileManagement",
      privGroupName = "Datastore",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Network.Delete",
      onParent = false,
      name = "Delete",
      privGroupName = "Network",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.AddStandaloneHost",
      onParent = false,
      name = "AddStandaloneHost",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.CreateCluster",
      onParent = false,
      name = "CreateCluster",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.AddHostToCluster",
      onParent = false,
      name = "AddHostToCluster",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.RemoveHostFromCluster",
      onParent = true,
      name = "RemoveHostFromCluster",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.MoveCluster",
      onParent = false,
      name = "MoveCluster",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.RenameCluster",
      onParent = false,
      name = "RenameCluster",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.DeleteCluster",
      onParent = true,
      name = "DeleteCluster",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.EditCluster",
      onParent = false,
      name = "EditCluster",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Inventory.MoveHost",
      onParent = false,
      name = "MoveHost",
      privGroupName = "Host.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.SystemManagement",
      onParent = false,
      name = "SystemManagement",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Connection",
      onParent = false,
      name = "Connection",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Maintenance",
      onParent = false,
      name = "Maintenance",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.AutoStart",
      onParent = false,
      name = "AutoStart",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.HyperThreading",
      onParent = false,
      name = "HyperThreading",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Storage",
      onParent = false,
      name = "Storage",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.NetService",
      onParent = false,
      name = "NetService",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Memory",
      onParent = false,
      name = "Memory",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Network",
      onParent = false,
      name = "Network",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.AdvancedConfig",
      onParent = false,
      name = "AdvancedConfig",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Resources",
      onParent = false,
      name = "Resources",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Snmp",
      onParent = false,
      name = "Snmp",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.DateTime",
      onParent = false,
      name = "DateTime",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Settings",
      onParent = false,
      name = "Settings",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Patch",
      onParent = false,
      name = "Patch",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Config.Firmware",
      onParent = false,
      name = "Firmware",
      privGroupName = "Host.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Local.InstallAgent",
      onParent = false,
      name = "InstallAgent",
      privGroupName = "Host.Local",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Local.ManageUserGroups",
      onParent = false,
      name = "ManageUserGroups",
      privGroupName = "Host.Local",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Local.CreateVM",
      onParent = false,
      name = "CreateVM",
      privGroupName = "Host.Local",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Local.DeleteVM",
      onParent = false,
      name = "DeleteVM",
      privGroupName = "Host.Local",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Host.Cim.CimInteraction",
      onParent = false,
      name = "CimInteraction",
      privGroupName = "Host.Cim",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Inventory.Create",
      onParent = false,
      name = "Create",
      privGroupName = "VirtualMachine.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Inventory.Delete",
      onParent = true,
      name = "Delete",
      privGroupName = "VirtualMachine.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Inventory.Move",
      onParent = false,
      name = "Move",
      privGroupName = "VirtualMachine.Inventory",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.PowerOn",
      onParent = false,
      name = "PowerOn",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.PowerOff",
      onParent = false,
      name = "PowerOff",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.Suspend",
      onParent = false,
      name = "Suspend",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.Reset",
      onParent = false,
      name = "Reset",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.AnswerQuestion",
      onParent = false,
      name = "AnswerQuestion",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.ConsoleInteract",
      onParent = false,
      name = "ConsoleInteract",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.DeviceConnection",
      onParent = false,
      name = "DeviceConnection",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.SetCDMedia",
      onParent = false,
      name = "SetCDMedia",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.SetFloppyMedia",
      onParent = false,
      name = "SetFloppyMedia",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.ToolsInstall",
      onParent = false,
      name = "ToolsInstall",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.DefragmentAllDisks",
      onParent = false,
      name = "DefragmentAllDisks",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Interact.Backup",
      onParent = false,
      name = "Backup",
      privGroupName = "VirtualMachine.Interact",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.Rename",
      onParent = false,
      name = "Rename",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.AddExistingDisk",
      onParent = false,
      name = "AddExistingDisk",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.AddNewDisk",
      onParent = false,
      name = "AddNewDisk",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.RemoveDisk",
      onParent = false,
      name = "RemoveDisk",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.RawDevice",
      onParent = false,
      name = "RawDevice",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.HostUSBDevice",
      onParent = false,
      name = "HostUSBDevice",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.CPUCount",
      onParent = false,
      name = "CPUCount",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.Memory",
      onParent = false,
      name = "Memory",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.AddRemoveDevice",
      onParent = false,
      name = "AddRemoveDevice",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.EditDevice",
      onParent = false,
      name = "EditDevice",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.Settings",
      onParent = false,
      name = "Settings",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.Resource",
      onParent = false,
      name = "Resource",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.UpgradeVirtualHardware",
      onParent = false,
      name = "UpgradeVirtualHardware",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.ResetGuestInfo",
      onParent = false,
      name = "ResetGuestInfo",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.AdvancedConfig",
      onParent = false,
      name = "AdvancedConfig",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.DiskLease",
      onParent = false,
      name = "DiskLease",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.SwapPlacement",
      onParent = false,
      name = "SwapPlacement",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Config.DiskExtend",
      onParent = false,
      name = "DiskExtend",
      privGroupName = "VirtualMachine.Config",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.State.CreateSnapshot",
      onParent = false,
      name = "CreateSnapshot",
      privGroupName = "VirtualMachine.State",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.State.RevertToSnapshot",
      onParent = false,
      name = "RevertToSnapshot",
      privGroupName = "VirtualMachine.State",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.State.RemoveSnapshot",
      onParent = false,
      name = "RemoveSnapshot",
      privGroupName = "VirtualMachine.State",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.State.RenameSnapshot",
      onParent = false,
      name = "RenameSnapshot",
      privGroupName = "VirtualMachine.State",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.Customize",
      onParent = false,
      name = "Customize",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.Clone",
      onParent = false,
      name = "Clone",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.CreateTemplateFromVM",
      onParent = false,
      name = "CreateTemplateFromVM",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.DeployTemplate",
      onParent = false,
      name = "DeployTemplate",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.CloneTemplate",
      onParent = false,
      name = "CloneTemplate",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.MarkAsTemplate",
      onParent = false,
      name = "MarkAsTemplate",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.MarkAsVM",
      onParent = false,
      name = "MarkAsVM",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.ReadCustSpecs",
      onParent = false,
      name = "ReadCustSpecs",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.ModifyCustSpecs",
      onParent = false,
      name = "ModifyCustSpecs",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.DiskRandomAccess",
      onParent = false,
      name = "DiskRandomAccess",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.DiskRandomRead",
      onParent = false,
      name = "DiskRandomRead",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.GetVmFiles",
      onParent = false,
      name = "GetVmFiles",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "VirtualMachine.Provisioning.PutVmFiles",
      onParent = false,
      name = "PutVmFiles",
      privGroupName = "VirtualMachine.Provisioning",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.AssignVMToPool",
      onParent = false,
      name = "AssignVMToPool",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.ApplyRecommendation",
      onParent = false,
      name = "ApplyRecommendation",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.CreatePool",
      onParent = false,
      name = "CreatePool",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.RenamePool",
      onParent = false,
      name = "RenamePool",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.EditPool",
      onParent = true,
      name = "EditPool",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.MovePool",
      onParent = false,
      name = "MovePool",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.DeletePool",
      onParent = true,
      name = "DeletePool",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.HotMigrate",
      onParent = false,
      name = "HotMigrate",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.ColdMigrate",
      onParent = false,
      name = "ColdMigrate",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Resource.QueryVMotion",
      onParent = false,
      name = "QueryVMotion",
      privGroupName = "Resource",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Alarm.Create",
      onParent = false,
      name = "Create",
      privGroupName = "Alarm",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Alarm.Delete",
      onParent = false,
      name = "Delete",
      privGroupName = "Alarm",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Alarm.Edit",
      onParent = false,
      name = "Edit",
      privGroupName = "Alarm",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Task.Create",
      onParent = false,
      name = "Create",
      privGroupName = "Task",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Task.Update",
      onParent = false,
      name = "Update",
      privGroupName = "Task",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "ScheduledTask.Create",
      onParent = false,
      name = "Create",
      privGroupName = "ScheduledTask",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "ScheduledTask.Delete",
      onParent = false,
      name = "Delete",
      privGroupName = "ScheduledTask",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "ScheduledTask.Run",
      onParent = false,
      name = "Run",
      privGroupName = "ScheduledTask",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "ScheduledTask.Edit",
      onParent = false,
      name = "Edit",
      privGroupName = "ScheduledTask",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Sessions.TerminateSession",
      onParent = false,
      name = "TerminateSession",
      privGroupName = "Sessions",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Sessions.ValidateSession",
      onParent = false,
      name = "ValidateSession",
      privGroupName = "Sessions",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Sessions.GlobalMessage",
      onParent = false,
      name = "GlobalMessage",
      privGroupName = "Sessions",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Sessions.ImpersonateUser",
      onParent = false,
      name = "ImpersonateUser",
      privGroupName = "Sessions",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Performance.ModifyIntervals",
      onParent = false,
      name = "ModifyIntervals",
      privGroupName = "Performance",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Authorization.ModifyRoles",
      onParent = false,
      name = "ModifyRoles",
      privGroupName = "Authorization",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Authorization.ReassignRolePermissions",
      onParent = false,
      name = "ReassignRolePermissions",
      privGroupName = "Authorization",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Authorization.ModifyPermissions",
      onParent = true,
      name = "ModifyPermissions",
      privGroupName = "Authorization",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Extension.Register",
      onParent = false,
      name = "Register",
      privGroupName = "Extension",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Extension.Update",
      onParent = false,
      name = "Update",
      privGroupName = "Extension",
   },
   (vim.AuthorizationManager.Privilege) {
      dynamicType = &lt;unset&gt;,
      privId = "Extension.Unregister",
      onParent = false,
      name = "Unregister",
      privGroupName = "Extension",
   }
 ]


[[Category: vimsh]]</text>
    <sha1>a7caaaed13057fc8edf2a4b065c4a78b7498956d</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsvc/auth/permissions</title>
  <ns>0</ns>
  <id>237</id>
  <revision>
    <id>509</id>
    <parentid>449</parentid>
    <timestamp>2008-12-28T22:33:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="821" xml:space="preserve">==== vimsh vimsvc/auth/permissions ====
Usage: permissions

Get all the permissions defined in the system.
This will list all the users and roles defined on your ESX host.

====example output====
Example output against a new ESX3.5i host:
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password vimsvc/auth/permissions
 (vim.AuthorizationManager.Permission) [
    (vim.AuthorizationManager.Permission) {
       dynamicType = &lt;unset&gt;,
       entity = 'vim.Folder:ha-folder-root',
       principal = "dcui",
       group = false,
       roleId = -1,
       propagate = true,
    },
    (vim.AuthorizationManager.Permission) {
       dynamicType = &lt;unset&gt;,
       entity = 'vim.Folder:ha-folder-root',
       principal = "root",
       group = false,
       roleId = -1,
       propagate = true,
    }
 ]


[[Category: vimsh]]</text>
    <sha1>3d5505be045863d5045973fe3647b4889050d1ed</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/perfcount/enumerate</title>
  <ns>0</ns>
  <id>276</id>
  <revision>
    <id>510</id>
    <parentid>501</parentid>
    <timestamp>2008-12-28T22:42:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3100" xml:space="preserve">==== vimsh internalsvc/perfcount/enumerate ====

Usage: enumerate registry_path

Enumerate paths in the registry.

====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password internalsvc/perfcount/enumerate /
 /hostd/  /vmomi/
 # vmware-vim-cmd -H 10.10.10.10 -U root -P MyAuntie internalsvc/perfcount/enumerate /hostd/vmomi/serverAdapter/method/
 /hostd/vmomi/serverAdapter/method/hostd.LogsvcManager.getLoggers/               
 /hostd/vmomi/serverAdapter/method/hostd.perfCounter.Registry.enumeratePath/     
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.GetPrivilegeList/    
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.GetRoleList/         
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.retrieveAllPermissions/
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.retrieveRolePermissions/
 /hostd/vmomi/serverAdapter/method/vim.Folder.registerVm/                        
 /hostd/vmomi/serverAdapter/method/vim.HistoryCollector.remove/                  
 /hostd/vmomi/serverAdapter/method/vim.HistoryCollector.setLatestPageSize/       
 /hostd/vmomi/serverAdapter/method/vim.LicenseManager.queryUsage/                
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.currentTime/              
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.retrieveContent/          
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.retrieveInternalContent/  
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.acquireLocalTicket/        
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.login/                     
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.logout/                    
 /hostd/vmomi/serverAdapter/method/vim.VirtualMachine.acquireMksTicket/          
 /hostd/vmomi/serverAdapter/method/vim.VirtualMachine.powerOn/                   
 /hostd/vmomi/serverAdapter/method/vim.event.EventHistoryCollector.readNext/     
 /hostd/vmomi/serverAdapter/method/vim.event.EventManager.createCollector/       
 /hostd/vmomi/serverAdapter/method/vim.event.EventManager.logUserEvent/          
 /hostd/vmomi/serverAdapter/method/vim.host.DatastoreBrowser.search/             
 /hostd/vmomi/serverAdapter/method/vim.view.InventoryView.openFolder/            
 /hostd/vmomi/serverAdapter/method/vim.view.ListView.modify/                     
 /hostd/vmomi/serverAdapter/method/vim.view.ListView.reset/                      
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createContainerView/     
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createInventoryView/     
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createListViewFromView/  
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.Filter.destroy/ 
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.cancelWaitForUpdates/
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.createFilter/   
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.retrieveContents/
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.waitForUpdates/ 

[[Category: Vimsh]]</text>
    <sha1>2d86f9aa6911deed86f1484079df10c89febfbc5</sha1>
  </revision>
  <revision>
    <id>511</id>
    <parentid>510</parentid>
    <timestamp>2008-12-28T22:45:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Undo revision 510 by [[Special:Contributions/Wila|Wila]] ([[User talk:Wila|Talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== vimsh internalsvc/perfcount/enumerate ====

Usage: enumerate registry_path

Enumerate paths in the registry.

[[Category: Vimsh]]</text>
    <sha1>8f0569681339417b863b05b792ede3f4e1cf3d4d</sha1>
  </revision>
  <revision>
    <id>512</id>
    <parentid>511</parentid>
    <timestamp>2008-12-28T22:47:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3099" xml:space="preserve">==== vimsh internalsvc/perfcount/enumerate ====

Usage: enumerate registry_path

Enumerate paths in the registry.
====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password internalsvc/perfcount/enumerate /
 /hostd/  /vmomi/
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password internalsvc/perfcount/enumerate /hostd/vmomi/serverAdapter/method/
 /hostd/vmomi/serverAdapter/method/hostd.LogsvcManager.getLoggers/               
 /hostd/vmomi/serverAdapter/method/hostd.perfCounter.Registry.enumeratePath/     
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.GetPrivilegeList/    
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.GetRoleList/         
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.retrieveAllPermissions/
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.retrieveRolePermissions/
 /hostd/vmomi/serverAdapter/method/vim.Folder.registerVm/                        
 /hostd/vmomi/serverAdapter/method/vim.HistoryCollector.remove/                  
 /hostd/vmomi/serverAdapter/method/vim.HistoryCollector.setLatestPageSize/       
 /hostd/vmomi/serverAdapter/method/vim.LicenseManager.queryUsage/                
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.currentTime/              
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.retrieveContent/          
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.retrieveInternalContent/  
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.acquireLocalTicket/        
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.login/                     
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.logout/                    
 /hostd/vmomi/serverAdapter/method/vim.VirtualMachine.acquireMksTicket/          
 /hostd/vmomi/serverAdapter/method/vim.VirtualMachine.powerOn/                   
 /hostd/vmomi/serverAdapter/method/vim.event.EventHistoryCollector.readNext/     
 /hostd/vmomi/serverAdapter/method/vim.event.EventManager.createCollector/       
 /hostd/vmomi/serverAdapter/method/vim.event.EventManager.logUserEvent/          
 /hostd/vmomi/serverAdapter/method/vim.host.DatastoreBrowser.search/             
 /hostd/vmomi/serverAdapter/method/vim.view.InventoryView.openFolder/            
 /hostd/vmomi/serverAdapter/method/vim.view.ListView.modify/                     
 /hostd/vmomi/serverAdapter/method/vim.view.ListView.reset/                      
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createContainerView/     
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createInventoryView/     
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createListViewFromView/  
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.Filter.destroy/ 
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.cancelWaitForUpdates/
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.createFilter/   
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.retrieveContents/
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.waitForUpdates/ 

[[Category: Vimsh]]</text>
    <sha1>771efcc51d28d687624b8e3df0ade7dbbd7cdb9d</sha1>
  </revision>
  <revision>
    <id>513</id>
    <parentid>512</parentid>
    <timestamp>2008-12-28T22:47:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3101" xml:space="preserve">==== vimsh internalsvc/perfcount/enumerate ====

Usage: enumerate registry_path

Enumerate paths in the registry.
====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password internalsvc/perfcount/enumerate /
 /hostd/  /vmomi/
 
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password internalsvc/perfcount/enumerate /hostd/vmomi/serverAdapter/method/
 /hostd/vmomi/serverAdapter/method/hostd.LogsvcManager.getLoggers/               
 /hostd/vmomi/serverAdapter/method/hostd.perfCounter.Registry.enumeratePath/     
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.GetPrivilegeList/    
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.GetRoleList/         
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.retrieveAllPermissions/
 /hostd/vmomi/serverAdapter/method/vim.AuthorizationManager.retrieveRolePermissions/
 /hostd/vmomi/serverAdapter/method/vim.Folder.registerVm/                        
 /hostd/vmomi/serverAdapter/method/vim.HistoryCollector.remove/                  
 /hostd/vmomi/serverAdapter/method/vim.HistoryCollector.setLatestPageSize/       
 /hostd/vmomi/serverAdapter/method/vim.LicenseManager.queryUsage/                
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.currentTime/              
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.retrieveContent/          
 /hostd/vmomi/serverAdapter/method/vim.ServiceInstance.retrieveInternalContent/  
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.acquireLocalTicket/        
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.login/                     
 /hostd/vmomi/serverAdapter/method/vim.SessionManager.logout/                    
 /hostd/vmomi/serverAdapter/method/vim.VirtualMachine.acquireMksTicket/          
 /hostd/vmomi/serverAdapter/method/vim.VirtualMachine.powerOn/                   
 /hostd/vmomi/serverAdapter/method/vim.event.EventHistoryCollector.readNext/     
 /hostd/vmomi/serverAdapter/method/vim.event.EventManager.createCollector/       
 /hostd/vmomi/serverAdapter/method/vim.event.EventManager.logUserEvent/          
 /hostd/vmomi/serverAdapter/method/vim.host.DatastoreBrowser.search/             
 /hostd/vmomi/serverAdapter/method/vim.view.InventoryView.openFolder/            
 /hostd/vmomi/serverAdapter/method/vim.view.ListView.modify/                     
 /hostd/vmomi/serverAdapter/method/vim.view.ListView.reset/                      
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createContainerView/     
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createInventoryView/     
 /hostd/vmomi/serverAdapter/method/vim.view.ViewManager.createListViewFromView/  
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.Filter.destroy/ 
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.cancelWaitForUpdates/
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.createFilter/   
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.retrieveContents/
 /hostd/vmomi/serverAdapter/method/vmodl.query.PropertyCollector.waitForUpdates/ 

[[Category: Vimsh]]</text>
    <sha1>286faba4109c255674c771595733fcb47a9cecc8</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/perfcount/query destroy</title>
  <ns>0</ns>
  <id>277</id>
  <revision>
    <id>514</id>
    <timestamp>2008-12-29T04:19:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/perfcount/query_destroy ==== Usage: query_destroy query_id  Destroy created query.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">==== vimsh internalsvc/perfcount/query_destroy ====
Usage: query_destroy query_id

Destroy created query.

[[Category: Vimsh]]</text>
    <sha1>30ae691696471a838e97ff14da14a399fc33fbd3</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/perfcount/query execute</title>
  <ns>0</ns>
  <id>278</id>
  <revision>
    <id>515</id>
    <timestamp>2008-12-29T04:21:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== internalsvc/perfcount/query_execute ==== Usage: query_execute [OPTIONS] query_id  Execute created query.   Options:     --vmomi-output         Display output in verbose VMOMI mode.  f...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="497" xml:space="preserve">==== internalsvc/perfcount/query_execute ====
Usage: query_execute [OPTIONS] query_id

Execute created query.

 Options:
    --vmomi-output
        Display output in verbose VMOMI mode.  false by default.
 No other display modifiers can be used with this option.
 
    --sort-by-name
        Sort results by name.  false by default.
 
    --sort-by-value
        Sort results by value.  false by default.
 
    --name-range=int
        Show only a range of bytes for the name.

[[Category: Vimsh]]</text>
    <sha1>00b8704abe894e0e6095db00381e327df7ed8f5d</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/perfcount/query info</title>
  <ns>0</ns>
  <id>279</id>
  <revision>
    <id>516</id>
    <timestamp>2008-12-29T04:23:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/perfcount/query_info ==== Usage: query_info query_id  Get information about the performance counter query.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="150" xml:space="preserve">==== vimsh internalsvc/perfcount/query_info ====
Usage: query_info query_id

Get information about the performance counter query.

[[Category: Vimsh]]</text>
    <sha1>22f85ca98d4ae61163779a132c5a48b5e2ddc96a</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/perfcount/query list</title>
  <ns>0</ns>
  <id>280</id>
  <revision>
    <id>517</id>
    <timestamp>2008-12-29T04:25:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/perfcount/query_list ==== Usage: query_list  List the queries that are associated with the performance counter registry  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">==== vimsh internalsvc/perfcount/query_list ====
Usage: query_list

List the queries that are associated with the performance counter registry

[[Category: Vimsh]]</text>
    <sha1>6390135e5d75c897c00eef4247dfce246aa55576</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/perfcount/query names</title>
  <ns>0</ns>
  <id>281</id>
  <revision>
    <id>518</id>
    <timestamp>2008-12-29T04:28:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== internalsvc/perfcount/query_names ==== Usage: query_names [OPTIONS] [counter0] [counter1] [counter2] [counter3] [counter5] [counter6] [counter7] [counter8] [counter9]  Query performan...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="884" xml:space="preserve">==== internalsvc/perfcount/query_names ====
Usage: query_names [OPTIONS] [counter0] [counter1] [counter2] [counter3] [counter5] [counter6] [counter7] [counter8] [counter9]

Query performance counter values by creating and executing a names query.  Query will automatically be destroyed unless create-only flag is specified.  Use query_execute on query object to access results on created query.

 Options:
    --create-only
        Only create the query.  Do not execute or destroy.  false by default. 
 
    --vmomi-output
        Display output in verbose VMOMI mode.  false by default. 
 No other display modifiers can be used with this option.
 
    --sort-by-name
        Sort results by name.  false by default. 
 
    --sort-by-value
        Sort results by value.  false by default. 
 
    --name-range=int
        Show only a range of bytes for the name.

[[Category: Vimsh]]</text>
    <sha1>bd239c2344f232da997fc92511abbcfe187f488f</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/perfcount/query regex</title>
  <ns>0</ns>
  <id>282</id>
  <revision>
    <id>519</id>
    <timestamp>2008-12-29T04:29:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/perfcount/query_regex ==== Usage: query_regex [OPTIONS] regex [case_sensitive]  Query performance counter values by creating and executing a regex query.  Query will...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="814" xml:space="preserve">==== vimsh internalsvc/perfcount/query_regex ====
Usage: query_regex [OPTIONS] regex [case_sensitive]

Query performance counter values by creating and executing a regex query.  Query will automatically be destroyed unless create-only flag is specified.  Use query_execute on query object to access results on created query.

 Options:
    --create-only
        Only create the query.  Do not execute or destroy.  false by default. 
 
    --vmomi-output
        Display output in verbose VMOMI mode.  false by default. 
 No other display modifiers can be used with this option.
 
    --sort-by-name
        Sort results by name.  false by default. 
 
    --sort-by-value
        Sort results by value.  false by default. 
 
    --name-range=int
        Show only a range of bytes for the name.

[[Category: Vimsh]]</text>
    <sha1>83c2cb163bcfac1696d6c7ef49c547f890b10610</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Internalsvc/perfcount/scoreboard</title>
  <ns>0</ns>
  <id>283</id>
  <revision>
    <id>520</id>
    <timestamp>2008-12-29T04:30:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh internalsvc/perfcount/scoreboard ==== Usage: Get the serialized object scoreboard.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="114" xml:space="preserve">==== vimsh internalsvc/perfcount/scoreboard ====
Usage: Get the serialized object scoreboard.

[[Category: Vimsh]]</text>
    <sha1>64025f61db87b789b46a5960567871d4a406d5b1</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/cpuinfo</title>
  <ns>0</ns>
  <id>76</id>
  <revision>
    <id>521</id>
    <parentid>207</parentid>
    <timestamp>2008-12-29T04:33:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="470" xml:space="preserve">==== vimsh hostsvc/cpuinfo ====

Usage: cpuinfo [hyperthreadCfg]

Get the CPU information.  If hyperthreadCfg is specified, sets configuration
for hyperthreading.  

Valid values include 'true' and 'false'.

====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/cpuinfo
 (vim.host.CpuSchedulerSystem.HyperThreadScheduleInfo) {
    dynamicType = &lt;unset&gt;,
    available = false,
    active = false,
    config = true,
 }


[[Category: vimsh]]</text>
    <sha1>58fb8cf2659159128d01e50504c8b9b6937d3793</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/runtimeinfo</title>
  <ns>0</ns>
  <id>92</id>
  <revision>
    <id>522</id>
    <parentid>238</parentid>
    <timestamp>2008-12-29T04:38:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3966" xml:space="preserve">==== Vimsh hostsvc/runtimeinfo====
Usage: runtimeinfo

Retrieves the host runtime information.

====example output===
Example output when accessing an ESX3.5i host:
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/runtimeinfo
 (vim.host.RuntimeInfo) {
   dynamicType = &lt;unset&gt;,
   connectionState = "connected",
   powerState = "poweredOn",
   inMaintenanceMode = false,
   bootTime = "2008-11-24T23:10:41.665567Z",
   healthSystemRuntime = (vim.host.HealthStatusSystem.Runtime) {
      dynamicType = &lt;unset&gt;,
      systemHealthInfo = (vim.host.SystemHealthInfo) {
         dynamicType = &lt;unset&gt;,
         numericSensorInfo = (vim.host.NumericSensorInfo) [
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "VMware Rollup Health State",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "system",
            },
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "Phoenix Technologies LTD System BIOS 6.00 2008-07-29 00:00:00.000",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "Software Components",
            },
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "VMware Inc. Hypervisor VMware ESX Server 3i 3.5.0 build-123629 2008-10-15 21:03:57.000",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "Software Components",
            }
         ],
      },
      hardwareStatusInfo = (vim.host.HardwareStatusInfo) {
         dynamicType = &lt;unset&gt;,
         memoryStatusInfo = (vim.host.HardwareStatusInfo.HardwareElementInfo) [
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "Memory",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            }
         ],
         cpuStatusInfo = (vim.host.HardwareStatusInfo.HardwareElementInfo) [
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "CPU socket #0",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            },
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "CPU socket #1",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            }
         ],
      },
   },
 }


[[Category: Vimsh]]</text>
    <sha1>896b47a86b9a70682b1d29b0172c7eedeeac7497</sha1>
  </revision>
  <revision>
    <id>523</id>
    <parentid>522</parentid>
    <timestamp>2008-12-29T04:38:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3967" xml:space="preserve">==== Vimsh hostsvc/runtimeinfo====
Usage: runtimeinfo

Retrieves the host runtime information.

====example output====
Example output when accessing an ESX3.5i host:
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/runtimeinfo
 (vim.host.RuntimeInfo) {
   dynamicType = &lt;unset&gt;,
   connectionState = "connected",
   powerState = "poweredOn",
   inMaintenanceMode = false,
   bootTime = "2008-11-24T23:10:41.665567Z",
   healthSystemRuntime = (vim.host.HealthStatusSystem.Runtime) {
      dynamicType = &lt;unset&gt;,
      systemHealthInfo = (vim.host.SystemHealthInfo) {
         dynamicType = &lt;unset&gt;,
         numericSensorInfo = (vim.host.NumericSensorInfo) [
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "VMware Rollup Health State",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "system",
            },
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "Phoenix Technologies LTD System BIOS 6.00 2008-07-29 00:00:00.000",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "Software Components",
            },
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "VMware Inc. Hypervisor VMware ESX Server 3i 3.5.0 build-123629 2008-10-15 21:03:57.000",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "Software Components",
            }
         ],
      },
      hardwareStatusInfo = (vim.host.HardwareStatusInfo) {
         dynamicType = &lt;unset&gt;,
         memoryStatusInfo = (vim.host.HardwareStatusInfo.HardwareElementInfo) [
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "Memory",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            }
         ],
         cpuStatusInfo = (vim.host.HardwareStatusInfo.HardwareElementInfo) [
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "CPU socket #0",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            },
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "CPU socket #1",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            }
         ],
      },
   },
 }


[[Category: Vimsh]]</text>
    <sha1>2de7531b6d221e18c8977995da78a9867547574c</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/hosthardware</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>524</id>
    <parentid>224</parentid>
    <timestamp>2008-12-29T04:48:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23938" xml:space="preserve">==== Vimsh Hostsvc/hosthardware ====
Usage: hosthardware

Retrieves the host hardware information.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/hosthardware
(vim.host.HardwareInfo) {
   dynamicType = &lt;unset&gt;,
   systemInfo = (vim.host.SystemInfo) {
      dynamicType = &lt;unset&gt;,
      vendor = "VMware, Inc.",
      model = "VMware Virtual Platform",
      uuid = "238ef3e5-a923-b48c-5ab7-0d820b1cbde7",
      otherIdentifyingInfo = (vim.host.SystemIdentificationInfo) [
         (vim.host.SystemIdentificationInfo) {
            dynamicType = &lt;unset&gt;,
            identifierValue = " No Asset Tag",
            identifierType = (vim.ElementDescription) {
               dynamicType = &lt;unset&gt;,
               label = "AssetTag",
               summary = "AssetTag",
               key = "AssetTag",
            },
         }
      ],
   },
   cpuInfo = (vim.host.CpuInfo) {
      dynamicType = &lt;unset&gt;,
      numCpuPackages = 2,
      numCpuCores = 2,
      numCpuThreads = 2,
      hz = 2407469482,
   },
   cpuPkg = (vim.host.CpuPackage) [
      (vim.host.CpuPackage) {
         dynamicType = &lt;unset&gt;,
         index = 0,
         vendor = "intel",
         hz = 2407469482,
         busHz = 65958068,
         description = "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz",
         threadId = (short) [
            0
         ],
         cpuFeature = (vim.host.CpuIdInfo) [
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 0,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:1010",
               ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
               ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
               edx = "0100:1001:0110:0101:0110:1110:0110:1001",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 1,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0110:1111:1011",
               ebx = "0000:0000:0000:0001:0000:1000:0000:0000",
               ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
               edx = "0000:1111:1110:1011:1111:1011:1111:1111",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483648,
               vendor = &lt;unset&gt;,
               eax = "1000:0000:0000:0000:0000:0000:0000:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483647,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:0000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
               edx = "0010:0000:0001:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483640,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0011:0000:0010:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            }
         ],
      },
      (vim.host.CpuPackage) {
         dynamicType = &lt;unset&gt;,
         index = 1,
         vendor = "intel",
         hz = 2407469482,
         busHz = 65958068,
         description = "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz",
         threadId = (short) [
            1
         ],
         cpuFeature = (vim.host.CpuIdInfo) [
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 0,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:1010",
               ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
               ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
               edx = "0100:1001:0110:0101:0110:1110:0110:1001",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 1,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0110:1111:1011",
               ebx = "0000:0010:0000:0001:0000:1000:0000:0000",
               ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
               edx = "0000:1111:1110:1011:1111:1011:1111:1111",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483648,
               vendor = &lt;unset&gt;,
               eax = "1000:0000:0000:0000:0000:0000:0000:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483647,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:0000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
               edx = "0010:0000:0001:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483640,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0011:0000:0010:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            }
         ],
      }
   ],
   memorySize = 1771626496,
   numaInfo = (vim.host.NumaInfo) {
      dynamicType = &lt;unset&gt;,
      type = "Fake Numa",
      numNodes = 1,
      numaNode = (vim.host.NumaNode) [
         (vim.host.NumaNode) {
            dynamicType = &lt;unset&gt;,
            typeId = 0,
            cpuID = (short) [
               1,
               0
            ],
            memoryRangeBegin = 0,
            memoryRangeLength = 1879048192,
         }
      ],
   },
   pciDevice = (vim.host.PciDevice) [
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:00.0",
         classId = 1536,
         bus = 0,
         slot = 0,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 29072,
         subDeviceId = 6518,
         deviceName = "440BX/ZX/DX - 82443BX/ZX/DX Host bridge",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:01.0",
         classId = 1540,
         bus = 0,
         slot = 1,
         function = 0,
         vendorId = -32634,
         subVendorId = 0,
         vendorName = "Intel Corporation",
         deviceId = 29073,
         subDeviceId = 0,
         deviceName = "440BX/ZX/DX - 82443BX/ZX/DX AGP bridge",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.0",
         classId = 1537,
         bus = 0,
         slot = 7,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28944,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 ISA",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.1",
         classId = 257,
         bus = 0,
         slot = 7,
         function = 1,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28945,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 IDE",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.3",
         classId = 1664,
         bus = 0,
         slot = 7,
         function = 3,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28947,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 ACPI",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.7",
         classId = 2176,
         bus = 0,
         slot = 7,
         function = 7,
         vendorId = 5549,
         subVendorId = 5549,
         vendorName = "VMWare Inc",
         deviceId = 1856,
         subDeviceId = 1856,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:0f.0",
         classId = 768,
         bus = 0,
         slot = 15,
         function = 0,
         vendorId = 5549,
         subVendorId = 5549,
         vendorName = "VMWare Inc",
         deviceId = 1029,
         subDeviceId = 1029,
         deviceName = "Virtual SVGA",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:10.0",
         classId = 256,
         bus = 0,
         slot = 16,
         function = 0,
         vendorId = 4096,
         subVendorId = 5549,
         vendorName = "LSI Logic / Symbios Logic",
         deviceId = 48,
         subDeviceId = 6518,
         deviceName = "53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:11.0",
         classId = 1540,
         bus = 0,
         slot = 17,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1936,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.0",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.1",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.2",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.3",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.4",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.5",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.6",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.7",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.0",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.1",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.2",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.3",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.4",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.5",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.6",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.7",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.0",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.1",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.2",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.3",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.4",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.5",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.6",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.7",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.0",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.1",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.2",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.3",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.4",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.5",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.6",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.7",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "02:00.0",
         classId = 512,
         bus = 2,
         slot = 0,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 4111,
         subDeviceId = 1872,
         deviceName = "82545EM Gigabit Ethernet Controller (Copper)",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "02:01.0",
         classId = 512,
         bus = 2,
         slot = 1,
         function = 0,
         vendorId = 4130,
         subVendorId = 4130,
         vendorName = "Advanced Micro Devices [AMD]",
         deviceId = 8192,
         subDeviceId = 8192,
         deviceName = "NetFinity 10/100 Fast Ethernet",
      }
   ],
   cpuFeature = (vim.host.CpuIdInfo) [
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = 0,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0000:0000:1010",
         ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
         ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
         edx = "0100:1001:0110:0101:0110:1110:0110:1001",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = 1,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0110:1111:1011",
         ebx = "0000:0000:0000:0001:0000:1000:0000:0000",
         ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
         edx = "0000:1111:1110:1011:1111:1011:1111:1111",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483648,
         vendor = &lt;unset&gt;,
         eax = "1000:0000:0000:0000:0000:0000:0000:1000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
         edx = "0000:0000:0000:0000:0000:0000:0000:0000",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483647,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0000:0000:0000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
         edx = "0000:0000:0001:0000:0000:0000:0000:0000",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483640,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0011:0000:0010:1000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
         edx = "0000:0000:0000:0000:0000:0000:0000:0000",
      }
   ],
   biosInfo = (vim.host.BIOSInfo) {
      dynamicType = &lt;unset&gt;,
      biosVersion = "6.00",
      releaseDate = "2008-07-29T00:00:00Z",
   },
 }

[[Category: Vimsh]]</text>
    <sha1>1ee4818c102d3270a0699295ea4097da05309ac0</sha1>
  </revision>
  <revision>
    <id>525</id>
    <parentid>524</parentid>
    <timestamp>2008-12-29T04:49:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23939" xml:space="preserve">==== Vimsh Hostsvc/hosthardware ====
Usage: hosthardware

Retrieves the host hardware information.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/hosthardware
 (vim.host.HardwareInfo) {
   dynamicType = &lt;unset&gt;,
   systemInfo = (vim.host.SystemInfo) {
      dynamicType = &lt;unset&gt;,
      vendor = "VMware, Inc.",
      model = "VMware Virtual Platform",
      uuid = "238ef3e5-a923-b48c-5ab7-0d820b1cbde7",
      otherIdentifyingInfo = (vim.host.SystemIdentificationInfo) [
         (vim.host.SystemIdentificationInfo) {
            dynamicType = &lt;unset&gt;,
            identifierValue = " No Asset Tag",
            identifierType = (vim.ElementDescription) {
               dynamicType = &lt;unset&gt;,
               label = "AssetTag",
               summary = "AssetTag",
               key = "AssetTag",
            },
         }
      ],
   },
   cpuInfo = (vim.host.CpuInfo) {
      dynamicType = &lt;unset&gt;,
      numCpuPackages = 2,
      numCpuCores = 2,
      numCpuThreads = 2,
      hz = 2407469482,
   },
   cpuPkg = (vim.host.CpuPackage) [
      (vim.host.CpuPackage) {
         dynamicType = &lt;unset&gt;,
         index = 0,
         vendor = "intel",
         hz = 2407469482,
         busHz = 65958068,
         description = "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz",
         threadId = (short) [
            0
         ],
         cpuFeature = (vim.host.CpuIdInfo) [
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 0,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:1010",
               ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
               ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
               edx = "0100:1001:0110:0101:0110:1110:0110:1001",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 1,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0110:1111:1011",
               ebx = "0000:0000:0000:0001:0000:1000:0000:0000",
               ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
               edx = "0000:1111:1110:1011:1111:1011:1111:1111",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483648,
               vendor = &lt;unset&gt;,
               eax = "1000:0000:0000:0000:0000:0000:0000:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483647,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:0000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
               edx = "0010:0000:0001:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483640,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0011:0000:0010:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            }
         ],
      },
      (vim.host.CpuPackage) {
         dynamicType = &lt;unset&gt;,
         index = 1,
         vendor = "intel",
         hz = 2407469482,
         busHz = 65958068,
         description = "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz",
         threadId = (short) [
            1
         ],
         cpuFeature = (vim.host.CpuIdInfo) [
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 0,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:1010",
               ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
               ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
               edx = "0100:1001:0110:0101:0110:1110:0110:1001",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 1,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0110:1111:1011",
               ebx = "0000:0010:0000:0001:0000:1000:0000:0000",
               ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
               edx = "0000:1111:1110:1011:1111:1011:1111:1111",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483648,
               vendor = &lt;unset&gt;,
               eax = "1000:0000:0000:0000:0000:0000:0000:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483647,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:0000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
               edx = "0010:0000:0001:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483640,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0011:0000:0010:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            }
         ],
      }
   ],
   memorySize = 1771626496,
   numaInfo = (vim.host.NumaInfo) {
      dynamicType = &lt;unset&gt;,
      type = "Fake Numa",
      numNodes = 1,
      numaNode = (vim.host.NumaNode) [
         (vim.host.NumaNode) {
            dynamicType = &lt;unset&gt;,
            typeId = 0,
            cpuID = (short) [
               1,
               0
            ],
            memoryRangeBegin = 0,
            memoryRangeLength = 1879048192,
         }
      ],
   },
   pciDevice = (vim.host.PciDevice) [
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:00.0",
         classId = 1536,
         bus = 0,
         slot = 0,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 29072,
         subDeviceId = 6518,
         deviceName = "440BX/ZX/DX - 82443BX/ZX/DX Host bridge",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:01.0",
         classId = 1540,
         bus = 0,
         slot = 1,
         function = 0,
         vendorId = -32634,
         subVendorId = 0,
         vendorName = "Intel Corporation",
         deviceId = 29073,
         subDeviceId = 0,
         deviceName = "440BX/ZX/DX - 82443BX/ZX/DX AGP bridge",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.0",
         classId = 1537,
         bus = 0,
         slot = 7,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28944,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 ISA",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.1",
         classId = 257,
         bus = 0,
         slot = 7,
         function = 1,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28945,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 IDE",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.3",
         classId = 1664,
         bus = 0,
         slot = 7,
         function = 3,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28947,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 ACPI",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.7",
         classId = 2176,
         bus = 0,
         slot = 7,
         function = 7,
         vendorId = 5549,
         subVendorId = 5549,
         vendorName = "VMWare Inc",
         deviceId = 1856,
         subDeviceId = 1856,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:0f.0",
         classId = 768,
         bus = 0,
         slot = 15,
         function = 0,
         vendorId = 5549,
         subVendorId = 5549,
         vendorName = "VMWare Inc",
         deviceId = 1029,
         subDeviceId = 1029,
         deviceName = "Virtual SVGA",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:10.0",
         classId = 256,
         bus = 0,
         slot = 16,
         function = 0,
         vendorId = 4096,
         subVendorId = 5549,
         vendorName = "LSI Logic / Symbios Logic",
         deviceId = 48,
         subDeviceId = 6518,
         deviceName = "53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:11.0",
         classId = 1540,
         bus = 0,
         slot = 17,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1936,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.0",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.1",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.2",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.3",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.4",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.5",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.6",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.7",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.0",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.1",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.2",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.3",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.4",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.5",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.6",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.7",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.0",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.1",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.2",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.3",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.4",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.5",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.6",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.7",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.0",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.1",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.2",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.3",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.4",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.5",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.6",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.7",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "02:00.0",
         classId = 512,
         bus = 2,
         slot = 0,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 4111,
         subDeviceId = 1872,
         deviceName = "82545EM Gigabit Ethernet Controller (Copper)",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "02:01.0",
         classId = 512,
         bus = 2,
         slot = 1,
         function = 0,
         vendorId = 4130,
         subVendorId = 4130,
         vendorName = "Advanced Micro Devices [AMD]",
         deviceId = 8192,
         subDeviceId = 8192,
         deviceName = "NetFinity 10/100 Fast Ethernet",
      }
   ],
   cpuFeature = (vim.host.CpuIdInfo) [
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = 0,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0000:0000:1010",
         ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
         ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
         edx = "0100:1001:0110:0101:0110:1110:0110:1001",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = 1,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0110:1111:1011",
         ebx = "0000:0000:0000:0001:0000:1000:0000:0000",
         ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
         edx = "0000:1111:1110:1011:1111:1011:1111:1111",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483648,
         vendor = &lt;unset&gt;,
         eax = "1000:0000:0000:0000:0000:0000:0000:1000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
         edx = "0000:0000:0000:0000:0000:0000:0000:0000",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483647,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0000:0000:0000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
         edx = "0000:0000:0001:0000:0000:0000:0000:0000",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483640,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0011:0000:0010:1000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
         edx = "0000:0000:0000:0000:0000:0000:0000:0000",
      }
   ],
   biosInfo = (vim.host.BIOSInfo) {
      dynamicType = &lt;unset&gt;,
      biosVersion = "6.00",
      releaseDate = "2008-07-29T00:00:00Z",
   },
 }

[[Category: Vimsh]]</text>
    <sha1>a75865c991ff4a8c508f9b7a7a84fdebdc9e4c68</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/hostsummary</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>526</id>
    <parentid>225</parentid>
    <timestamp>2008-12-29T04:54:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6121" xml:space="preserve">==== Vimsh hostsvc/hostsummary ====
Usage: hostsummary

Retrieves the host summary information.
====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/hostsummary
 (vim.host.Summary) {
   dynamicType = &lt;unset&gt;,
   host = 'vim.HostSystem:ha-host',
   hardware = (vim.host.Summary.HardwareSummary) {
      dynamicType = &lt;unset&gt;,
      vendor = "VMware, Inc.",
      model = "VMware Virtual Platform",
      uuid = "238ef3e5-a923-b48c-5ab7-0d820b1cbde7",
      otherIdentifyingInfo = (vim.host.SystemIdentificationInfo) [
         (vim.host.SystemIdentificationInfo) {
            dynamicType = &lt;unset&gt;,
            identifierValue = " No Asset Tag",
            identifierType = (vim.ElementDescription) {
               dynamicType = &lt;unset&gt;,
               label = "AssetTag",
               summary = "AssetTag",
               key = "AssetTag",
            },
         }
      ],
      memorySize = 1771626496,
      cpuModel = "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz",
      cpuMhz = 2407,
      numCpuPkgs = 2,
      numCpuCores = 2,
      numCpuThreads = 2,
      numNics = 1,
      numHBAs = 3,
   },
   runtime = (vim.host.RuntimeInfo) {
      dynamicType = &lt;unset&gt;,
      connectionState = "connected",
      powerState = "poweredOn",
      inMaintenanceMode = false,
      bootTime = "2008-11-24T23:10:41.665567Z",
      healthSystemRuntime = (vim.host.HealthStatusSystem.Runtime) {
         dynamicType = &lt;unset&gt;,
         systemHealthInfo = (vim.host.SystemHealthInfo) {
            dynamicType = &lt;unset&gt;,
            numericSensorInfo = (vim.host.NumericSensorInfo) [
               (vim.host.NumericSensorInfo) {
                  dynamicType = &lt;unset&gt;,
                  name = "VMware Rollup Health State",
                  healthState = (vim.ElementDescription) {
                     dynamicType = &lt;unset&gt;,
                     label = "Green",
                     summary = "Green",
                     key = "Green",
                  },
                  currentReading = 0,
                  unitModifier = 0,
                  baseUnits = "",
                  rateUnits = &lt;unset&gt;,
                  sensorType = "system",
               },
               (vim.host.NumericSensorInfo) {
                  dynamicType = &lt;unset&gt;,
                  name = "Phoenix Technologies LTD System BIOS 6.00 2008-07-29 00:00:00.000",
                  healthState = (vim.ElementDescription) {
                     dynamicType = &lt;unset&gt;,
                     label = "Green",
                     summary = "Green",
                     key = "Green",
                  },
                  currentReading = 0,
                  unitModifier = 0,
                  baseUnits = "",
                  rateUnits = &lt;unset&gt;,
                  sensorType = "Software Components",
               },
               (vim.host.NumericSensorInfo) {
                  dynamicType = &lt;unset&gt;,
                  name = "VMware Inc. Hypervisor VMware ESX Server 3i 3.5.0 build-123629 2008-10-15 21:03:57.000",
                  healthState = (vim.ElementDescription) {
                     dynamicType = &lt;unset&gt;,
                     label = "Green",
                     summary = "Green",
                     key = "Green",
                  },
                  currentReading = 0,
                  unitModifier = 0,
                  baseUnits = "",
                  rateUnits = &lt;unset&gt;,
                  sensorType = "Software Components",
               }
            ],
         },
         hardwareStatusInfo = (vim.host.HardwareStatusInfo) {
            dynamicType = &lt;unset&gt;,
            memoryStatusInfo = (vim.host.HardwareStatusInfo.HardwareElementInfo) [
               (vim.host.HardwareStatusInfo.HardwareElementInfo) {
                  dynamicType = &lt;unset&gt;,
                  name = "Memory",
                  status = (vim.ElementDescription) {
                     dynamicType = &lt;unset&gt;,
                     label = "Green",
                     summary = "Physical element is functioning as expected",
                     key = "Green",
                  },
               }
            ],
            cpuStatusInfo = (vim.host.HardwareStatusInfo.HardwareElementInfo) [
               (vim.host.HardwareStatusInfo.HardwareElementInfo) {
                  dynamicType = &lt;unset&gt;,
                  name = "CPU socket #0",
                  status = (vim.ElementDescription) {
                     dynamicType = &lt;unset&gt;,
                     label = "Green",
                     summary = "Physical element is functioning as expected",
                     key = "Green",
                  },
               },
               (vim.host.HardwareStatusInfo.HardwareElementInfo) {
                  dynamicType = &lt;unset&gt;,
                  name = "CPU socket #1",
                  status = (vim.ElementDescription) {
                     dynamicType = &lt;unset&gt;,
                     label = "Green",
                     summary = "Physical element is functioning as expected",
                     key = "Green",
                  },
               }
            ],
         },
      },
   },
   config = (vim.host.Summary.ConfigSummary) {
      dynamicType = &lt;unset&gt;,
      name = "localhost.example.com",
      port = 902,
      product = (vim.AboutInfo) {
         dynamicType = &lt;unset&gt;,
         name = "VMware ESX Server 3i",
         fullName = "VMware ESX Server 3i 3.5.0 build-123629",
         vendor = "VMware, Inc.",
         version = "3.5.0",
         build = "123629",
         localeVersion = "INTL",
         localeBuild = "000",
         osType = "vmnix-x86",
         productLineId = "embeddedEsx",
         apiType = "HostAgent",
         apiVersion = "2.5u2",
      },
      vmotionEnabled = false,
   },
   quickStats = (vim.host.Summary.QuickStats) {
      dynamicType = &lt;unset&gt;,
      overallCpuUsage = 579,
      overallMemoryUsage = 356,
      distributedCpuFairness = &lt;unset&gt;,
      distributedMemoryFairness = &lt;unset&gt;,
   },
   overallStatus = "gray",
   rebootRequired = false,
   managementServerIp = &lt;unset&gt;,
}


[[Category: Vimsh]]</text>
    <sha1>902cee54e2917767e26ccea205a6babf9b9061c7</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Solo/environment</title>
  <ns>0</ns>
  <id>182</id>
  <revision>
    <id>527</id>
    <parentid>352</parentid>
    <timestamp>2008-12-29T05:07:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3239" xml:space="preserve">==== vimsh solo/environment ====
Usage: environment

Display the default vm environment on this host.
====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password solo/environment
 (vim.vm.ConfigTarget) {
   dynamicType = &lt;unset&gt;,
   numCpus = 2,
   numCpuCores = 2,
   numNumaNodes = 1,
   datastore = (vim.vm.DatastoreInfo) [
      (vim.vm.DatastoreInfo) {
         dynamicType = &lt;unset&gt;,
         name = "store",
         datastore = (vim.Datastore.Summary) {
            dynamicType = &lt;unset&gt;,
            datastore = 'vim.Datastore:24b27cd4-228f5304-5b3a-00a1c2a09550',
            name = "store",
            url = "/vmfs/volumes/24b27cd4-228f5304-5b3a-00a1c2a09550",
            capacity = 639681691648,
            freeSpace = 62658707456,
            accessible = true,
            multipleHostAccess = &lt;unset&gt;,
            type = "VMFS",
         },
         capability = (vim.Datastore.Capability) {
            dynamicType = &lt;unset&gt;,
            directoryHierarchySupported = true,
            rawDiskMappingsSupported = true,
            perFileThinProvisioningSupported = true,
         },
         maxFileSize = 0,
         mode = "readWrite",
      },
      (vim.vm.DatastoreInfo) {
         dynamicType = &lt;unset&gt;,
         name = "datastore2",
         datastore = (vim.Datastore.Summary) {
            dynamicType = &lt;unset&gt;,
            datastore = 'vim.Datastore:381b025b-1f339a0d-c14d-000d191cdef8',
            name = "datastore2",
            url = "/vmfs/volumes/381b025b-1f339a0d-c14d-000d191cdef8",
            capacity = 3489660928,
            freeSpace = 3178233856,
            accessible = true,
            multipleHostAccess = &lt;unset&gt;,
            type = "VMFS",
         },
         capability = (vim.Datastore.Capability) {
            dynamicType = &lt;unset&gt;,
            directoryHierarchySupported = true,
            rawDiskMappingsSupported = true,
            perFileThinProvisioningSupported = true,
         },
         maxFileSize = 0,
         mode = "readWrite",
      }
   ],
   network = (vim.vm.NetworkInfo) [
      (vim.vm.NetworkInfo) {
         dynamicType = &lt;unset&gt;,
         name = "VM Network",
         network = (vim.Network.Summary) {
            dynamicType = &lt;unset&gt;,
            network = 'vim.Network:HaNetwork-VM Network',
            name = "VM Network",
            accessible = true,
         },
      }
   ],
   cdRom = (vim.vm.CdromInfo) [
      (vim.vm.CdromInfo) {
         dynamicType = &lt;unset&gt;,
         name = "/vmfs/devices/genide/vmhba0:0:0",
      }
   ],
   usb = (vim.vm.UsbInfo) [
      (vim.vm.UsbInfo) {
         dynamicType = &lt;unset&gt;,
         name = "435890192344555",
         description = "My funky USB dongle",
         vendor = 0,
         product = 0,
         physicalPath = "",
         summary = (vim.vm.Summary) null,
      },
      (vim.vm.UsbInfo) {
         dynamicType = &lt;unset&gt;,
         name = "43589324325534",
         description = "Digital SEC FVRW Doohickey",
         vendor = 0,
         product = 0,
         physicalPath = "",
         summary = (vim.vm.Summary) null,
      }
   ],
   maxMemMBOptimalPerf = 1689,
   resourcePool = (vim.ResourcePool.RuntimeInfo) null,
   autoVmotion = &lt;unset&gt;,
 }


[[Category: Vimsh]]</text>
    <sha1>5260f2027b5aa1476ef8f08ee7d8d4a7dff33517</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsh</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>528</id>
    <parentid>185</parentid>
    <timestamp>2008-12-29T05:11:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3477" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX, there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;

==== List of commands ====

Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki)

Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help and in many cases some example output of the commands.

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that vimsh will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>6832fcf35e7d5db65065bd40174f588f25852053</sha1>
  </revision>
  <revision>
    <id>532</id>
    <parentid>528</parentid>
    <timestamp>2008-12-29T20:36:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added tip from lamw on using vim-cmd on ESXi</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3558" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX (ESX3.5+), there's also a command line non interactive version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;
When using ESX embedded (ESXi3.5+) the command is [[vim-cmd]] instead.

==== List of commands ====

Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki)

Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help and in many cases some example output of the commands.

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that vimsh will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>a009f52a0109e74f7a8bc213ce642c45ff9796e8</sha1>
  </revision>
  <revision>
    <id>533</id>
    <parentid>532</parentid>
    <timestamp>2008-12-29T20:37:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3558" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 #vimsh
 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help           puload        
 internalsvc/  ?                csls           pinfo          puse          
 proxysvc/    argtype       csuimport  pload         quit          
 solo/           cls               echo         ploadpath   sleep         
 vimsvc/       csimport      exit           pls             source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX (ESX3.5+), there's also a non interactive command line version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;
When using ESX embedded (ESXi3.5+) the command is [[vim-cmd]] instead.

==== List of commands ====

Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki)

Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help and in many cases some example output of the commands.

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that vimsh will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>cf4f257852a2370d7b123973817b199cb06a6f09</sha1>
  </revision>
  <revision>
    <id>547</id>
    <parentid>533</parentid>
    <timestamp>2008-12-30T12:30:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>fix the alignment now that we use a monospaced font on source</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3506" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help          puload
 internalsvc/  ?             csls          pinfo         puse
 proxysvc/     argtype       csuimport     pload         quit
 solo/         cls           echo          ploadpath     sleep
 vimsvc/       csimport      exit          pls           source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX (ESX3.5+), there's also a non interactive command line version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative:
 vimsh -n -e &lt;command&gt;
When using ESX embedded (ESXi3.5+) the command is [[vim-cmd]] instead.

==== List of commands ====

Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki)

Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help and in many cases some example output of the commands.

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that vimsh will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>704eb4f742e85774ba1ccf4dabac94b912237fb5</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vmsvc/device.connection</title>
  <ns>0</ns>
  <id>155</id>
  <revision>
    <id>529</id>
    <parentid>310</parentid>
    <timestamp>2008-12-29T20:32:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example to disconnect CDrom</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="689" xml:space="preserve">==== vimsh vmsvc/device.connection ====
Usage: device.connection vmid deviceKey connect

Connect/Disconnect the virtual device specified


====example: disconnect cdrom device from VM====
Get the ID of your VM in question using (scroll using shift page up / page down if you have to)

 vmsvc/getallvms
Write down the VM ID for example it can be a number like 4400
Find the key for your VirtualCDrom by querying the hardware devices for your VM.

 vmsvc/device.getdevices 4400
Scroll up again and write down the Key, in my case it is 3000
Now disconnect the CDrom device by running:

 vmsvc/device.connection 4400 3000 false
Use true if you want to connect the device.


[[Category: Vimsh]]</text>
    <sha1>1f32e5ea8eec0d4fb4099a09c81f741435be3a9e</sha1>
  </revision>
  <revision>
    <id>530</id>
    <parentid>529</parentid>
    <timestamp>2008-12-29T20:32:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="690" xml:space="preserve">==== vimsh vmsvc/device.connection ====
Usage: device.connection vmid deviceKey connect

Connect/Disconnect the virtual device specified


====example: disconnect cdrom device from VM====
Get the ID of your VM in question using (scroll using shift page up / page down if you have to)

 vmsvc/getallvms
Write down the VM ID for example it can be a number like 4400

Find the key for your VirtualCDrom by querying the hardware devices for your VM.

 vmsvc/device.getdevices 4400
Scroll up again and write down the Key, in my case it is 3000
Now disconnect the CDrom device by running:

 vmsvc/device.connection 4400 3000 false
Use true if you want to connect the device.


[[Category: Vimsh]]</text>
    <sha1>8b1304369cc36aae9523a78d81b51b4a3ae42f02</sha1>
  </revision>
  <revision>
    <id>531</id>
    <parentid>530</parentid>
    <timestamp>2008-12-29T20:33:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>spaces...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="691" xml:space="preserve">==== vimsh vmsvc/device.connection ====
Usage: device.connection vmid deviceKey connect

Connect/Disconnect the virtual device specified


====example: disconnect cdrom device from VM====
Get the ID of your VM in question using (scroll using shift page up / page down if you have to)

 vmsvc/getallvms
Write down the VM ID for example it can be a number like 4400

Find the key for your VirtualCDrom by querying the hardware devices for your VM.

 vmsvc/device.getdevices 4400
Scroll up again and write down the Key, in my case it is 3000

Now disconnect the CDrom device by running:

 vmsvc/device.connection 4400 3000 false
Use true if you want to connect the device.


[[Category: Vimsh]]</text>
    <sha1>269f173993539898b9209bb507e05d2015cec78b</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>534</id>
    <parentid>431</parentid>
    <timestamp>2008-12-29T21:23:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1220" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://teckinfo.blogspot.com Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>146c890c58b7914a2c43c8e9db78709f89548284</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>535</id>
    <parentid>500</parentid>
    <timestamp>2008-12-29T21:34:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Updated VIX 1.6 link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="757" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

Supported on VMware Workstation 6.0.x and up, VMware Server 1.x and up, VMware ESX3.5U2+

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX 1.1 API reference Guide]

[http://www.vmware.com/support/developer/vix-api/vix16_reference/ VMware VIX 1.6 API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>d409a598991f468d263e00b3ba2b33b71d650c34</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/summary/</title>
  <ns>0</ns>
  <id>284</id>
  <revision>
    <id>536</id>
    <timestamp>2008-12-29T22:07:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/summary/ ====   [[hostsvc/summary/fsvolume]]  [[hostsvc/summary/hba]]  [[hostsvc/summary/scsilun]]  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="138" xml:space="preserve">==== vimsh hostsvc/summary/ ====

 [[hostsvc/summary/fsvolume]]
 [[hostsvc/summary/hba]]
 [[hostsvc/summary/scsilun]]

[[Category: Vimsh]]</text>
    <sha1>3382456d79c6ff6754e5c74fbb8bf2aa17df397b</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/summary/fsvolume</title>
  <ns>0</ns>
  <id>285</id>
  <revision>
    <id>537</id>
    <timestamp>2008-12-29T22:09:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/summary/fsvolume ==== Usage: fsvolume  Get file system volume information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="114" xml:space="preserve">==== vimsh hostsvc/summary/fsvolume ====
Usage: fsvolume

Get file system volume information.

[[Category: Vimsh]]</text>
    <sha1>b8a40ee0a8c60104a8475ace08a95d1f98d2393e</sha1>
  </revision>
  <revision>
    <id>544</id>
    <parentid>537</parentid>
    <timestamp>2008-12-30T12:20:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="598" xml:space="preserve">==== vimsh hostsvc/summary/fsvolume ====
Usage: fsvolume

Get file system volume information.

====example output====
# vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/summary/fsvolume
   Name         Type      SubType                         Path                             Device         Capacity       Mode
store          VmfsVolume   VMFS      /vmfs/volumes/24b85cd6-123d5101-7b21-0016c8c08128   vmhba32:0:0:1   639681691648 readWrite
datastore2   VmfsVolume   VMFS      /vmfs/volumes/271a2c8b-1f21810d-c28d-000d172bcef8   vmhba1:0:0:3      3489660928 readWrite


[[Category: Vimsh]]</text>
    <sha1>a39a836264186a151100251db5a610f00c168c21</sha1>
  </revision>
  <revision>
    <id>545</id>
    <parentid>544</parentid>
    <timestamp>2008-12-30T12:21:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>fix formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="602" xml:space="preserve">==== vimsh hostsvc/summary/fsvolume ====
Usage: fsvolume

Get file system volume information.

====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/summary/fsvolume
    Name         Type      SubType                         Path                             Device         Capacity       Mode
 store          VmfsVolume   VMFS      /vmfs/volumes/24b85cd6-123d5101-7b21-0016c8c08128   vmhba32:0:0:1   639681691648 readWrite
 datastore2   VmfsVolume   VMFS      /vmfs/volumes/271a2c8b-1f21810d-c28d-000d172bcef8   vmhba1:0:0:3      3489660928 readWrite


[[Category: Vimsh]]</text>
    <sha1>7d05421c3ed83bebd818acbf5664e9648362c6d7</sha1>
  </revision>
  <revision>
    <id>546</id>
    <parentid>545</parentid>
    <timestamp>2008-12-30T12:22:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>rinse repeat (too lame to use preview)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="600" xml:space="preserve">==== vimsh hostsvc/summary/fsvolume ====
Usage: fsvolume

Get file system volume information.

====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/summary/fsvolume
    Name         Type      SubType                         Path                             Device         Capacity       Mode
 store        VmfsVolume   VMFS      /vmfs/volumes/24b85cd6-123d5101-7b21-0016c8c08128   vmhba32:0:0:1   639681691648 readWrite
 datastore2   VmfsVolume   VMFS      /vmfs/volumes/271a2c8b-1f21810d-c28d-000d172bcef8   vmhba1:0:0:3      3489660928 readWrite


[[Category: Vimsh]]</text>
    <sha1>81d7393a45cf8ab7cf2e6749ac2e23144868456c</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/summary/hba</title>
  <ns>0</ns>
  <id>286</id>
  <revision>
    <id>538</id>
    <timestamp>2008-12-29T22:10:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/summary/hba ==== Usage: hba  Get storage vmhba information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="99" xml:space="preserve">==== vimsh hostsvc/summary/hba ====
Usage: hba

Get storage vmhba information.

[[Category: Vimsh]]</text>
    <sha1>629fbed4ca84bc5dbfbbffc75bea7b3fb095efd4</sha1>
  </revision>
  <revision>
    <id>541</id>
    <parentid>538</parentid>
    <timestamp>2008-12-30T11:20:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="485" xml:space="preserve">==== vimsh hostsvc/summary/hba ====
Usage: hba

Get storage vmhba information.

====example output====

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/summary/hba 
 Device         Type           Driver        PCI Id          Model
 vmhba32   InternetScsiHba   iscsi_mod     UNKNOWN -    iSCSI Software A
 vmhba0    BlockHba          ide           00:07.1      82371AB/EB/MB PI
 vmhba1    ParallelScsiHba   mptscsi_2xx   00:10.0      53c1030 PCI-X Fu


[[Category: Vimsh]]</text>
    <sha1>dc12433116995e5e03e49a8c5d7c2cd00461d647</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/summary/scsilun</title>
  <ns>0</ns>
  <id>287</id>
  <revision>
    <id>539</id>
    <timestamp>2008-12-29T22:11:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/summary/scsilun ==== Usage: scsilun  Get storage LUN information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="105" xml:space="preserve">==== vimsh hostsvc/summary/scsilun ====
Usage: scsilun

Get storage LUN information.

[[Category: Vimsh]]</text>
    <sha1>018b3ff7d97de3c44faa7e7e24e00b51f75e7f5d</sha1>
  </revision>
  <revision>
    <id>543</id>
    <parentid>539</parentid>
    <timestamp>2008-12-30T12:16:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="619" xml:space="preserve">==== vimsh hostsvc/summary/scsilun ====
Usage: scsilun

Get storage LUN information.

====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/summary/scsilun
   Device      Type     Vendor         Model                           UUID                       Hba
 vmhba32:0:0   disk    IET        VIRTUAL-DISK       020000000010521222485261113212             vmhba32
 vmhba0:0:0    cdrom   VMware     Block device       000e000000544e582168214b21234b55505b3c20   vmhba0
 vmhba1:0:0    disk    VMware,    VMware Virtual S   0020003000886e576861123a42203b54403b4c20   vmhba1


[[Category: Vimsh]]</text>
    <sha1>26c8d308b6dd18e85e414b8d439d7f467b402ce2</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>540</id>
    <parentid>411</parentid>
    <timestamp>2008-12-30T08:21:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="518" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/thread/156302 HBA Load Balancer]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]</text>
    <sha1>c5b0c4398eaa74fcfa45f0280f9af56d02876095</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>542</id>
    <parentid>429</parentid>
    <timestamp>2008-12-30T12:11:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>marked what's done</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1532" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages. Partly done
* Add "what's new" to the main page
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)
* Do email notifications work? (I think not)

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?

[[Category: website]]</text>
    <sha1>762c6a3b1b0b5afac5219e27af6c686e2d41a896</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsh: hostsvc/</title>
  <ns>0</ns>
  <id>45</id>
  <revision>
    <id>548</id>
    <parentid>203</parentid>
    <timestamp>2008-12-30T12:32:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>remove fluff</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1058" xml:space="preserve">==== Hostsvc sub ====

ESX host services, lists and/or change host specific information such as firewall information, host status like maintenance mode and standby.

 [[hostsvc/advopt/]]
 [[hostsvc/autostartmanager/]]
 [[hostsvc/datastore/]]
 [[hostsvc/datastorebrowser/]]
 [[hostsvc/firmware/]]
 [[hostsvc/net/]]
 [[hostsvc/rsrc/]]
 [[hostsvc/storage/]]
 [[hostsvc/summary/]]
 [[hostsvc/vmotion/]]
 [[hostsvc/connect]]
 [[hostsvc/cpuinfo]]
 [[hostsvc/firewall_disable_ruleset]]
 [[hostsvc/firewall_enable_ruleset]] 
 [[hostsvc/hostconfig]]
 [[hostsvc/hosthardware]]
 [[hostsvc/hostsummary]]
 [[hostsvc/login]]
 [[hostsvc/logout]]
 [[hostsvc/maintenance_mode_enter]]
 [[hostsvc/maintenance_mode_exit]]
 [[hostsvc/memoryinfo]]
 [[hostsvc/pci_add]]
 [[hostsvc/pci_remove]]
 [[hostsvc/queryconnectioninfo]]
 [[hostsvc/querydisabledmethods]]
 [[hostsvc/refresh_firewall]]
 [[hostsvc/refresh_services]] 
 [[hostsvc/runtimeinfo]] 
 [[hostsvc/set_hostid]] 
 [[hostsvc/standby_mode_enter]] 
 [[hostsvc/standby_mode_exit]] 
 [[hostsvc/task_list]]

[[Category: Vimsh]]</text>
    <sha1>238427543192c682119d144e1a2bad6404116a66</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Hostsvc/advopt/</title>
  <ns>0</ns>
  <id>288</id>
  <revision>
    <id>549</id>
    <timestamp>2008-12-30T12:34:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/advopt ====   [[hostsvc/advopt/options]]  [[hostsvc/advopt/settings]]  [[hostsvc/advopt/update]]  [[hostsvc/advopt/view]]  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="161" xml:space="preserve">==== vimsh hostsvc/advopt ====

 [[hostsvc/advopt/options]]
 [[hostsvc/advopt/settings]]
 [[hostsvc/advopt/update]]
 [[hostsvc/advopt/view]]

[[Category: Vimsh]]</text>
    <sha1>faff3dd3e3ab4b11247cb95eee16f14fb17ed167</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsh: internalsvc/</title>
  <ns>0</ns>
  <id>48</id>
  <revision>
    <id>550</id>
    <parentid>465</parentid>
    <timestamp>2008-12-30T12:36:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>remove fluff</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="803" xml:space="preserve">==== vimsh internalsvc/ ====

 [[internalsvc/perfcount/]]       
 [[internalsvc/access_address]]
 [[internalsvc/connect]]           
 [[internalsvc/host_mode_lock]]            
 [[internalsvc/login]]     
 [[internalsvc/loglist]]             
 [[internalsvc/logout]]   
 [[internalsvc/redirect_stderr]]      
 [[internalsvc/redirect_stdout]]
 [[internalsvc/refresh]]       
 [[internalsvc/refresh_consolenic]]            
 [[internalsvc/refresh_datastores]]      
 [[internalsvc/refresh_gateway]]               
 [[internalsvc/refresh_network]]
 [[internalsvc/refresh_pnic]]            
 [[internalsvc/set_exception_variable]]  
 [[internalsvc/set_log_level]]           
 [[internalsvc/shutdown]]                
 [[internalsvc/throw_exception]]         
 [[internalsvc/use_fds]]


[[Category: Vimsh]]</text>
    <sha1>08c3987b370c94c0b96c7cd8314179554be726cf</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsh: proxysvc/</title>
  <ns>0</ns>
  <id>49</id>
  <revision>
    <id>551</id>
    <parentid>455</parentid>
    <timestamp>2008-12-30T12:37:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>remove fluff</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="260" xml:space="preserve">==== vimsh proxysvc/ ====

 [[proxysvc/add_np_service]]  
 [[proxysvc/add_tcp_service]] 
 [[proxysvc/connect]]    
 [[proxysvc/login]]
 [[proxysvc/logout]]
 [[proxysvc/port_info]]
 [[proxysvc/remove_service]]   
 [[proxysvc/service_list]]


[[Category: Vimsh]]</text>
    <sha1>fc976377e8361255e22495781efb8b9782764acc</sha1>
  </revision>
</page>
<page arvcontinue="20081228214416|503">
  <title>Vimsh: solo/</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>552</id>
    <parentid>350</parentid>
    <timestamp>2008-12-30T12:38:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>remove fluff</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="186" xml:space="preserve">==== vimsh solo/ ====

 [[solo/connect]]
 [[solo/environment]]
 [[solo/login]]
 [[solo/logout]]
 [[solo/querycfgopt]] 
 [[solo/querycfgoptdesc]]
 [[solo/registervm]]

[[Category: Vimsh]]</text>
    <sha1>8ddc68f3054972dac99dda47b45503467aaf18fe</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Vimsh: vimsvc/</title>
  <ns>0</ns>
  <id>50</id>
  <revision>
    <id>553</id>
    <parentid>400</parentid>
    <timestamp>2008-12-30T12:38:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>remove fluff</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="263" xml:space="preserve">==== vimsh vimsvc/ ====

 [[vimsvc/auth/]]
 [[vimsvc/connect]]
 [[vimsvc/license]]
 [[vimsvc/login]]
 [[vimsvc/logout]]
 [[vimsvc/property_dump]]
 [[vimsvc/task_cancel]]
 [[vimsvc/task_description]]
 [[vimsvc/task_info]]
 [[vimsvc/task_list]]

[[Category: Vimsh]]</text>
    <sha1>fe13efdcfb9a966578c2a1ca3c3d59c8170c7e24</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Vimsh: vmsvc/</title>
  <ns>0</ns>
  <id>46</id>
  <revision>
    <id>554</id>
    <parentid>337</parentid>
    <timestamp>2008-12-30T12:39:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>remove fluff</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2160" xml:space="preserve">==== vimsh vmsvc/ ====

 [[vmsvc/acquiremksticket]]              
 [[vmsvc/connect]]                  
 [[vmsvc/convert.toTemplate]]          
 [[vmsvc/convert.toVm]]               
 [[vmsvc/createdummyvm]]        
 [[vmsvc/destroy]]             
 [[vmsvc/device.connection]]               
 [[vmsvc/device.connusbdev]]            
 [[vmsvc/device.disconnusbdev]]       
 [[vmsvc/device.diskadd]]              
 [[vmsvc/device.diskaddexisting]]          
 [[vmsvc/device.diskremove]]     
 [[vmsvc/device.getdevices]]          
 [[vmsvc/device.toolsSyncSet]]
 [[vmsvc/device.vmiadd]] 
 [[vmsvc/device.vmiremove]]             
 [[vmsvc/devices.createnic]]         
 [[vmsvc/get.capability]]         
 [[vmsvc/get.config]]                   
 [[vmsvc/get.config.cpuidmask]]
 [[vmsvc/get.configoption]]       
 [[vmsvc/get.datastores]]                
 [[vmsvc/get.disabledmethods]]       
 [[vmsvc/get.environment]]           
 [[vmsvc/get.filelayout]]       
 [[vmsvc/get.guest]]        
 [[vmsvc/get.guestheartbeatStatus]]  
 [[vmsvc/get.managedentitystatus]]       
 [[vmsvc/get.networks]]         
 [[vmsvc/get.runtime]]          
 [[vmsvc/get.snapshotinfo]]     
 [[vmsvc/get.summary]]  
 [[vmsvc/get.tasklist]]      
 [[vmsvc/getallvms]]       
 [[vmsvc/gethostconstraints]]  
 [[vmsvc/login]]        
 [[vmsvc/logout]]           
 [[vmsvc/message]]    
 [[vmsvc/power.getstate]]      
 [[vmsvc/power.hibernate]]
 [[vmsvc/power.off]]                 
 [[vmsvc/power.on]]                  
 [[vmsvc/power.reboot]]              
 [[vmsvc/power.reset]]               
 [[vmsvc/power.shutdown]]            
 [[vmsvc/power.suspend]]             
 [[vmsvc/reload]]                    
 [[vmsvc/setscreenres]]              
 [[vmsvc/snapshot.create]]           
 [[vmsvc/snapshot.get]]              
 [[vmsvc/snapshot.remove]]           
 [[vmsvc/snapshot.removeall]]        
 [[vmsvc/snapshot.revert]]           
 [[vmsvc/snapshot.setoption]]        
 [[vmsvc/tools.cancelinstall]]       
 [[vmsvc/tools.install]]             
 [[vmsvc/tools.upgrade]]             
 [[vmsvc/unregister]]                
 [[vmsvc/upgrade]]                   


[[Category: Vimsh]]</text>
    <sha1>53a11c31254f28fe46168c1dabc0713a7d81e902</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/advopt/</title>
  <ns>0</ns>
  <id>288</id>
  <revision>
    <id>555</id>
    <parentid>549</parentid>
    <timestamp>2008-12-31T17:40:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="162" xml:space="preserve">==== vimsh hostsvc/advopt/ ====

 [[hostsvc/advopt/options]]
 [[hostsvc/advopt/settings]]
 [[hostsvc/advopt/update]]
 [[hostsvc/advopt/view]]

[[Category: Vimsh]]</text>
    <sha1>39af7713af13dd9075d3c1ac8ff94808a210c5c6</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/advopt/options</title>
  <ns>0</ns>
  <id>289</id>
  <revision>
    <id>556</id>
    <timestamp>2008-12-31T18:01:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/advopt/options ==== Usage: Get the list of all supported options. ==== example output ==== Attached is some example output from a pristine ESX3.5i host.   # vmware-vim-c...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155788" xml:space="preserve">==== vimsh hostsvc/advopt/options ====
Usage: Get the list of all supported options.
==== example output ====
Attached is some example output from a pristine ESX3.5i host.

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/advopt/options
 (vim.option.OptionDef) [
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RoutingPolicy",
      summary = "policy for interrupt routing, 1 for idle-routing, 2 for greedy routing, 0 to disable moving IRQs",
      key = "Irq.RoutingPolicy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BestVcpuRouting",
      summary = "",
      key = "Irq.BestVcpuRouting",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IRQRebalancePeriod",
      summary = "time in ms between attempts to rebalance interrupts",
      key = "Irq.IRQRebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 20000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IRQMaxLoadPct",
      summary = "maximum percentage of a cpu's resources that should be devoted to interrupts",
      key = "Irq.IRQMaxLoadPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 70,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogToFile",
      summary = "Send vmkernel log messages to /var/log/vmkernel",
      key = "Misc.LogToFile",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogToSerial",
      summary = "Send vmkernel log messages to the serial port",
      key = "Misc.LogToSerial",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogWldPrefix",
      summary = "Including running world on every log statement",
      key = "Misc.LogWldPrefix",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinimalPanic",
      summary = "Don't attempt to coredump after PSODing",
      key = "Misc.MinimalPanic",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BlueScreenTimeout",
      summary = "timeout in seconds, 0 is no timeout",
      key = "Misc.BlueScreenTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 65535,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatTimeout",
      summary = "Timeout in seconds, for sending NMI to the locked CPU",
      key = "Misc.HeartbeatTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatInterval",
      summary = "Interval in msec to check CPU lockups",
      key = "Misc.HeartbeatInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 86400000,
         defaultValue = 10000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatPanicTimeout",
      summary = "Interval in seconds after which to panic if no heartbeats received",
      key = "Misc.HeartbeatPanicTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatAnyPcpuPanic",
      summary = "Should we panic on any cpu lockups? (default we panic only for COS)",
      key = "Misc.HeartbeatAnyPcpuPanic",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MCEMonitorInterval",
      summary = "Interval[1 - 0x0xffffffff secs] to check Machine Check Errors",
      key = "Misc.MCEMonitorInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = -1,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DebugMemEnable",
      summary = "Enable memory debugging, 0 to disable",
      key = "Misc.DebugMemEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DebugBuddyEnable",
      summary = "Enable buddy debugging, 0 to disable",
      key = "Misc.DebugBuddyEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableHighDMA",
      summary = "Enable DMA above 4GB",
      key = "Misc.EnableHighDMA",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMinHardPeriod",
      summary = "Minimum hard timer interrupt period in microseconds",
      key = "Misc.TimerMinHardPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMaxHardPeriod",
      summary = "Maximum hard timer interrupt period in microseconds",
      key = "Misc.TimerMaxHardPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMinGuestPeriod",
      summary = "Minimum period for guest timer callbacks in microseconds",
      key = "Misc.TimerMinGuestPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 1000000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemAdmitMapEntriesMin",
      summary = "free KVMap entries required to power on VM",
      key = "Misc.MemAdmitMapEntriesMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemMapEntriesLow",
      summary = "Point at which to start conserving KVMap entries",
      key = "Misc.MemMapEntriesLow",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1024,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "KVMapGuardUncached",
      summary = "use guard pages around uncached kvmap mappings",
      key = "Misc.KVMapGuardUncached",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SerialPort",
      summary = "Which serial port (1 or 2) to use for logging, or 0 for neither.",
      key = "Misc.SerialPort",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SerialBaudRate",
      summary = "Baud rate",
      key = "Misc.SerialBaudRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 9600,
         max = 115200,
         defaultValue = 115200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "WatchdogBacktrace",
      summary = "Backtrace on every nth watchdog",
      key = "Misc.WatchdogBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BHTimeout",
      summary = "Timeout for bottom-half handlers in milliseconds",
      key = "Misc.BHTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BhTimeBound",
      summary = "Time bound on BH checking in us (microseconds).",
      key = "Misc.BhTimeBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 500000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IntTimeout",
      summary = "Timeout for interrupt handlers in milliseconds",
      key = "Misc.IntTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RunningVCpuLimit",
      summary = "The limit for the number of VCPUs",
      key = "Misc.RunningVCpuLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1024,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HordeEnabled",
      summary = "Enables horde mode",
      key = "Misc.HordeEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AckActual",
      summary = "Ack actual end",
      key = "Misc.AckActual",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NoWaitOnSocket",
      summary = "Don't wait on socket",
      key = "Misc.NoWaitOnSocket",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScreenSaverDelay",
      summary = "Delay in minutes before screensaver kicks in",
      key = "Misc.ScreenSaverDelay",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 60,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimEnabled",
      summary = "Enable CIM Service",
      key = "Misc.CimEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimOemProvidersEnabled",
      summary = "Enable OEM Providers",
      key = "Misc.CimOemProvidersEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimIHVProvidersEnabled",
      summary = "Enable IHV Providers",
      key = "Misc.CimIHVProvidersEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimWatchdogInterval",
      summary = "Seconds of delay between sfcbd poll",
      key = "Misc.CimWatchdogInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "FSSLightWeightProbe",
      summary = "Enable light-weight efficient probe of ESX supported datastores",
      key = "Misc.FSSLightWeightProbe",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ProcVerbose",
      summary = "option unused",
      key = "Misc.ProcVerbose",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPortRxQueueLen",
      summary = "Max length of the rx queue for virtual ports whose clients support queueing.",
      key = "Net.MaxPortRxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 500,
         defaultValue = 80,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxNetifRxQueueLen",
      summary = "Max length of the rx queue for the physical NICs.",
      key = "Net.MaxNetifRxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxNetifTxQueueLen",
      summary = "Max length of the tx queue for the physical NICs.",
      key = "Net.MaxNetifTxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "GuestTxCopyBreak",
      summary = "transmits smaller than this will be copied rather than mapped.",
      key = "Net.GuestTxCopyBreak",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = -1,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VmxnetTxCopySize",
      summary = "vmxnet tx &lt;= than this will be fully copied with no need for completion.",
      key = "Net.VmxnetTxCopySize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = -1,
         defaultValue = 256,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VmxnetWinUDPTxFullCopy",
      summary = "whether Windows vmxnet UDP tx is fullCopy.",
      key = "Net.VmxnetWinUDPTxFullCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseProc",
      summary = "whether or not to populate /proc/vmware/net. [0 = disabled, 1 = enabled]",
      key = "Net.UseProc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseLegacyProc",
      summary = "whether or not to populate legacy entries in /proc/vmware/net. [0 = disabled, 1 = enabled]",
      key = "Net.UseLegacyProc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NotifySwitch",
      summary = "Broadcasts an arp request on net handle enable. [0 = disabled, 1 = enabled]",
      key = "Net.NotifySwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetTxDontClusterSize",
      summary = "transmits smaller than this will not be subject to clustering/coalescing.",
      key = "Net.NetTxDontClusterSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8192,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetPktAllocTries",
      summary = "Number of tries for allocating pkt within the page.",
      key = "Net.NetPktAllocTries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceTxTimeout",
      summary = "set the coalesce timeout in micro-seconds.",
      key = "Net.CoalesceTxTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = -1,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceDefaultOn",
      summary = "whether dynamic coalescing is on by default. [0 = disabled by default, 1 = enabled by default]",
      key = "Net.CoalesceDefaultOn",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceLowTxMsRate",
      summary = "No tx coalescing calibration when the number of pkts tx per ms is lower than this number.",
      key = "Net.CoalesceLowTxMsRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 64,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceLowRxMsRate",
      summary = "No rx coalescing calibration when the number of pkts rx per ms is lower than this number.",
      key = "Net.CoalesceLowRxMsRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 64,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceHandlerPcpu",
      summary = "Pcpu that coalesce timeout handler runs on.",
      key = "Net.CoalesceHandlerPcpu",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceTxAlwaysPoll",
      summary = "Whether always poll Tx at coalesce timeout handler.",
      key = "Net.CoalesceTxAlwaysPoll",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "vmxnetBHNetPoll",
      summary = "Whether to poll for Tx in BH NetPoll.",
      key = "Net.vmxnetBHNetPoll",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "vmxnetThroughputWeight",
      summary = "How far to favor throughput in vmxnet behavior.",
      key = "Net.vmxnetThroughputWeight",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EtherswitchHashSize",
      summary = "number of ports on the switch x 2^N is the size of the hash table for looking up MACs.",
      key = "Net.EtherswitchHashSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NoLocalCSum",
      summary = "if set, don't bother checksumming local tx/rx frames.",
      key = "Net.NoLocalCSum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortSerializeInput",
      summary = "if enabled(1), input into port through appropriate calls are serialized to prevent out-of-order delivery.",
      key = "Net.PortSerializeInput",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortFlushIterLimit",
      summary = "when input is serialized, this bounds the number of times a thread flushes the deferred list.",
      key = "Net.PortFlushIterLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 127,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortFlushPktLimit",
      summary = "when input is serialized, this bounds the number of pkts a thread flushes from the deferred list.",
      key = "Net.PortFlushPktLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortTrackTxRace",
      summary = "if enabled(1), collect statistics on potential tx race between concurrent threads.",
      key = "Net.PortTrackTxRace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortKeepDetailedStats",
      summary = "if enabled(1), collect detailed statistics on port.",
      key = "Net.PortKeepDetailedStats",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortDisableTimeout",
      summary = "max timeout delay to wait for ports to complete I/O before disabling.",
      key = "Net.PortDisableTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipHeapSize",
      summary = "Initial size of the tcpip module heap in megabytes. (REQUIRES REBOOT!)",
      key = "Net.TcpipHeapSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 6,
         max = 30,
         defaultValue = 9,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipHeapMax",
      summary = "Max megabytes the tcpip module heap can grow to. (REQUIRES REBOOT!)",
      key = "Net.TcpipHeapMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 120,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPageInQueueLen",
      summary = "maximum number of pageing requests to queue for guest DMA.",
      key = "Net.MaxPageInQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxBeaconsAtOnce",
      summary = "maximum number of beacons to send in one beacon cycle.",
      key = "Net.MaxBeaconsAtOnce",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4096,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxBeaconVlans",
      summary = "maximum number of VLANs to probe with beacons.",
      key = "Net.MaxBeaconVlans",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4096,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipNoBcopyRx",
      summary = "Avoid bcopy in tcp rx.",
      key = "Net.TcpipNoBcopyRx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipCopySmallTx",
      summary = "Copy and tx complete small packets for tcp tx.",
      key = "Net.TcpipCopySmallTx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipLargeRx",
      summary = "Allow frames larger than mtu for tcp rx.",
      key = "Net.TcpipLargeRx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipMaxPktInFlight",
      summary = "Maximum zero copy mbuf packet in flight.",
      key = "Net.TcpipMaxPktInFlight",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipDelayedAck",
      summary = "Enable/Disable delayed ACKs.",
      key = "Net.TcpipDelayedAck",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LinkStatePollTimeout",
      summary = "Link State poll timer period in milliseconds.",
      key = "Net.LinkStatePollTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 90000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipUseIoat",
      summary = "Use IOAT chipset if present. (REQUIRES REBOOT!)",
      key = "Net.TcpipUseIoat",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipIoatAlwaysWakeup",
      summary = "Wakeup soreceive thread on every tcp packet (for IOAT only).",
      key = "Net.TcpipIoatAlwaysWakeup",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "E1000TxZeroCopy",
      summary = "Use tx zero copy for non-tso packets for e1000.",
      key = "Net.E1000TxZeroCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "E1000TxTsoZeroCopy",
      summary = "Use tx zero copy for tso packets for e1000.",
      key = "Net.E1000TxTsoZeroCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinEtherLen",
      summary = "Minimum size ethernet frame to transmit.",
      key = "Net.MinEtherLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1518,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPktRxListQueue",
      summary = "Maximum packet we can queue in rxList.",
      key = "Net.MaxPktRxListQueue",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 3500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxWorkBound",
      summary = "Maximum rx pkts processed in one NetBH invocation.",
      key = "Net.NetBHRxWorkBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 320,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxInputBound",
      summary = "Maximum rx pkts sent up an uplink at one go.",
      key = "Net.NetBHRxInputBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxStormThreshold",
      summary = "Declare Rx Storm after this number of consecutive rx pkt drops during queuing in NetBH rxList.",
      key = "Net.NetBHRxStormThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 320,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReversePathFwdCheck",
      summary = "Block the multicast/broadcast packets that come back from physical switches in a teamed environment.",
      key = "Net.ReversePathFwdCheck",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllowPromiscFilters",
      summary = "Block duplicate multicast/broadcast packet in a teamed environment when the virtual switch is set to Promiscuous mode.",
      key = "Net.AllowPromiscFilters",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Vmxnet2PinRxBuf",
      summary = "Pin RX buffers for vmxnet2 clients. (windows guest only)",
      key = "Net.Vmxnet2PinRxBuf",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TsoDumpPkt",
      summary = "detailed dump of every &lt;n&gt; pkts.",
      key = "Net.TsoDumpPkt",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPVersion",
      summary = "IGMP Version (2 or 3).",
      key = "Net.IGMPVersion",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 2,
         max = 3,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPQueries",
      summary = "Number of IGMP Queries to send during after VMotion/Teaming failover.",
      key = "Net.IGMPQueries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NcpLlcSap",
      summary = "beacon/color NCP messages created with this SAP (DSAP/SSAP)",
      key = "Net.NcpLlcSap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPRouterIP",
      summary = "Router IP Address for IGMP (generally not necessary to set this).",
      key = "Net.IGMPRouterIP",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "10.0.0.0",
         validCharacters = "10.0.0.0",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BalancePeriod",
      summary = "period in seconds, 0 to disable",
      key = "Mem.BalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 120,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SamplePeriod",
      summary = "period in seconds, 0 to disable",
      key = "Mem.SamplePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 180,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdleTax",
      summary = "idle memory tax rate",
      key = "Mem.IdleTax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 99,
         defaultValue = 75,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdleTaxType",
      summary = "idle tax type. 0=flat, 1=variable",
      key = "Mem.IdleTaxType",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SampleActivePctMin",
      summary = "lower bound for sampled active memory",
      key = "Mem.SampleActivePctMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareScanGHz",
      summary = "max page scan rate in MB/sec per GHz of host CPU, 0 to disable",
      key = "Mem.ShareScanGHz",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareScanTime",
      summary = "desired time in minutes to scan entire VM",
      key = "Mem.ShareScanTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 600,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareRateMax",
      summary = "per-VM upper limit on pshare scan/check rate in pages/sec. (0 to disable)",
      key = "Mem.ShareRateMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32768,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CtlMaxPercent",
      summary = "vmmemctl limit as percentage of VM max size",
      key = "Mem.CtlMaxPercent",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 75,
         defaultValue = 65,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocHighThreshold",
      summary = "Threshold (in MB) at which we start allocating memory above 4GB",
      key = "Mem.AllocHighThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 4096,
         defaultValue = 1500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocGuestLargePage",
      summary = "Enable large page backing of guest memory",
      key = "Mem.AllocGuestLargePage",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocUsePSharePool",
      summary = "Use pshare pool to allocate memory for shared pages",
      key = "Mem.AllocUsePSharePool",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocUseGuestPool",
      summary = "Use large page pool to allocate memory for guest pages",
      key = "Mem.AllocUseGuestPool",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AdmitHeapMin",
      summary = "free heap space required to power on VM, in KB",
      key = "Mem.AdmitHeapMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 256,
         max = 10240,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinFreePct",
      summary = "Minimum percent of memory that should be kept free",
      key = "Mem.MinFreePct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 6,
         max = 24,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareCOSBufSize",
      summary = "Specify number of MPNs to be used by COW P2M buffer",
      key = "Mem.ShareCOSBufSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 2,
         max = 8,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapIORetry",
      summary = "Number of retries for swap-in operation on I/O failures",
      key = "Mem.SwapIORetry",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TestOnAlloc",
      summary = "Check the newly allocated page for Memory Errors",
      key = "Mem.TestOnAlloc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimatePeriod",
      summary = "Sleep interval for pshare-est daemon world",
      key = "Mem.ShareEstimatePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 300000,
         defaultValue = 30000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimateProbe",
      summary = "Maximum per-VM page probes for pshare estimation",
      key = "Mem.ShareEstimateProbe",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 5000,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimateSamples",
      summary = "Minimum required per-VM page samples for pshare estimation",
      key = "Mem.ShareEstimateSamples",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 100,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "kernelResvPad",
      summary = "Extra padding (in MB) for MemSched's tracking of kernel memory usage",
      key = "Mem.kernelResvPad",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 128,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogLowMemoryStateUsage",
      summary = "Log memory usage of memclients during low memory state",
      key = "Mem.LogLowMemoryStateUsage",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogLowMemoryStateBT",
      summary = "Log back-trace of contexts that allocate MPNs during low memory state",
      key = "Mem.LogLowMemoryStateBT",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapDecayPct",
      summary = "Percentage of swap target to be proactively transferred to balloon target",
      key = "Mem.SwapDecayPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DesiredAllocEnable",
      summary = "Enable use of desired allocations when computing allocation targets",
      key = "Mem.DesiredAllocEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DesiredAllocPct",
      summary = "Percentage of consumed memory to be considered as the desired allocation target",
      key = "Mem.DesiredAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 200,
         defaultValue = 125,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BonusAllocPct",
      summary = "Percentage of group allocation to be distributed to children as bonus",
      key = "Mem.BonusAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapFilePersist",
      summary = "The swap file is not deleted when the VM powers off, 1 to enable",
      key = "Mem.SwapFilePersist",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapInBatchPages",
      summary = "Number of pages swapped in per batch during opportunistic prefaulting",
      key = "Mem.SwapInBatchPages",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 512,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapAsyncWritePages",
      summary = "Maximum allowed pending asynchronous swapout requests per VM",
      key = "Mem.SwapAsyncWritePages",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 16,
         max = 64,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HostLocalSwapDirEnabled",
      summary = "Enable use of host-local swap directory",
      key = "Mem.HostLocalSwapDirEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageAllocAllowance",
      summary = "Memory alloc allowance (in 4K pages) while usage is tracked via heartbeat or swap action post",
      key = "Mem.TrackUsageAllocAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 4096,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageSwapAllowance",
      summary = "Memory swap allowance (in 4K pages) while usage is tracked via heartbeat or swap action post",
      key = "Mem.TrackUsageSwapAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 4096,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageLPageAllowance",
      summary = "Memory large page alloc allowance (in 2M pages) while usage is tracked via heartbeat action post",
      key = "Mem.TrackUsageLPageAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageHeartbeatPeriod",
      summary = "Sleep interval in seconds for busmem heartbeat",
      key = "Mem.TrackUsageHeartbeatPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 300,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageHeartbeatEnable",
      summary = "Enable/disable MPN usage tracking via heartbeat monitor action (0 for disable)",
      key = "Mem.TrackUsageHeartbeatEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMOverheadGrowthLimit",
      summary = "Default limit (in MB) on VM overhead memory growth",
      key = "Mem.VMOverheadGrowthLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = -1,
         defaultValue = -1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HostLocalSwapDir",
      summary = "Host-local directory for VM swap files",
      key = "Mem.HostLocalSwapDir",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigratePeriod",
      summary = "milliseconds between opportunities to migrate across cpus",
      key = "Cpu.MigratePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CellMigratePeriod",
      summary = "milliseconds between opportunities to migrate across cells",
      key = "Cpu.CellMigratePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 60000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "WakeupMigrateIdle",
      summary = "migrate to idle package on wakeup, 0 to disable",
      key = "Cpu.WakeupMigrateIdle",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PcpuMigrateIdle",
      summary = "always migrate from remote pcpus when a core becomes idle, 0 to disable",
      key = "Cpu.PcpuMigrateIdle",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CreditAgePeriod",
      summary = "period in milliseconds",
      key = "Cpu.CreditAgePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 10000,
         defaultValue = 3000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BoundLagQuanta",
      summary = "number of global quanta before bound lag",
      key = "Cpu.BoundLagQuanta",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 100,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CacheStats",
      summary = "enable per-world cache data collection",
      key = "Cpu.CacheStats",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Quantum",
      summary = "quantum in milliseconds",
      key = "Cpu.Quantum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewPollUsec",
      summary = "interval between coscheduling skew checks, in usec",
      key = "Cpu.SkewPollUsec",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 5000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewInstanceThreshold",
      summary = "maximum individual skew between vcpus in usec, 0 to disable",
      key = "Cpu.SkewInstanceThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewCumulativeThreshold",
      summary = "maximum cumulative skew between vcpus in usec, 0 to disable",
      key = "Cpu.SkewCumulativeThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdlePackageRebalancePeriod",
      summary = "usec between chances to rebalance idle packages (0 to disable, 100000 max)",
      key = "Cpu.IdlePackageRebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 541,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IntraCoreMigrate",
      summary = " When to allow intra-core migrations [0:when inter-core migration allowed, 1:always]",
      key = "Cpu.IntraCoreMigrate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMotionMinAllocPct",
      summary = "Per-VM minimum CPU allocations (in %) for VMotion requirements",
      key = "Cpu.VMotionMinAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMAdmitCheckPerVcpuMin",
      summary = "Perform additional admission control check that per vcpu VM cpu min does not exceed the speed of a single physical  cpu. [0:dis",
      key = "Cpu.VMAdmitCheckPerVcpuMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoSchedIdleBalancePeriod",
      summary = "millisecs between opportunities to move co-scheduled vcpus to more idle cores and packages, 0 to disable",
      key = "Cpu.CoSchedIdleBalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalancePeriod",
      summary = "frequency of NUMA node rebalancing, in milliseconds",
      key = "Numa.RebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 60000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigImbalanceThreshold",
      summary = "minimum percent load imbalance between nodes to trigger migration",
      key = "Numa.MigImbalanceThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 200,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigThreshold",
      summary = "minimum percent load balance improvement to allow single migration/swap",
      key = "Numa.MigThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigThrashThreshold",
      summary = "maximum post-migration load imbalance, as percentage of pre-migration imbalance, to prevent thrashing",
      key = "Numa.MigThrashThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapLoadEnable",
      summary = "1 to enable VM swaps across nodes to balance CPU load, 0 to disable",
      key = "Numa.SwapLoadEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapLocalityEnable",
      summary = "1 to enable VM swaps across nodes to improve memory locality, 0 to disable",
      key = "Numa.SwapLocalityEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceEnable",
      summary = "1 to enable NUMA rebalancer, 0 to disable it",
      key = "Numa.RebalanceEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceCoresTotal",
      summary = "minimum number of total host cores required to enable NUMA rebalancer",
      key = "Numa.RebalanceCoresTotal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 32,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceCoresNode",
      summary = "minimum number of cores per node required to enable NUMA rebalancer",
      key = "Numa.RebalanceCoresNode",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 8,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MonMigEnable",
      summary = "1 to allow NUMASched monitor migrations, 0 to disallow",
      key = "Numa.MonMigEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AutoMemAffinity",
      summary = "1 to set mem affinity automatically based on cpu affinity, 0 to disable",
      key = "Numa.AutoMemAffinity",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageMigEnable",
      summary = "1 to permit NUMASched to manipulate page migration, 0 to disallow it",
      key = "Numa.PageMigEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PostMigUseActiveMetric",
      summary = "1 to use alternative migActive metric for post-migration imbalance prediction, 0 to use default migEntitlement metric",
      key = "Numa.PostMigUseActiveMetric",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragEnable",
      summary = "Enable large page defragmentation",
      key = "LPage.LPageDefragEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageMarkLowNodes",
      summary = "Enable marking of nodes with low large pages free",
      key = "LPage.LPageMarkLowNodes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragRateVM",
      summary = "Maximum number of lpage defrag attempts per second per VM",
      key = "LPage.LPageDefragRateVM",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragRateTotal",
      summary = "Maximum number of lpage defrag attempts per second ",
      key = "LPage.LPageDefragRateTotal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10240,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageAlwaysTryForNPT",
      summary = "Enable always try to alloc large page for NPT",
      key = "LPage.LPageAlwaysTryForNPT",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesNormal",
      summary = "shares for normal/default disk priority",
      key = "Disk.SharesNormal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesHigh",
      summary = "shares for high disk priority",
      key = "Disk.SharesHigh",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesLow",
      summary = "shares for low disk priority",
      key = "Disk.SharesLow",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BandwidthCap",
      summary = "cap on disk bandwidth (Kb/s) usage",
      key = "Disk.BandwidthCap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 2147483647,
         defaultValue = 2147483647,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ThroughputCap",
      summary = "cap on disk throughput (IO/S) usage",
      key = "Disk.ThroughputCap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 2147483647,
         defaultValue = 2147483647,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SectorMaxDiff",
      summary = "Distance in sectors at which disk BW sched affinity stops",
      key = "Disk.SectorMaxDiff",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2000000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQuantum",
      summary = "Number of consecutive requests from one World",
      key = "Disk.SchedQuantum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 64,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedNumReqOutstanding",
      summary = "Number of outstanding commands to a target with competing worlds",
      key = "Disk.SchedNumReqOutstanding",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQControlSeqReqs",
      summary = "Number of consecutive requests from a VM required to raise the outstanding commands to max",
      key = "Disk.SchedQControlSeqReqs",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2048,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQControlVMSwitches",
      summary = "Number of switches between commands issued by different VMs required to reduce outstanding commands to SchedNumReqOutstanding",
      key = "Disk.SchedQControlVMSwitches",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2048,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxLUN",
      summary = "Maximum LUN id that is scanned on a target",
      key = "Disk.MaxLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 256,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SupportSparseLUN",
      summary = "Support for sparse LUNs if set to one",
      key = "Disk.SupportSparseLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseReportLUN",
      summary = "Use the REPORT LUN command to speed up scanning for devices",
      key = "Disk.UseReportLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseDeviceReset",
      summary = "Use device reset (instead of bus reset) to reset a SCSI device",
      key = "Disk.UseDeviceReset",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseLunReset",
      summary = "Use LUN reset (instead of device/bus reset) to reset a SCSI device",
      key = "Disk.UseLunReset",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RetryUnitAttention",
      summary = "Retry all SCSI commands that return a unit attention error",
      key = "Disk.RetryUnitAttention",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetOnFailover",
      summary = "Issue a SCSI reset when failing over to an alternate HBA",
      key = "Disk.ResetOnFailover",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PathEvalTime",
      summary = "The number of seconds between FC path evaluations",
      key = "Disk.PathEvalTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 1500,
         defaultValue = 300,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxVCNotReadyTime",
      summary = "The number of seconds a VC path can report NOT READY status before being declared dead",
      key = "Disk.MaxVCNotReadyTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 15,
         max = 90,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxDS400NotReadyTime",
      summary = "The number of seconds a DS400 path can report IN TRANSITION before being declared dead",
      key = "Disk.MaxDS400NotReadyTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 15,
         max = 90,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableNaviReg",
      summary = "Enable automatic NaviAgent registration with CLARiiON and Invista (vmvisor only)",
      key = "Disk.EnableNaviReg",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DelayOnBusy",
      summary = "Delay in milliseconds for completion of commands with a BUSY status",
      key = "Disk.DelayOnBusy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 400,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetLatency",
      summary = "Delay in milliseconds between reset thread wake-ups",
      key = "Disk.ResetLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 600000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxResetLatency",
      summary = "Delay in milliseconds before logging warnings and spawning new reset worlds if a reset is overdue or taking too long",
      key = "Disk.MaxResetLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 600000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetPeriod",
      summary = "Delay in seconds between bus resets retries",
      key = "Disk.ResetPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 3600,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetMaxRetries",
      summary = "Max number of bus reset retries (0=infinite)",
      key = "Disk.ResetMaxRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadMin",
      summary = "Min number of reset handler threads",
      key = "Disk.ResetThreadMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadMax",
      summary = "Max number of reset handler threads",
      key = "Disk.ResetThreadMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadExpires",
      summary = "Life in seconds of an inactive reset handle thread",
      key = "Disk.ResetThreadExpires",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetOverdueLogPeriod",
      summary = "Delay in seconds between logs of overdue reset",
      key = "Disk.ResetOverdueLogPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SPBlksToSwitch",
      summary = "Number of blocks of I/O sent over a given path before a path switch (0=infinite)",
      key = "Disk.SPBlksToSwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000000,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SPCmdsToSwitch",
      summary = "Number of I/O commands sent over a given path before a path switch (0=infinite) ",
      key = "Disk.SPCmdsToSwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreventVMFSOverwrite",
      summary = "Prevent Console OS from overwriting VMFS partitions",
      key = "Disk.PreventVMFSOverwrite",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DumpMaxRetries",
      summary = "Max number of I/O retries during disk dump",
      key = "Disk.DumpMaxRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DiskMaxIOSize",
      summary = "Max Disk READ/WRITE I/O size before splitting (in KB)",
      key = "Disk.DiskMaxIOSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 32767,
         defaultValue = 32767,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaskLUNs",
      summary = "LUN's to mask from kernel. Format: &lt;adapter&gt;:&lt;target&gt;:&lt;comma separated LUN range list&gt;",
      key = "Disk.MaskLUNs",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SANDevicesWithAPFailover",
      summary = "SAN devices with Active/Passive Path Failover. Format: &lt;16 Character Device Id&gt;:&lt;16 Character Device Id&gt;:...",
      key = "Disk.SANDevicesWithAPFailover",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Enabled",
      summary = "Enable hot migration support",
      key = "Migrate.Enabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreCopyLeftMB",
      summary = "Maximum modified memory left over after pre-copy is done",
      key = "Migrate.PreCopyLeftMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreCopyMinProgressMB",
      summary = "Minimum reduction in modified memory after a pre-copy iteration",
      key = "Migrate.PreCopyMinProgressMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetTimeout",
      summary = "Timeout for migration network operations",
      key = "Migrate.NetTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 3600,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemChksum",
      summary = "Checksum VM's memory while migrating",
      key = "Migrate.MemChksum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TSMaster",
      summary = "Pseudo-synchronize clocks for migration to/from this machine",
      key = "Migrate.TSMaster",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInTimeout",
      summary = "Time in seconds to wait for page-in to finish",
      key = "Migrate.PageInTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 18000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInTimeoutResetOnProgress",
      summary = "Page-in progess will reset the page-in timeout",
      key = "Migrate.PageInTimeoutResetOnProgress",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInProgress",
      summary = "Time in seconds after which a page-in will be killed if there is no progress",
      key = "Migrate.PageInProgress",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 18000,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInBeforeResume",
      summary = "Wait for page-in to finish before resuming on the dest",
      key = "Migrate.PageInBeforeResume",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PassthroughLocking",
      summary = "Disable locking for scsi passthrough devices",
      key = "Scsi.PassthroughLocking",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ConflictRetries",
      summary = "Maximum number of retries when encountering reservation conflict.",
      key = "Scsi.ConflictRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 200,
         defaultValue = 80,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogMultiPath",
      summary = "Log path state changes",
      key = "Scsi.LogMultiPath",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogAborts",
      summary = "Log timing of aborted or reseted IOs",
      key = "Scsi.LogAborts",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PrintCmdErrors",
      summary = "Print the error to log on a SCSI command error.",
      key = "Scsi.PrintCmdErrors",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveTime",
      summary = "Maximum time (in msecs) a system-initiated reservation is normally held (debug only)",
      key = "Scsi.MaxReserveTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 50,
         max = 500,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveTotalTime",
      summary = "Maximum time (in msecs) a system-initiated reservation normally takes from issue to release (debug only)",
      key = "Scsi.MaxReserveTotalTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 50,
         max = 500,
         defaultValue = 250,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveBacktrace",
      summary = "Log a backtrace if caller exceeds SCSI_MAX_RESERVE_TIME or SCSI_MAX_RESERVE_TOTALTIME (debug only)",
      key = "Scsi.MaxReserveBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReserveBacktrace",
      summary = "Log a backtrace for all Reserve/Release pairs (debug only)",
      key = "Scsi.ReserveBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SCSITimeout_ScanTime",
      summary = "time (in ms) to sleep between checking for timed-out async IO",
      key = "Scsi.SCSITimeout_ScanTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 99999999,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SCSITimeout_ReabortTime",
      summary = "delay (in ms) after an abort due to timeout before the abort is re-issued",
      key = "Scsi.SCSITimeout_ReabortTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 99999999,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScanOnDriverLoad",
      summary = "Scan new SCSI buses on device driver load",
      key = "Scsi.ScanOnDriverLoad",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadMin",
      summary = "Min number of timeout task-mgmt handler threads",
      key = "Scsi.TimeoutTMThreadMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadMax",
      summary = "Max number of device task-mgmt handler threads",
      key = "Scsi.TimeoutTMThreadMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadExpires",
      summary = "Life in seconds of timeout task mgmt handler thread",
      key = "Scsi.TimeoutTMThreadExpires",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadRetry",
      summary = "Delay in milliseconds before retrying failed timeout taskmgmt",
      key = "Scsi.TimeoutTMThreadRetry",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 100000,
         defaultValue = 40000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadLatency",
      summary = "Delay in ms before waking up new task mgmt thread ",
      key = "Scsi.TimeoutTMThreadLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 600000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScsiRestartStalledQueueLatency",
      summary = "Delay in ms before restarting a stalled queue ",
      key = "Scsi.ScsiRestartStalledQueueLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 60000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CompareLUNNumber",
      summary = "Consider LUN number when determining LUN identity.",
      key = "Scsi.CompareLUNNumber",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScsiRescanAllHbas",
      summary = "During esxcfg-rescan, rescan all vmhbas at once rather than just a single vmhba",
      key = "Scsi.ScsiRescanAllHbas",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReaddirRetries",
      summary = "Maximum number of retries when reading entries from directories",
      key = "User.ReaddirRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 20,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CDROMSenseTimeout",
      summary = "Physical CDROM sense timeout (seconds)",
      key = "User.CDROMSenseTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PTEDisableNX",
      summary = "Disables the use of NX bit in user pagetable entries",
      key = "User.PTEDisableNX",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IndirectSend",
      summary = "Use NFS indirect send",
      key = "NFS.IndirectSend",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DiskFileLockUpdateFreq",
      summary = "Time (in seconds) between updates to a disk lock file [8-3600]",
      key = "NFS.DiskFileLockUpdateFreq",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 8,
         max = 3600,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockUpdateTimeout",
      summary = "Time (in seconds) before we abort an outstanding lock update",
      key = "NFS.LockUpdateTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockRenewMaxFailureNumber",
      summary = "Number of update failures before a disk file lock is declared stale",
      key = "NFS.LockRenewMaxFailureNumber",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockDisable",
      summary = "1 to disable NFS locking protocol",
      key = "NFS.LockDisable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatFrequency",
      summary = "Time in seconds between heartbeats",
      key = "NFS.HeartbeatFrequency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 86400,
         defaultValue = 9,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatTimeout",
      summary = "Time in seconds before we abort an outstanding hearbeat",
      key = "NFS.HeartbeatTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 3,
         max = 30,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatDelta",
      summary = "Time in seconds since the last successful update before we send a heartbeat",
      key = "NFS.HeartbeatDelta",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 3,
         max = 30,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatMaxFailures",
      summary = "Number of sequential failures before we mark a volume as down",
      key = "NFS.HeartbeatMaxFailures",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxVolumes",
      summary = "Maximum number of mounted NFS volumes",
      key = "NFS.MaxVolumes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 8,
         max = 32,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SendBufferSize",
      summary = "Default size of socket's send buffer in KB",
      key = "NFS.SendBufferSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 264,
         defaultValue = 264,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReceiveBufferSize",
      summary = "Default Size of socket's receive buffer in KB",
      key = "NFS.ReceiveBufferSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 264,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VolumeRemountFrequency",
      summary = "Time in seconds before attempting to remount a volume",
      key = "NFS.VolumeRemountFrequency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 3600,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UDPRetransmitDelay",
      summary = "Time in milliseconds retransmitting a UDP RPC",
      key = "NFS.UDPRetransmitDelay",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 2000,
         defaultValue = 700,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "OpenWithoutJournal",
      summary = "Open file system when out of space for journal allocation, allowing reads and no meta-data updates",
      key = "VMFS3.OpenWithoutJournal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxHeapSizeMB",
      summary = "Maximum size (in MB) to which the VMFS-3 heap is allowed to grow",
      key = "VMFS3.MaxHeapSizeMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 16,
         max = 128,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SoftMaxDirty",
      summary = "Flush immediately if this many buffers are dirty (percent)",
      key = "BufferCache.SoftMaxDirty",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HardMaxDirty",
      summary = "Block writers if this many buffers are dirty (percent)",
      key = "BufferCache.HardMaxDirty",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 95,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "FlushInterval",
      summary = "Flush periodically at this interval (msec)",
      key = "BufferCache.FlushInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 3600000,
         defaultValue = 30000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableResignature",
      summary = "Enable Volume Resignaturing",
      key = "LVM.EnableResignature",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DisallowSnapshotLun",
      summary = "Disallow access to snapshot LUN if resignaturing is off. This is ignored if resignaturing is on.",
      key = "LVM.DisallowSnapshotLun",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxHeapSizeMB",
      summary = "Maximum size (in MB) to which the COW heap is allowed to grow",
      key = "COW.MaxHeapSizeMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 192,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxDentryPerObj",
      summary = "Maximum directory entries cached per directory",
      key = "DirentryCache.MaxDentryPerObj",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = 30000,
         defaultValue = 2500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Annotations.WelcomeMessage",
      summary = "",
      key = "Annotations.WelcomeMessage",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.eax",
      summary = "CPUID override that may be applied to level 0 register eax; controlled by Config.Defaults.cpuidMask.mode.0.eax.",
      key = "Config.Defaults.cpuidMask.val.0.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.ebx",
      summary = "CPUID override that may be applied to level 0 register ebx; controlled by Config.Defaults.cpuidMask.mode.0.ebx.",
      key = "Config.Defaults.cpuidMask.val.0.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.ecx",
      summary = "CPUID override that may be applied to level 0 register ecx; controlled by Config.Defaults.cpuidMask.mode.0.ecx.",
      key = "Config.Defaults.cpuidMask.val.0.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.edx",
      summary = "CPUID override that may be applied to level 0 register edx; controlled by Config.Defaults.cpuidMask.mode.0.edx.",
      key = "Config.Defaults.cpuidMask.val.0.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.eax",
      summary = "CPUID override that may be applied to level 1 register eax; controlled by Config.Defaults.cpuidMask.mode.1.eax.",
      key = "Config.Defaults.cpuidMask.val.1.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.ebx",
      summary = "CPUID override that may be applied to level 1 register ebx; controlled by Config.Defaults.cpuidMask.mode.1.ebx.",
      key = "Config.Defaults.cpuidMask.val.1.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.ecx",
      summary = "CPUID override that may be applied to level 1 register ecx; controlled by Config.Defaults.cpuidMask.mode.1.ecx.",
      key = "Config.Defaults.cpuidMask.val.1.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.edx",
      summary = "CPUID override that may be applied to level 1 register edx; controlled by Config.Defaults.cpuidMask.mode.1.edx.",
      key = "Config.Defaults.cpuidMask.val.1.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.eax",
      summary = "CPUID override that may be applied to level 80000000 register eax; controlled by Config.Defaults.cpuidMask.mode.80000000.eax.",
      key = "Config.Defaults.cpuidMask.val.80000000.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.ebx",
      summary = "CPUID override that may be applied to level 80000000 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000000.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000000.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.ecx",
      summary = "CPUID override that may be applied to level 80000000 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000000.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000000.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.edx",
      summary = "CPUID override that may be applied to level 80000000 register edx; controlled by Config.Defaults.cpuidMask.mode.80000000.edx.",
      key = "Config.Defaults.cpuidMask.val.80000000.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.eax",
      summary = "CPUID override that may be applied to level 80000001 register eax; controlled by Config.Defaults.cpuidMask.mode.80000001.eax.",
      key = "Config.Defaults.cpuidMask.val.80000001.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.ebx",
      summary = "CPUID override that may be applied to level 80000001 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000001.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000001.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.ecx",
      summary = "CPUID override that may be applied to level 80000001 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000001.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000001.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.edx",
      summary = "CPUID override that may be applied to level 80000001 register edx; controlled by Config.Defaults.cpuidMask.mode.80000001.edx.",
      key = "Config.Defaults.cpuidMask.val.80000001.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.eax",
      summary = "CPUID override that may be applied to level 80000008 register eax; controlled by Config.Defaults.cpuidMask.mode.80000008.eax.",
      key = "Config.Defaults.cpuidMask.val.80000008.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.ebx",
      summary = "CPUID override that may be applied to level 80000008 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000008.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000008.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.ecx",
      summary = "CPUID override that may be applied to level 80000008 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000008.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000008.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.edx",
      summary = "CPUID override that may be applied to level 80000008 register edx; controlled by Config.Defaults.cpuidMask.mode.80000008.edx.",
      key = "Config.Defaults.cpuidMask.val.80000008.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.eax",
      summary = "CPUID override that may be applied to level 8000000A register eax; controlled by Config.Defaults.cpuidMask.mode.8000000A.eax.",
      key = "Config.Defaults.cpuidMask.val.8000000A.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.ebx",
      summary = "CPUID override that may be applied to level 8000000A register ebx; controlled by Config.Defaults.cpuidMask.mode.8000000A.ebx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.ecx",
      summary = "CPUID override that may be applied to level 8000000A register ecx; controlled by Config.Defaults.cpuidMask.mode.8000000A.ecx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.edx",
      summary = "CPUID override that may be applied to level 8000000A register edx; controlled by Config.Defaults.cpuidMask.mode.8000000A.edx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "security.host.ruissl",
      summary = "Require SSL to be used when communicating with the host over port 902.",
      key = "Config.Defaults.security.host.ruissl",
      optionType = (vim.option.BoolOption) {
         dynamicType = "",
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "guest.commands.sharedPolicyRefCount",
      summary = "Reference count to enable guest operations.",
      key = "Config.GlobalSettings.guest.commands.sharedPolicyRefCount",
      optionType = (vim.option.IntOption) {
         dynamicType = "",
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.ConfiguredScratchLocation",
      summary = "The directory configured to be used for scratch space.Changes will take effect on next reboot.",
      key = "ScratchConfig.ConfiguredScratchLocation",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.ConfiguredSwapState",
      summary = "Whether userwold swap is configured to be enabledChanges will take effect on next reboot.",
      key = "ScratchConfig.ConfiguredSwapState",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = false,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.CurrentScratchLocation",
      summary = "The directory currently being used for scratch space",
      key = "ScratchConfig.CurrentScratchLocation",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = true,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.CurrentSwapState",
      summary = "Whether userworld swap is currently enabled",
      key = "ScratchConfig.CurrentSwapState",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = true,
         supported = false,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Local.DatastorePath",
      summary = "Datastore path of file to which local syslogd data is written.",
      key = "Syslog.Local.DatastorePath",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Remote.Hostname",
      summary = "Hostname to which syslog data will be forwarded.  Disabled on null.",
      key = "Syslog.Remote.Hostname",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Remote.Port",
      summary = "Port to which syslog data will be forwarded.",
      key = "Syslog.Remote.Port",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 65535,
         defaultValue = 514,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.ACPI",
      summary = "Initialize ACPI CA.",
      key = "VMkernel.Boot.ACPI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.acpiDbgLevel",
      summary = "ACPI debug level",
      key = "VMkernel.Boot.acpiDbgLevel",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.assumeCommonBusClock",
      summary = "Assume all NUMA nodes run off a common, synchronous bus clock (normally autodetected).",
      key = "VMkernel.Boot.assumeCommonBusClock",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.assumePerNodeBusClock",
      summary = "Assume each NUMA node has a separate bus clock (normally autodetected).",
      key = "VMkernel.Boot.assumePerNodeBusClock",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.baudRate",
      summary = "Baud rate to run the serial port at.",
      key = "VMkernel.Boot.baudRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 115200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      summary = "Buddy physical mem debug info switch.",
      key = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.busSpeedMayVary",
      summary = "Allow different bus clock speeds, even within a single NUMA node or SMP system.",
      key = "VMkernel.Boot.busSpeedMayVary",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.busSpeedMayVaryPerNode",
      summary = "Allow substantially different bus clock speeds in different NUMA nodes.",
      key = "VMkernel.Boot.busSpeedMayVaryPerNode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.checkCPUIDLimit",
      summary = "Refuse to run on CPUID limited cpus.",
      key = "VMkernel.Boot.checkCPUIDLimit",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.clockMultiplierMayVary",
      summary = "Allow different CPU clock multipliers, even within a single NUMA node or SMP system.",
      key = "VMkernel.Boot.clockMultiplierMayVary",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      summary = "Allow different CPU clock multipliers in different NUMA nodes.",
      key = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.coresPerPkg",
      summary = "Number of cores per package that vmkernel should use",
      key = "VMkernel.Boot.coresPerPkg",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.correctBSPMTRRMasks",
      summary = "Correct BSP Variable MTRR masks to match the processor physical address bit support",
      key = "VMkernel.Boot.correctBSPMTRRMasks",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.cpuCellSize",
      summary = "Requested cpu scheduler cell size.",
      key = "VMkernel.Boot.cpuCellSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.debugBreak",
      summary = "Break into debugger during vmkernel initialization.",
      key = "VMkernel.Boot.debugBreak",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.dumpDiag",
      summary = "Dump diagnostics information.",
      key = "VMkernel.Boot.dumpDiag",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.executePOST",
      summary = "Run POST tests.",
      key = "VMkernel.Boot.executePOST",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fakeNUMAnodes",
      summary = "Fake # NUMA nodes on UMA systems.",
      key = "VMkernel.Boot.fakeNUMAnodes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fastHzEstimate",
      summary = "Use ACPI PM timer for frequency estimation at boot.",
      key = "VMkernel.Boot.fastHzEstimate",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.forceCRS",
      summary = "Always use IRQ from _CRS",
      key = "VMkernel.Boot.forceCRS",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fsCheck",
      summary = "Run filesystem checks on system partitions.",
      key = "VMkernel.Boot.fsCheck",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.hyperthreading",
      summary = "Enable hyperthreading if available.",
      key = "VMkernel.Boot.hyperthreading",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.ioapic",
      summary = "Use IOAPICs.",
      key = "VMkernel.Boot.ioapic",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logOnScreen",
      summary = "Display vmkernel log on screen.",
      key = "VMkernel.Boot.logOnScreen",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logSynchronous",
      summary = "Print log messages to screen and/or serial port synchronously.",
      key = "VMkernel.Boot.logSynchronous",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logicalApicId",
      summary = "Use logical not physical APIC IDs.",
      key = "VMkernel.Boot.logicalApicId",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.maxPCPUS",
      summary = "Number of PCPUs vmkernel should use.",
      key = "VMkernel.Boot.maxPCPUS",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memCheckEveryWord",
      summary = "Check every single word when checking mem.",
      key = "VMkernel.Boot.memCheckEveryWord",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      summary = "Maximum physical memory (in MB) recognized by kernel",
      key = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 262144,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memmapStressHighBitMPNs",
      summary = "Test &gt; 64GB physical RAM support by ignoring 4GB - 64GB range",
      key = "VMkernel.Boot.memmapStressHighBitMPNs",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.mpsIntRouting",
      summary = "Use MPS interrupt routing.",
      key = "VMkernel.Boot.mpsIntRouting",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netESX2LegacyMode",
      summary = "ESX2 Legacy networking config compatability.",
      key = "VMkernel.Boot.netESX2LegacyMode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      summary = "Maximum number of pkt buffers queued in each PCPU slab cache.",
      key = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNetqueueEnabled",
      summary = "Enable/Disable NetQueue support.",
      key = "VMkernel.Boot.netNetqueueEnabled",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNumGPBuffers",
      summary = "Number of general purpose buffers to allocate up front.",
      key = "VMkernel.Boot.netNumGPBuffers",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNumPortsets",
      summary = "Maximum number of portsets.",
      key = "VMkernel.Boot.netNumPortsets",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPanicBadDevOpen",
      summary = "panic if device has a bad open handler.",
      key = "VMkernel.Boot.netPanicBadDevOpen",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktBufUseSlab",
      summary = "Whether to allocate PktBufDescriptor from the pkt slab allocator.",
      key = "VMkernel.Boot.netPktBufUseSlab",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktHeapMaxSize",
      summary = "Maximum size in MB of the pkt buffer heap (advisory only).",
      key = "VMkernel.Boot.netPktHeapMaxSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktHeapMinSize",
      summary = "Minimum size in MB of the pkt buffer heap (advisory only).",
      key = "VMkernel.Boot.netPktHeapMinSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktNumSlabSizes",
      summary = "Number of different slab sizes for the allocator.",
      key = "VMkernel.Boot.netPktNumSlabSizes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netUseMemcpyNt",
      summary = "Enable/Disable non temporal memcpy in packet copy.",
      key = "VMkernel.Boot.netUseMemcpyNt",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netUseProc",
      summary = "Enable/Disable /proc nodes.",
      key = "VMkernel.Boot.netUseProc",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.oem",
      summary = "Enable OEM extensions.",
      key = "VMkernel.Boot.oem",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.overrideSerialPortAddr",
      summary = "UART I/O address",
      key = "VMkernel.Boot.overrideSerialPortAddr",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.pageSharing",
      summary = "Enable page sharing.",
      key = "VMkernel.Boot.pageSharing",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.panicOnVmkernelAbort",
      summary = "Panic if vmkernel aborts initialization.",
      key = "VMkernel.Boot.panicOnVmkernelAbort",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.realNMI",
      summary = "Use real NMI for LINT1.",
      key = "VMkernel.Boot.realNMI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.serialPort",
      summary = "0 = disable, 1 = COM1, 2 = COM2.",
      key = "VMkernel.Boot.serialPort",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.storageHeapMaxSize",
      summary = "Maximum size in bytes of the main storage heap",
      key = "VMkernel.Boot.storageHeapMaxSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.storageHeapMinSize",
      summary = "Minimum size in bytes of the main storage heap",
      key = "VMkernel.Boot.storageHeapMinSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.techSupportMode",
      summary = "Allow VMware Tech Support Mode access.",
      key = "VMkernel.Boot.techSupportMode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableACPI",
      summary = "Enable ACPI PM timer as system reference timer.",
      key = "VMkernel.Boot.timerEnableACPI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableHPET",
      summary = "Enable HPET as system reference timer.",
      key = "VMkernel.Boot.timerEnableHPET",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableMPMC",
      summary = "Enable Cyclone MPMC timer as system reference timer.",
      key = "VMkernel.Boot.timerEnableMPMC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableTSC",
      summary = "Enable TSC as system reference timer.",
      key = "VMkernel.Boot.timerEnableTSC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerForceTSC",
      summary = "Always use TSC as system reference timer.",
      key = "VMkernel.Boot.timerForceTSC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.usbBoot",
      summary = "Require USB boot if bootFS.",
      key = "VMkernel.Boot.usbBoot",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.useNUMAInfo",
      summary = "enable/disable NUMA-ness",
      key = "VMkernel.Boot.useNUMAInfo",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.useTSCForCPUHz",
      summary = "On systems where TSC and CPU frequencies are the same, determines whether to use TSC or the non-halted clock cycles MSR to determine CPU frequency.",
      key = "VMkernel.Boot.useTSCForCPUHz",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.uwSwap",
      summary = "Enable Userworld Swap.",
      key = "VMkernel.Boot.uwSwap",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.vmkKeyboard",
      summary = "Enable vmkernel keyboard driver.",
      key = "VMkernel.Boot.vmkKeyboard",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.vmkTerminals",
      summary = "Enable switching to vmkernel terminals.",
      key = "VMkernel.Boot.vmkTerminals",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.xapicAMDDetect",
      summary = "Detect xapic on opteron",
      key = "VMkernel.Boot.xapicAMDDetect",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.xapicForce",
      summary = "Force APIC ID to 8 bits",
      key = "VMkernel.Boot.xapicForce",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   }
 ]

[[Category: Vimsh]]</text>
    <sha1>79245432e18c390355e43a101eb453460f6d86d0</sha1>
  </revision>
  <revision>
    <id>557</id>
    <parentid>556</parentid>
    <timestamp>2008-12-31T18:03:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added stop to example output as it looks like not everything is on the results page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155815" xml:space="preserve">==== vimsh hostsvc/advopt/options ====
Usage: Get the list of all supported options.
==== example output ====
Attached is some example output from a pristine ESX3.5i host.

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/advopt/options
 (vim.option.OptionDef) [
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RoutingPolicy",
      summary = "policy for interrupt routing, 1 for idle-routing, 2 for greedy routing, 0 to disable moving IRQs",
      key = "Irq.RoutingPolicy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BestVcpuRouting",
      summary = "",
      key = "Irq.BestVcpuRouting",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IRQRebalancePeriod",
      summary = "time in ms between attempts to rebalance interrupts",
      key = "Irq.IRQRebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 20000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IRQMaxLoadPct",
      summary = "maximum percentage of a cpu's resources that should be devoted to interrupts",
      key = "Irq.IRQMaxLoadPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 70,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogToFile",
      summary = "Send vmkernel log messages to /var/log/vmkernel",
      key = "Misc.LogToFile",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogToSerial",
      summary = "Send vmkernel log messages to the serial port",
      key = "Misc.LogToSerial",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogWldPrefix",
      summary = "Including running world on every log statement",
      key = "Misc.LogWldPrefix",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinimalPanic",
      summary = "Don't attempt to coredump after PSODing",
      key = "Misc.MinimalPanic",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BlueScreenTimeout",
      summary = "timeout in seconds, 0 is no timeout",
      key = "Misc.BlueScreenTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 65535,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatTimeout",
      summary = "Timeout in seconds, for sending NMI to the locked CPU",
      key = "Misc.HeartbeatTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatInterval",
      summary = "Interval in msec to check CPU lockups",
      key = "Misc.HeartbeatInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 86400000,
         defaultValue = 10000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatPanicTimeout",
      summary = "Interval in seconds after which to panic if no heartbeats received",
      key = "Misc.HeartbeatPanicTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatAnyPcpuPanic",
      summary = "Should we panic on any cpu lockups? (default we panic only for COS)",
      key = "Misc.HeartbeatAnyPcpuPanic",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MCEMonitorInterval",
      summary = "Interval[1 - 0x0xffffffff secs] to check Machine Check Errors",
      key = "Misc.MCEMonitorInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = -1,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DebugMemEnable",
      summary = "Enable memory debugging, 0 to disable",
      key = "Misc.DebugMemEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DebugBuddyEnable",
      summary = "Enable buddy debugging, 0 to disable",
      key = "Misc.DebugBuddyEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableHighDMA",
      summary = "Enable DMA above 4GB",
      key = "Misc.EnableHighDMA",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMinHardPeriod",
      summary = "Minimum hard timer interrupt period in microseconds",
      key = "Misc.TimerMinHardPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMaxHardPeriod",
      summary = "Maximum hard timer interrupt period in microseconds",
      key = "Misc.TimerMaxHardPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMinGuestPeriod",
      summary = "Minimum period for guest timer callbacks in microseconds",
      key = "Misc.TimerMinGuestPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 1000000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemAdmitMapEntriesMin",
      summary = "free KVMap entries required to power on VM",
      key = "Misc.MemAdmitMapEntriesMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemMapEntriesLow",
      summary = "Point at which to start conserving KVMap entries",
      key = "Misc.MemMapEntriesLow",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1024,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "KVMapGuardUncached",
      summary = "use guard pages around uncached kvmap mappings",
      key = "Misc.KVMapGuardUncached",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SerialPort",
      summary = "Which serial port (1 or 2) to use for logging, or 0 for neither.",
      key = "Misc.SerialPort",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SerialBaudRate",
      summary = "Baud rate",
      key = "Misc.SerialBaudRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 9600,
         max = 115200,
         defaultValue = 115200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "WatchdogBacktrace",
      summary = "Backtrace on every nth watchdog",
      key = "Misc.WatchdogBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BHTimeout",
      summary = "Timeout for bottom-half handlers in milliseconds",
      key = "Misc.BHTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BhTimeBound",
      summary = "Time bound on BH checking in us (microseconds).",
      key = "Misc.BhTimeBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 500000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IntTimeout",
      summary = "Timeout for interrupt handlers in milliseconds",
      key = "Misc.IntTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RunningVCpuLimit",
      summary = "The limit for the number of VCPUs",
      key = "Misc.RunningVCpuLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1024,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HordeEnabled",
      summary = "Enables horde mode",
      key = "Misc.HordeEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AckActual",
      summary = "Ack actual end",
      key = "Misc.AckActual",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NoWaitOnSocket",
      summary = "Don't wait on socket",
      key = "Misc.NoWaitOnSocket",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScreenSaverDelay",
      summary = "Delay in minutes before screensaver kicks in",
      key = "Misc.ScreenSaverDelay",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 60,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimEnabled",
      summary = "Enable CIM Service",
      key = "Misc.CimEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimOemProvidersEnabled",
      summary = "Enable OEM Providers",
      key = "Misc.CimOemProvidersEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimIHVProvidersEnabled",
      summary = "Enable IHV Providers",
      key = "Misc.CimIHVProvidersEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimWatchdogInterval",
      summary = "Seconds of delay between sfcbd poll",
      key = "Misc.CimWatchdogInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "FSSLightWeightProbe",
      summary = "Enable light-weight efficient probe of ESX supported datastores",
      key = "Misc.FSSLightWeightProbe",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ProcVerbose",
      summary = "option unused",
      key = "Misc.ProcVerbose",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPortRxQueueLen",
      summary = "Max length of the rx queue for virtual ports whose clients support queueing.",
      key = "Net.MaxPortRxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 500,
         defaultValue = 80,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxNetifRxQueueLen",
      summary = "Max length of the rx queue for the physical NICs.",
      key = "Net.MaxNetifRxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxNetifTxQueueLen",
      summary = "Max length of the tx queue for the physical NICs.",
      key = "Net.MaxNetifTxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "GuestTxCopyBreak",
      summary = "transmits smaller than this will be copied rather than mapped.",
      key = "Net.GuestTxCopyBreak",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = -1,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VmxnetTxCopySize",
      summary = "vmxnet tx &lt;= than this will be fully copied with no need for completion.",
      key = "Net.VmxnetTxCopySize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = -1,
         defaultValue = 256,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VmxnetWinUDPTxFullCopy",
      summary = "whether Windows vmxnet UDP tx is fullCopy.",
      key = "Net.VmxnetWinUDPTxFullCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseProc",
      summary = "whether or not to populate /proc/vmware/net. [0 = disabled, 1 = enabled]",
      key = "Net.UseProc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseLegacyProc",
      summary = "whether or not to populate legacy entries in /proc/vmware/net. [0 = disabled, 1 = enabled]",
      key = "Net.UseLegacyProc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NotifySwitch",
      summary = "Broadcasts an arp request on net handle enable. [0 = disabled, 1 = enabled]",
      key = "Net.NotifySwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetTxDontClusterSize",
      summary = "transmits smaller than this will not be subject to clustering/coalescing.",
      key = "Net.NetTxDontClusterSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8192,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetPktAllocTries",
      summary = "Number of tries for allocating pkt within the page.",
      key = "Net.NetPktAllocTries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceTxTimeout",
      summary = "set the coalesce timeout in micro-seconds.",
      key = "Net.CoalesceTxTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = -1,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceDefaultOn",
      summary = "whether dynamic coalescing is on by default. [0 = disabled by default, 1 = enabled by default]",
      key = "Net.CoalesceDefaultOn",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceLowTxMsRate",
      summary = "No tx coalescing calibration when the number of pkts tx per ms is lower than this number.",
      key = "Net.CoalesceLowTxMsRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 64,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceLowRxMsRate",
      summary = "No rx coalescing calibration when the number of pkts rx per ms is lower than this number.",
      key = "Net.CoalesceLowRxMsRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 64,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceHandlerPcpu",
      summary = "Pcpu that coalesce timeout handler runs on.",
      key = "Net.CoalesceHandlerPcpu",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceTxAlwaysPoll",
      summary = "Whether always poll Tx at coalesce timeout handler.",
      key = "Net.CoalesceTxAlwaysPoll",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "vmxnetBHNetPoll",
      summary = "Whether to poll for Tx in BH NetPoll.",
      key = "Net.vmxnetBHNetPoll",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "vmxnetThroughputWeight",
      summary = "How far to favor throughput in vmxnet behavior.",
      key = "Net.vmxnetThroughputWeight",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EtherswitchHashSize",
      summary = "number of ports on the switch x 2^N is the size of the hash table for looking up MACs.",
      key = "Net.EtherswitchHashSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NoLocalCSum",
      summary = "if set, don't bother checksumming local tx/rx frames.",
      key = "Net.NoLocalCSum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortSerializeInput",
      summary = "if enabled(1), input into port through appropriate calls are serialized to prevent out-of-order delivery.",
      key = "Net.PortSerializeInput",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortFlushIterLimit",
      summary = "when input is serialized, this bounds the number of times a thread flushes the deferred list.",
      key = "Net.PortFlushIterLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 127,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortFlushPktLimit",
      summary = "when input is serialized, this bounds the number of pkts a thread flushes from the deferred list.",
      key = "Net.PortFlushPktLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortTrackTxRace",
      summary = "if enabled(1), collect statistics on potential tx race between concurrent threads.",
      key = "Net.PortTrackTxRace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortKeepDetailedStats",
      summary = "if enabled(1), collect detailed statistics on port.",
      key = "Net.PortKeepDetailedStats",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortDisableTimeout",
      summary = "max timeout delay to wait for ports to complete I/O before disabling.",
      key = "Net.PortDisableTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipHeapSize",
      summary = "Initial size of the tcpip module heap in megabytes. (REQUIRES REBOOT!)",
      key = "Net.TcpipHeapSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 6,
         max = 30,
         defaultValue = 9,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipHeapMax",
      summary = "Max megabytes the tcpip module heap can grow to. (REQUIRES REBOOT!)",
      key = "Net.TcpipHeapMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 120,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPageInQueueLen",
      summary = "maximum number of pageing requests to queue for guest DMA.",
      key = "Net.MaxPageInQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxBeaconsAtOnce",
      summary = "maximum number of beacons to send in one beacon cycle.",
      key = "Net.MaxBeaconsAtOnce",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4096,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxBeaconVlans",
      summary = "maximum number of VLANs to probe with beacons.",
      key = "Net.MaxBeaconVlans",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4096,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipNoBcopyRx",
      summary = "Avoid bcopy in tcp rx.",
      key = "Net.TcpipNoBcopyRx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipCopySmallTx",
      summary = "Copy and tx complete small packets for tcp tx.",
      key = "Net.TcpipCopySmallTx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipLargeRx",
      summary = "Allow frames larger than mtu for tcp rx.",
      key = "Net.TcpipLargeRx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipMaxPktInFlight",
      summary = "Maximum zero copy mbuf packet in flight.",
      key = "Net.TcpipMaxPktInFlight",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipDelayedAck",
      summary = "Enable/Disable delayed ACKs.",
      key = "Net.TcpipDelayedAck",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LinkStatePollTimeout",
      summary = "Link State poll timer period in milliseconds.",
      key = "Net.LinkStatePollTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 90000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipUseIoat",
      summary = "Use IOAT chipset if present. (REQUIRES REBOOT!)",
      key = "Net.TcpipUseIoat",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipIoatAlwaysWakeup",
      summary = "Wakeup soreceive thread on every tcp packet (for IOAT only).",
      key = "Net.TcpipIoatAlwaysWakeup",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "E1000TxZeroCopy",
      summary = "Use tx zero copy for non-tso packets for e1000.",
      key = "Net.E1000TxZeroCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "E1000TxTsoZeroCopy",
      summary = "Use tx zero copy for tso packets for e1000.",
      key = "Net.E1000TxTsoZeroCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinEtherLen",
      summary = "Minimum size ethernet frame to transmit.",
      key = "Net.MinEtherLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1518,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPktRxListQueue",
      summary = "Maximum packet we can queue in rxList.",
      key = "Net.MaxPktRxListQueue",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 3500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxWorkBound",
      summary = "Maximum rx pkts processed in one NetBH invocation.",
      key = "Net.NetBHRxWorkBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 320,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxInputBound",
      summary = "Maximum rx pkts sent up an uplink at one go.",
      key = "Net.NetBHRxInputBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxStormThreshold",
      summary = "Declare Rx Storm after this number of consecutive rx pkt drops during queuing in NetBH rxList.",
      key = "Net.NetBHRxStormThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 320,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReversePathFwdCheck",
      summary = "Block the multicast/broadcast packets that come back from physical switches in a teamed environment.",
      key = "Net.ReversePathFwdCheck",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllowPromiscFilters",
      summary = "Block duplicate multicast/broadcast packet in a teamed environment when the virtual switch is set to Promiscuous mode.",
      key = "Net.AllowPromiscFilters",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Vmxnet2PinRxBuf",
      summary = "Pin RX buffers for vmxnet2 clients. (windows guest only)",
      key = "Net.Vmxnet2PinRxBuf",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TsoDumpPkt",
      summary = "detailed dump of every &lt;n&gt; pkts.",
      key = "Net.TsoDumpPkt",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPVersion",
      summary = "IGMP Version (2 or 3).",
      key = "Net.IGMPVersion",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 2,
         max = 3,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPQueries",
      summary = "Number of IGMP Queries to send during after VMotion/Teaming failover.",
      key = "Net.IGMPQueries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NcpLlcSap",
      summary = "beacon/color NCP messages created with this SAP (DSAP/SSAP)",
      key = "Net.NcpLlcSap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPRouterIP",
      summary = "Router IP Address for IGMP (generally not necessary to set this).",
      key = "Net.IGMPRouterIP",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "10.0.0.0",
         validCharacters = "10.0.0.0",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BalancePeriod",
      summary = "period in seconds, 0 to disable",
      key = "Mem.BalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 120,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SamplePeriod",
      summary = "period in seconds, 0 to disable",
      key = "Mem.SamplePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 180,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdleTax",
      summary = "idle memory tax rate",
      key = "Mem.IdleTax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 99,
         defaultValue = 75,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdleTaxType",
      summary = "idle tax type. 0=flat, 1=variable",
      key = "Mem.IdleTaxType",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SampleActivePctMin",
      summary = "lower bound for sampled active memory",
      key = "Mem.SampleActivePctMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareScanGHz",
      summary = "max page scan rate in MB/sec per GHz of host CPU, 0 to disable",
      key = "Mem.ShareScanGHz",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareScanTime",
      summary = "desired time in minutes to scan entire VM",
      key = "Mem.ShareScanTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 600,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareRateMax",
      summary = "per-VM upper limit on pshare scan/check rate in pages/sec. (0 to disable)",
      key = "Mem.ShareRateMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32768,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CtlMaxPercent",
      summary = "vmmemctl limit as percentage of VM max size",
      key = "Mem.CtlMaxPercent",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 75,
         defaultValue = 65,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocHighThreshold",
      summary = "Threshold (in MB) at which we start allocating memory above 4GB",
      key = "Mem.AllocHighThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 4096,
         defaultValue = 1500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocGuestLargePage",
      summary = "Enable large page backing of guest memory",
      key = "Mem.AllocGuestLargePage",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocUsePSharePool",
      summary = "Use pshare pool to allocate memory for shared pages",
      key = "Mem.AllocUsePSharePool",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocUseGuestPool",
      summary = "Use large page pool to allocate memory for guest pages",
      key = "Mem.AllocUseGuestPool",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AdmitHeapMin",
      summary = "free heap space required to power on VM, in KB",
      key = "Mem.AdmitHeapMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 256,
         max = 10240,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinFreePct",
      summary = "Minimum percent of memory that should be kept free",
      key = "Mem.MinFreePct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 6,
         max = 24,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareCOSBufSize",
      summary = "Specify number of MPNs to be used by COW P2M buffer",
      key = "Mem.ShareCOSBufSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 2,
         max = 8,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapIORetry",
      summary = "Number of retries for swap-in operation on I/O failures",
      key = "Mem.SwapIORetry",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TestOnAlloc",
      summary = "Check the newly allocated page for Memory Errors",
      key = "Mem.TestOnAlloc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimatePeriod",
      summary = "Sleep interval for pshare-est daemon world",
      key = "Mem.ShareEstimatePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 300000,
         defaultValue = 30000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimateProbe",
      summary = "Maximum per-VM page probes for pshare estimation",
      key = "Mem.ShareEstimateProbe",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 5000,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimateSamples",
      summary = "Minimum required per-VM page samples for pshare estimation",
      key = "Mem.ShareEstimateSamples",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 100,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "kernelResvPad",
      summary = "Extra padding (in MB) for MemSched's tracking of kernel memory usage",
      key = "Mem.kernelResvPad",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 128,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogLowMemoryStateUsage",
      summary = "Log memory usage of memclients during low memory state",
      key = "Mem.LogLowMemoryStateUsage",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogLowMemoryStateBT",
      summary = "Log back-trace of contexts that allocate MPNs during low memory state",
      key = "Mem.LogLowMemoryStateBT",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapDecayPct",
      summary = "Percentage of swap target to be proactively transferred to balloon target",
      key = "Mem.SwapDecayPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DesiredAllocEnable",
      summary = "Enable use of desired allocations when computing allocation targets",
      key = "Mem.DesiredAllocEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DesiredAllocPct",
      summary = "Percentage of consumed memory to be considered as the desired allocation target",
      key = "Mem.DesiredAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 200,
         defaultValue = 125,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BonusAllocPct",
      summary = "Percentage of group allocation to be distributed to children as bonus",
      key = "Mem.BonusAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapFilePersist",
      summary = "The swap file is not deleted when the VM powers off, 1 to enable",
      key = "Mem.SwapFilePersist",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapInBatchPages",
      summary = "Number of pages swapped in per batch during opportunistic prefaulting",
      key = "Mem.SwapInBatchPages",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 512,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapAsyncWritePages",
      summary = "Maximum allowed pending asynchronous swapout requests per VM",
      key = "Mem.SwapAsyncWritePages",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 16,
         max = 64,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HostLocalSwapDirEnabled",
      summary = "Enable use of host-local swap directory",
      key = "Mem.HostLocalSwapDirEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageAllocAllowance",
      summary = "Memory alloc allowance (in 4K pages) while usage is tracked via heartbeat or swap action post",
      key = "Mem.TrackUsageAllocAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 4096,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageSwapAllowance",
      summary = "Memory swap allowance (in 4K pages) while usage is tracked via heartbeat or swap action post",
      key = "Mem.TrackUsageSwapAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 4096,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageLPageAllowance",
      summary = "Memory large page alloc allowance (in 2M pages) while usage is tracked via heartbeat action post",
      key = "Mem.TrackUsageLPageAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageHeartbeatPeriod",
      summary = "Sleep interval in seconds for busmem heartbeat",
      key = "Mem.TrackUsageHeartbeatPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 300,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageHeartbeatEnable",
      summary = "Enable/disable MPN usage tracking via heartbeat monitor action (0 for disable)",
      key = "Mem.TrackUsageHeartbeatEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMOverheadGrowthLimit",
      summary = "Default limit (in MB) on VM overhead memory growth",
      key = "Mem.VMOverheadGrowthLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = -1,
         defaultValue = -1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HostLocalSwapDir",
      summary = "Host-local directory for VM swap files",
      key = "Mem.HostLocalSwapDir",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigratePeriod",
      summary = "milliseconds between opportunities to migrate across cpus",
      key = "Cpu.MigratePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CellMigratePeriod",
      summary = "milliseconds between opportunities to migrate across cells",
      key = "Cpu.CellMigratePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 60000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "WakeupMigrateIdle",
      summary = "migrate to idle package on wakeup, 0 to disable",
      key = "Cpu.WakeupMigrateIdle",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PcpuMigrateIdle",
      summary = "always migrate from remote pcpus when a core becomes idle, 0 to disable",
      key = "Cpu.PcpuMigrateIdle",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CreditAgePeriod",
      summary = "period in milliseconds",
      key = "Cpu.CreditAgePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 10000,
         defaultValue = 3000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BoundLagQuanta",
      summary = "number of global quanta before bound lag",
      key = "Cpu.BoundLagQuanta",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 100,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CacheStats",
      summary = "enable per-world cache data collection",
      key = "Cpu.CacheStats",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Quantum",
      summary = "quantum in milliseconds",
      key = "Cpu.Quantum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewPollUsec",
      summary = "interval between coscheduling skew checks, in usec",
      key = "Cpu.SkewPollUsec",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 5000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewInstanceThreshold",
      summary = "maximum individual skew between vcpus in usec, 0 to disable",
      key = "Cpu.SkewInstanceThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewCumulativeThreshold",
      summary = "maximum cumulative skew between vcpus in usec, 0 to disable",
      key = "Cpu.SkewCumulativeThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdlePackageRebalancePeriod",
      summary = "usec between chances to rebalance idle packages (0 to disable, 100000 max)",
      key = "Cpu.IdlePackageRebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 541,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IntraCoreMigrate",
      summary = " When to allow intra-core migrations [0:when inter-core migration allowed, 1:always]",
      key = "Cpu.IntraCoreMigrate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMotionMinAllocPct",
      summary = "Per-VM minimum CPU allocations (in %) for VMotion requirements",
      key = "Cpu.VMotionMinAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMAdmitCheckPerVcpuMin",
      summary = "Perform additional admission control check that per vcpu VM cpu min does not exceed the speed of a single physical  cpu. [0:dis",
      key = "Cpu.VMAdmitCheckPerVcpuMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoSchedIdleBalancePeriod",
      summary = "millisecs between opportunities to move co-scheduled vcpus to more idle cores and packages, 0 to disable",
      key = "Cpu.CoSchedIdleBalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalancePeriod",
      summary = "frequency of NUMA node rebalancing, in milliseconds",
      key = "Numa.RebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 60000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigImbalanceThreshold",
      summary = "minimum percent load imbalance between nodes to trigger migration",
      key = "Numa.MigImbalanceThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 200,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigThreshold",
      summary = "minimum percent load balance improvement to allow single migration/swap",
      key = "Numa.MigThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigThrashThreshold",
      summary = "maximum post-migration load imbalance, as percentage of pre-migration imbalance, to prevent thrashing",
      key = "Numa.MigThrashThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapLoadEnable",
      summary = "1 to enable VM swaps across nodes to balance CPU load, 0 to disable",
      key = "Numa.SwapLoadEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapLocalityEnable",
      summary = "1 to enable VM swaps across nodes to improve memory locality, 0 to disable",
      key = "Numa.SwapLocalityEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceEnable",
      summary = "1 to enable NUMA rebalancer, 0 to disable it",
      key = "Numa.RebalanceEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceCoresTotal",
      summary = "minimum number of total host cores required to enable NUMA rebalancer",
      key = "Numa.RebalanceCoresTotal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 32,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceCoresNode",
      summary = "minimum number of cores per node required to enable NUMA rebalancer",
      key = "Numa.RebalanceCoresNode",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 8,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MonMigEnable",
      summary = "1 to allow NUMASched monitor migrations, 0 to disallow",
      key = "Numa.MonMigEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AutoMemAffinity",
      summary = "1 to set mem affinity automatically based on cpu affinity, 0 to disable",
      key = "Numa.AutoMemAffinity",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageMigEnable",
      summary = "1 to permit NUMASched to manipulate page migration, 0 to disallow it",
      key = "Numa.PageMigEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PostMigUseActiveMetric",
      summary = "1 to use alternative migActive metric for post-migration imbalance prediction, 0 to use default migEntitlement metric",
      key = "Numa.PostMigUseActiveMetric",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragEnable",
      summary = "Enable large page defragmentation",
      key = "LPage.LPageDefragEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageMarkLowNodes",
      summary = "Enable marking of nodes with low large pages free",
      key = "LPage.LPageMarkLowNodes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragRateVM",
      summary = "Maximum number of lpage defrag attempts per second per VM",
      key = "LPage.LPageDefragRateVM",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragRateTotal",
      summary = "Maximum number of lpage defrag attempts per second ",
      key = "LPage.LPageDefragRateTotal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10240,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageAlwaysTryForNPT",
      summary = "Enable always try to alloc large page for NPT",
      key = "LPage.LPageAlwaysTryForNPT",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesNormal",
      summary = "shares for normal/default disk priority",
      key = "Disk.SharesNormal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesHigh",
      summary = "shares for high disk priority",
      key = "Disk.SharesHigh",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesLow",
      summary = "shares for low disk priority",
      key = "Disk.SharesLow",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BandwidthCap",
      summary = "cap on disk bandwidth (Kb/s) usage",
      key = "Disk.BandwidthCap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 2147483647,
         defaultValue = 2147483647,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ThroughputCap",
      summary = "cap on disk throughput (IO/S) usage",
      key = "Disk.ThroughputCap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 2147483647,
         defaultValue = 2147483647,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SectorMaxDiff",
      summary = "Distance in sectors at which disk BW sched affinity stops",
      key = "Disk.SectorMaxDiff",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2000000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQuantum",
      summary = "Number of consecutive requests from one World",
      key = "Disk.SchedQuantum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 64,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedNumReqOutstanding",
      summary = "Number of outstanding commands to a target with competing worlds",
      key = "Disk.SchedNumReqOutstanding",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQControlSeqReqs",
      summary = "Number of consecutive requests from a VM required to raise the outstanding commands to max",
      key = "Disk.SchedQControlSeqReqs",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2048,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQControlVMSwitches",
      summary = "Number of switches between commands issued by different VMs required to reduce outstanding commands to SchedNumReqOutstanding",
      key = "Disk.SchedQControlVMSwitches",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2048,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxLUN",
      summary = "Maximum LUN id that is scanned on a target",
      key = "Disk.MaxLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 256,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SupportSparseLUN",
      summary = "Support for sparse LUNs if set to one",
      key = "Disk.SupportSparseLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseReportLUN",
      summary = "Use the REPORT LUN command to speed up scanning for devices",
      key = "Disk.UseReportLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseDeviceReset",
      summary = "Use device reset (instead of bus reset) to reset a SCSI device",
      key = "Disk.UseDeviceReset",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseLunReset",
      summary = "Use LUN reset (instead of device/bus reset) to reset a SCSI device",
      key = "Disk.UseLunReset",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RetryUnitAttention",
      summary = "Retry all SCSI commands that return a unit attention error",
      key = "Disk.RetryUnitAttention",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetOnFailover",
      summary = "Issue a SCSI reset when failing over to an alternate HBA",
      key = "Disk.ResetOnFailover",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PathEvalTime",
      summary = "The number of seconds between FC path evaluations",
      key = "Disk.PathEvalTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 1500,
         defaultValue = 300,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxVCNotReadyTime",
      summary = "The number of seconds a VC path can report NOT READY status before being declared dead",
      key = "Disk.MaxVCNotReadyTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 15,
         max = 90,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxDS400NotReadyTime",
      summary = "The number of seconds a DS400 path can report IN TRANSITION before being declared dead",
      key = "Disk.MaxDS400NotReadyTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 15,
         max = 90,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableNaviReg",
      summary = "Enable automatic NaviAgent registration with CLARiiON and Invista (vmvisor only)",
      key = "Disk.EnableNaviReg",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DelayOnBusy",
      summary = "Delay in milliseconds for completion of commands with a BUSY status",
      key = "Disk.DelayOnBusy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 400,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetLatency",
      summary = "Delay in milliseconds between reset thread wake-ups",
      key = "Disk.ResetLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 600000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxResetLatency",
      summary = "Delay in milliseconds before logging warnings and spawning new reset worlds if a reset is overdue or taking too long",
      key = "Disk.MaxResetLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 600000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetPeriod",
      summary = "Delay in seconds between bus resets retries",
      key = "Disk.ResetPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 3600,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetMaxRetries",
      summary = "Max number of bus reset retries (0=infinite)",
      key = "Disk.ResetMaxRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadMin",
      summary = "Min number of reset handler threads",
      key = "Disk.ResetThreadMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadMax",
      summary = "Max number of reset handler threads",
      key = "Disk.ResetThreadMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadExpires",
      summary = "Life in seconds of an inactive reset handle thread",
      key = "Disk.ResetThreadExpires",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetOverdueLogPeriod",
      summary = "Delay in seconds between logs of overdue reset",
      key = "Disk.ResetOverdueLogPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SPBlksToSwitch",
      summary = "Number of blocks of I/O sent over a given path before a path switch (0=infinite)",
      key = "Disk.SPBlksToSwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000000,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SPCmdsToSwitch",
      summary = "Number of I/O commands sent over a given path before a path switch (0=infinite) ",
      key = "Disk.SPCmdsToSwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreventVMFSOverwrite",
      summary = "Prevent Console OS from overwriting VMFS partitions",
      key = "Disk.PreventVMFSOverwrite",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DumpMaxRetries",
      summary = "Max number of I/O retries during disk dump",
      key = "Disk.DumpMaxRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DiskMaxIOSize",
      summary = "Max Disk READ/WRITE I/O size before splitting (in KB)",
      key = "Disk.DiskMaxIOSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 32767,
         defaultValue = 32767,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaskLUNs",
      summary = "LUN's to mask from kernel. Format: &lt;adapter&gt;:&lt;target&gt;:&lt;comma separated LUN range list&gt;",
      key = "Disk.MaskLUNs",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SANDevicesWithAPFailover",
      summary = "SAN devices with Active/Passive Path Failover. Format: &lt;16 Character Device Id&gt;:&lt;16 Character Device Id&gt;:...",
      key = "Disk.SANDevicesWithAPFailover",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Enabled",
      summary = "Enable hot migration support",
      key = "Migrate.Enabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreCopyLeftMB",
      summary = "Maximum modified memory left over after pre-copy is done",
      key = "Migrate.PreCopyLeftMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreCopyMinProgressMB",
      summary = "Minimum reduction in modified memory after a pre-copy iteration",
      key = "Migrate.PreCopyMinProgressMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetTimeout",
      summary = "Timeout for migration network operations",
      key = "Migrate.NetTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 3600,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemChksum",
      summary = "Checksum VM's memory while migrating",
      key = "Migrate.MemChksum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TSMaster",
      summary = "Pseudo-synchronize clocks for migration to/from this machine",
      key = "Migrate.TSMaster",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInTimeout",
      summary = "Time in seconds to wait for page-in to finish",
      key = "Migrate.PageInTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 18000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInTimeoutResetOnProgress",
      summary = "Page-in progess will reset the page-in timeout",
      key = "Migrate.PageInTimeoutResetOnProgress",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInProgress",
      summary = "Time in seconds after which a page-in will be killed if there is no progress",
      key = "Migrate.PageInProgress",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 18000,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInBeforeResume",
      summary = "Wait for page-in to finish before resuming on the dest",
      key = "Migrate.PageInBeforeResume",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PassthroughLocking",
      summary = "Disable locking for scsi passthrough devices",
      key = "Scsi.PassthroughLocking",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ConflictRetries",
      summary = "Maximum number of retries when encountering reservation conflict.",
      key = "Scsi.ConflictRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 200,
         defaultValue = 80,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogMultiPath",
      summary = "Log path state changes",
      key = "Scsi.LogMultiPath",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogAborts",
      summary = "Log timing of aborted or reseted IOs",
      key = "Scsi.LogAborts",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PrintCmdErrors",
      summary = "Print the error to log on a SCSI command error.",
      key = "Scsi.PrintCmdErrors",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveTime",
      summary = "Maximum time (in msecs) a system-initiated reservation is normally held (debug only)",
      key = "Scsi.MaxReserveTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 50,
         max = 500,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveTotalTime",
      summary = "Maximum time (in msecs) a system-initiated reservation normally takes from issue to release (debug only)",
      key = "Scsi.MaxReserveTotalTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 50,
         max = 500,
         defaultValue = 250,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveBacktrace",
      summary = "Log a backtrace if caller exceeds SCSI_MAX_RESERVE_TIME or SCSI_MAX_RESERVE_TOTALTIME (debug only)",
      key = "Scsi.MaxReserveBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReserveBacktrace",
      summary = "Log a backtrace for all Reserve/Release pairs (debug only)",
      key = "Scsi.ReserveBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SCSITimeout_ScanTime",
      summary = "time (in ms) to sleep between checking for timed-out async IO",
      key = "Scsi.SCSITimeout_ScanTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 99999999,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SCSITimeout_ReabortTime",
      summary = "delay (in ms) after an abort due to timeout before the abort is re-issued",
      key = "Scsi.SCSITimeout_ReabortTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 99999999,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScanOnDriverLoad",
      summary = "Scan new SCSI buses on device driver load",
      key = "Scsi.ScanOnDriverLoad",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadMin",
      summary = "Min number of timeout task-mgmt handler threads",
      key = "Scsi.TimeoutTMThreadMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadMax",
      summary = "Max number of device task-mgmt handler threads",
      key = "Scsi.TimeoutTMThreadMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadExpires",
      summary = "Life in seconds of timeout task mgmt handler thread",
      key = "Scsi.TimeoutTMThreadExpires",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadRetry",
      summary = "Delay in milliseconds before retrying failed timeout taskmgmt",
      key = "Scsi.TimeoutTMThreadRetry",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 100000,
         defaultValue = 40000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadLatency",
      summary = "Delay in ms before waking up new task mgmt thread ",
      key = "Scsi.TimeoutTMThreadLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 600000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScsiRestartStalledQueueLatency",
      summary = "Delay in ms before restarting a stalled queue ",
      key = "Scsi.ScsiRestartStalledQueueLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 60000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CompareLUNNumber",
      summary = "Consider LUN number when determining LUN identity.",
      key = "Scsi.CompareLUNNumber",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScsiRescanAllHbas",
      summary = "During esxcfg-rescan, rescan all vmhbas at once rather than just a single vmhba",
      key = "Scsi.ScsiRescanAllHbas",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReaddirRetries",
      summary = "Maximum number of retries when reading entries from directories",
      key = "User.ReaddirRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 20,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CDROMSenseTimeout",
      summary = "Physical CDROM sense timeout (seconds)",
      key = "User.CDROMSenseTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PTEDisableNX",
      summary = "Disables the use of NX bit in user pagetable entries",
      key = "User.PTEDisableNX",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IndirectSend",
      summary = "Use NFS indirect send",
      key = "NFS.IndirectSend",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DiskFileLockUpdateFreq",
      summary = "Time (in seconds) between updates to a disk lock file [8-3600]",
      key = "NFS.DiskFileLockUpdateFreq",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 8,
         max = 3600,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockUpdateTimeout",
      summary = "Time (in seconds) before we abort an outstanding lock update",
      key = "NFS.LockUpdateTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockRenewMaxFailureNumber",
      summary = "Number of update failures before a disk file lock is declared stale",
      key = "NFS.LockRenewMaxFailureNumber",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockDisable",
      summary = "1 to disable NFS locking protocol",
      key = "NFS.LockDisable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatFrequency",
      summary = "Time in seconds between heartbeats",
      key = "NFS.HeartbeatFrequency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 86400,
         defaultValue = 9,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatTimeout",
      summary = "Time in seconds before we abort an outstanding hearbeat",
      key = "NFS.HeartbeatTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 3,
         max = 30,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatDelta",
      summary = "Time in seconds since the last successful update before we send a heartbeat",
      key = "NFS.HeartbeatDelta",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 3,
         max = 30,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatMaxFailures",
      summary = "Number of sequential failures before we mark a volume as down",
      key = "NFS.HeartbeatMaxFailures",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxVolumes",
      summary = "Maximum number of mounted NFS volumes",
      key = "NFS.MaxVolumes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 8,
         max = 32,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SendBufferSize",
      summary = "Default size of socket's send buffer in KB",
      key = "NFS.SendBufferSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 264,
         defaultValue = 264,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReceiveBufferSize",
      summary = "Default Size of socket's receive buffer in KB",
      key = "NFS.ReceiveBufferSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 264,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VolumeRemountFrequency",
      summary = "Time in seconds before attempting to remount a volume",
      key = "NFS.VolumeRemountFrequency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 3600,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UDPRetransmitDelay",
      summary = "Time in milliseconds retransmitting a UDP RPC",
      key = "NFS.UDPRetransmitDelay",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 2000,
         defaultValue = 700,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "OpenWithoutJournal",
      summary = "Open file system when out of space for journal allocation, allowing reads and no meta-data updates",
      key = "VMFS3.OpenWithoutJournal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxHeapSizeMB",
      summary = "Maximum size (in MB) to which the VMFS-3 heap is allowed to grow",
      key = "VMFS3.MaxHeapSizeMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 16,
         max = 128,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SoftMaxDirty",
      summary = "Flush immediately if this many buffers are dirty (percent)",
      key = "BufferCache.SoftMaxDirty",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HardMaxDirty",
      summary = "Block writers if this many buffers are dirty (percent)",
      key = "BufferCache.HardMaxDirty",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 95,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "FlushInterval",
      summary = "Flush periodically at this interval (msec)",
      key = "BufferCache.FlushInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 3600000,
         defaultValue = 30000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableResignature",
      summary = "Enable Volume Resignaturing",
      key = "LVM.EnableResignature",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DisallowSnapshotLun",
      summary = "Disallow access to snapshot LUN if resignaturing is off. This is ignored if resignaturing is on.",
      key = "LVM.DisallowSnapshotLun",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxHeapSizeMB",
      summary = "Maximum size (in MB) to which the COW heap is allowed to grow",
      key = "COW.MaxHeapSizeMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 192,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxDentryPerObj",
      summary = "Maximum directory entries cached per directory",
      key = "DirentryCache.MaxDentryPerObj",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = 30000,
         defaultValue = 2500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Annotations.WelcomeMessage",
      summary = "",
      key = "Annotations.WelcomeMessage",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.eax",
      summary = "CPUID override that may be applied to level 0 register eax; controlled by Config.Defaults.cpuidMask.mode.0.eax.",
      key = "Config.Defaults.cpuidMask.val.0.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.ebx",
      summary = "CPUID override that may be applied to level 0 register ebx; controlled by Config.Defaults.cpuidMask.mode.0.ebx.",
      key = "Config.Defaults.cpuidMask.val.0.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.ecx",
      summary = "CPUID override that may be applied to level 0 register ecx; controlled by Config.Defaults.cpuidMask.mode.0.ecx.",
      key = "Config.Defaults.cpuidMask.val.0.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.edx",
      summary = "CPUID override that may be applied to level 0 register edx; controlled by Config.Defaults.cpuidMask.mode.0.edx.",
      key = "Config.Defaults.cpuidMask.val.0.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.eax",
      summary = "CPUID override that may be applied to level 1 register eax; controlled by Config.Defaults.cpuidMask.mode.1.eax.",
      key = "Config.Defaults.cpuidMask.val.1.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.ebx",
      summary = "CPUID override that may be applied to level 1 register ebx; controlled by Config.Defaults.cpuidMask.mode.1.ebx.",
      key = "Config.Defaults.cpuidMask.val.1.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.ecx",
      summary = "CPUID override that may be applied to level 1 register ecx; controlled by Config.Defaults.cpuidMask.mode.1.ecx.",
      key = "Config.Defaults.cpuidMask.val.1.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.edx",
      summary = "CPUID override that may be applied to level 1 register edx; controlled by Config.Defaults.cpuidMask.mode.1.edx.",
      key = "Config.Defaults.cpuidMask.val.1.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.eax",
      summary = "CPUID override that may be applied to level 80000000 register eax; controlled by Config.Defaults.cpuidMask.mode.80000000.eax.",
      key = "Config.Defaults.cpuidMask.val.80000000.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.ebx",
      summary = "CPUID override that may be applied to level 80000000 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000000.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000000.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.ecx",
      summary = "CPUID override that may be applied to level 80000000 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000000.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000000.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.edx",
      summary = "CPUID override that may be applied to level 80000000 register edx; controlled by Config.Defaults.cpuidMask.mode.80000000.edx.",
      key = "Config.Defaults.cpuidMask.val.80000000.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.eax",
      summary = "CPUID override that may be applied to level 80000001 register eax; controlled by Config.Defaults.cpuidMask.mode.80000001.eax.",
      key = "Config.Defaults.cpuidMask.val.80000001.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.ebx",
      summary = "CPUID override that may be applied to level 80000001 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000001.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000001.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.ecx",
      summary = "CPUID override that may be applied to level 80000001 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000001.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000001.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.edx",
      summary = "CPUID override that may be applied to level 80000001 register edx; controlled by Config.Defaults.cpuidMask.mode.80000001.edx.",
      key = "Config.Defaults.cpuidMask.val.80000001.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.eax",
      summary = "CPUID override that may be applied to level 80000008 register eax; controlled by Config.Defaults.cpuidMask.mode.80000008.eax.",
      key = "Config.Defaults.cpuidMask.val.80000008.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.ebx",
      summary = "CPUID override that may be applied to level 80000008 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000008.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000008.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.ecx",
      summary = "CPUID override that may be applied to level 80000008 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000008.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000008.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.edx",
      summary = "CPUID override that may be applied to level 80000008 register edx; controlled by Config.Defaults.cpuidMask.mode.80000008.edx.",
      key = "Config.Defaults.cpuidMask.val.80000008.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.eax",
      summary = "CPUID override that may be applied to level 8000000A register eax; controlled by Config.Defaults.cpuidMask.mode.8000000A.eax.",
      key = "Config.Defaults.cpuidMask.val.8000000A.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.ebx",
      summary = "CPUID override that may be applied to level 8000000A register ebx; controlled by Config.Defaults.cpuidMask.mode.8000000A.ebx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.ecx",
      summary = "CPUID override that may be applied to level 8000000A register ecx; controlled by Config.Defaults.cpuidMask.mode.8000000A.ecx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.edx",
      summary = "CPUID override that may be applied to level 8000000A register edx; controlled by Config.Defaults.cpuidMask.mode.8000000A.edx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "security.host.ruissl",
      summary = "Require SSL to be used when communicating with the host over port 902.",
      key = "Config.Defaults.security.host.ruissl",
      optionType = (vim.option.BoolOption) {
         dynamicType = "",
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "guest.commands.sharedPolicyRefCount",
      summary = "Reference count to enable guest operations.",
      key = "Config.GlobalSettings.guest.commands.sharedPolicyRefCount",
      optionType = (vim.option.IntOption) {
         dynamicType = "",
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.ConfiguredScratchLocation",
      summary = "The directory configured to be used for scratch space.Changes will take effect on next reboot.",
      key = "ScratchConfig.ConfiguredScratchLocation",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.ConfiguredSwapState",
      summary = "Whether userwold swap is configured to be enabledChanges will take effect on next reboot.",
      key = "ScratchConfig.ConfiguredSwapState",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = false,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.CurrentScratchLocation",
      summary = "The directory currently being used for scratch space",
      key = "ScratchConfig.CurrentScratchLocation",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = true,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.CurrentSwapState",
      summary = "Whether userworld swap is currently enabled",
      key = "ScratchConfig.CurrentSwapState",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = true,
         supported = false,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Local.DatastorePath",
      summary = "Datastore path of file to which local syslogd data is written.",
      key = "Syslog.Local.DatastorePath",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Remote.Hostname",
      summary = "Hostname to which syslog data will be forwarded.  Disabled on null.",
      key = "Syslog.Remote.Hostname",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Remote.Port",
      summary = "Port to which syslog data will be forwarded.",
      key = "Syslog.Remote.Port",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 65535,
         defaultValue = 514,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.ACPI",
      summary = "Initialize ACPI CA.",
      key = "VMkernel.Boot.ACPI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.acpiDbgLevel",
      summary = "ACPI debug level",
      key = "VMkernel.Boot.acpiDbgLevel",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.assumeCommonBusClock",
      summary = "Assume all NUMA nodes run off a common, synchronous bus clock (normally autodetected).",
      key = "VMkernel.Boot.assumeCommonBusClock",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.assumePerNodeBusClock",
      summary = "Assume each NUMA node has a separate bus clock (normally autodetected).",
      key = "VMkernel.Boot.assumePerNodeBusClock",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.baudRate",
      summary = "Baud rate to run the serial port at.",
      key = "VMkernel.Boot.baudRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 115200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      summary = "Buddy physical mem debug info switch.",
      key = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.busSpeedMayVary",
      summary = "Allow different bus clock speeds, even within a single NUMA node or SMP system.",
      key = "VMkernel.Boot.busSpeedMayVary",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.busSpeedMayVaryPerNode",
      summary = "Allow substantially different bus clock speeds in different NUMA nodes.",
      key = "VMkernel.Boot.busSpeedMayVaryPerNode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.checkCPUIDLimit",
      summary = "Refuse to run on CPUID limited cpus.",
      key = "VMkernel.Boot.checkCPUIDLimit",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.clockMultiplierMayVary",
      summary = "Allow different CPU clock multipliers, even within a single NUMA node or SMP system.",
      key = "VMkernel.Boot.clockMultiplierMayVary",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      summary = "Allow different CPU clock multipliers in different NUMA nodes.",
      key = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.coresPerPkg",
      summary = "Number of cores per package that vmkernel should use",
      key = "VMkernel.Boot.coresPerPkg",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.correctBSPMTRRMasks",
      summary = "Correct BSP Variable MTRR masks to match the processor physical address bit support",
      key = "VMkernel.Boot.correctBSPMTRRMasks",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.cpuCellSize",
      summary = "Requested cpu scheduler cell size.",
      key = "VMkernel.Boot.cpuCellSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.debugBreak",
      summary = "Break into debugger during vmkernel initialization.",
      key = "VMkernel.Boot.debugBreak",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.dumpDiag",
      summary = "Dump diagnostics information.",
      key = "VMkernel.Boot.dumpDiag",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.executePOST",
      summary = "Run POST tests.",
      key = "VMkernel.Boot.executePOST",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fakeNUMAnodes",
      summary = "Fake # NUMA nodes on UMA systems.",
      key = "VMkernel.Boot.fakeNUMAnodes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fastHzEstimate",
      summary = "Use ACPI PM timer for frequency estimation at boot.",
      key = "VMkernel.Boot.fastHzEstimate",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.forceCRS",
      summary = "Always use IRQ from _CRS",
      key = "VMkernel.Boot.forceCRS",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fsCheck",
      summary = "Run filesystem checks on system partitions.",
      key = "VMkernel.Boot.fsCheck",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.hyperthreading",
      summary = "Enable hyperthreading if available.",
      key = "VMkernel.Boot.hyperthreading",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.ioapic",
      summary = "Use IOAPICs.",
      key = "VMkernel.Boot.ioapic",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logOnScreen",
      summary = "Display vmkernel log on screen.",
      key = "VMkernel.Boot.logOnScreen",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logSynchronous",
      summary = "Print log messages to screen and/or serial port synchronously.",
      key = "VMkernel.Boot.logSynchronous",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logicalApicId",
      summary = "Use logical not physical APIC IDs.",
      key = "VMkernel.Boot.logicalApicId",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.maxPCPUS",
      summary = "Number of PCPUs vmkernel should use.",
      key = "VMkernel.Boot.maxPCPUS",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memCheckEveryWord",
      summary = "Check every single word when checking mem.",
      key = "VMkernel.Boot.memCheckEveryWord",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      summary = "Maximum physical memory (in MB) recognized by kernel",
      key = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 262144,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memmapStressHighBitMPNs",
      summary = "Test &gt; 64GB physical RAM support by ignoring 4GB - 64GB range",
      key = "VMkernel.Boot.memmapStressHighBitMPNs",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.mpsIntRouting",
      summary = "Use MPS interrupt routing.",
      key = "VMkernel.Boot.mpsIntRouting",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netESX2LegacyMode",
      summary = "ESX2 Legacy networking config compatability.",
      key = "VMkernel.Boot.netESX2LegacyMode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      summary = "Maximum number of pkt buffers queued in each PCPU slab cache.",
      key = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNetqueueEnabled",
      summary = "Enable/Disable NetQueue support.",
      key = "VMkernel.Boot.netNetqueueEnabled",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNumGPBuffers",
      summary = "Number of general purpose buffers to allocate up front.",
      key = "VMkernel.Boot.netNumGPBuffers",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNumPortsets",
      summary = "Maximum number of portsets.",
      key = "VMkernel.Boot.netNumPortsets",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPanicBadDevOpen",
      summary = "panic if device has a bad open handler.",
      key = "VMkernel.Boot.netPanicBadDevOpen",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktBufUseSlab",
      summary = "Whether to allocate PktBufDescriptor from the pkt slab allocator.",
      key = "VMkernel.Boot.netPktBufUseSlab",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktHeapMaxSize",
      summary = "Maximum size in MB of the pkt buffer heap (advisory only).",
      key = "VMkernel.Boot.netPktHeapMaxSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktHeapMinSize",
      summary = "Minimum size in MB of the pkt buffer heap (advisory only).",
      key = "VMkernel.Boot.netPktHeapMinSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktNumSlabSizes",
      summary = "Number of different slab sizes for the allocator.",
      key = "VMkernel.Boot.netPktNumSlabSizes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netUseMemcpyNt",
      summary = "Enable/Disable non temporal memcpy in packet copy.",
      key = "VMkernel.Boot.netUseMemcpyNt",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netUseProc",
      summary = "Enable/Disable /proc nodes.",
      key = "VMkernel.Boot.netUseProc",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.oem",
      summary = "Enable OEM extensions.",
      key = "VMkernel.Boot.oem",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.overrideSerialPortAddr",
      summary = "UART I/O address",
      key = "VMkernel.Boot.overrideSerialPortAddr",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.pageSharing",
      summary = "Enable page sharing.",
      key = "VMkernel.Boot.pageSharing",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.panicOnVmkernelAbort",
      summary = "Panic if vmkernel aborts initialization.",
      key = "VMkernel.Boot.panicOnVmkernelAbort",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.realNMI",
      summary = "Use real NMI for LINT1.",
      key = "VMkernel.Boot.realNMI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.serialPort",
      summary = "0 = disable, 1 = COM1, 2 = COM2.",
      key = "VMkernel.Boot.serialPort",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.storageHeapMaxSize",
      summary = "Maximum size in bytes of the main storage heap",
      key = "VMkernel.Boot.storageHeapMaxSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.storageHeapMinSize",
      summary = "Minimum size in bytes of the main storage heap",
      key = "VMkernel.Boot.storageHeapMinSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.techSupportMode",
      summary = "Allow VMware Tech Support Mode access.",
      key = "VMkernel.Boot.techSupportMode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableACPI",
      summary = "Enable ACPI PM timer as system reference timer.",
      key = "VMkernel.Boot.timerEnableACPI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableHPET",
      summary = "Enable HPET as system reference timer.",
      key = "VMkernel.Boot.timerEnableHPET",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableMPMC",
      summary = "Enable Cyclone MPMC timer as system reference timer.",
      key = "VMkernel.Boot.timerEnableMPMC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableTSC",
      summary = "Enable TSC as system reference timer.",
      key = "VMkernel.Boot.timerEnableTSC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerForceTSC",
      summary = "Always use TSC as system reference timer.",
      key = "VMkernel.Boot.timerForceTSC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.usbBoot",
      summary = "Require USB boot if bootFS.",
      key = "VMkernel.Boot.usbBoot",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.useNUMAInfo",
      summary = "enable/disable NUMA-ness",
      key = "VMkernel.Boot.useNUMAInfo",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.useTSCForCPUHz",
      summary = "On systems where TSC and CPU frequencies are the same, determines whether to use TSC or the non-halted clock cycles MSR to determine CPU frequency.",
      key = "VMkernel.Boot.useTSCForCPUHz",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.uwSwap",
      summary = "Enable Userworld Swap.",
      key = "VMkernel.Boot.uwSwap",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.vmkKeyboard",
      summary = "Enable vmkernel keyboard driver.",
      key = "VMkernel.Boot.vmkKeyboard",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.vmkTerminals",
      summary = "Enable switching to vmkernel terminals.",
      key = "VMkernel.Boot.vmkTerminals",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.xapicAMDDetect",
      summary = "Detect xapic on opteron",
      key = "VMkernel.Boot.xapicAMDDetect",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.xapicForce",
      summary = "Force APIC ID to 8 bits",
      key = "VMkernel.Boot.xapicForce",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   }
 ]
 stop

example output ends

[[Category: Vimsh]]</text>
    <sha1>d2900731960b1c7bec046e8970852cb99bd07c65</sha1>
  </revision>
  <revision>
    <id>558</id>
    <parentid>557</parentid>
    <timestamp>2008-12-31T18:05:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>breaking output up for display purposes</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155816" xml:space="preserve">==== vimsh hostsvc/advopt/options ====
Usage: Get the list of all supported options.
==== example output ====
Attached is some example output from a pristine ESX3.5i host.

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/advopt/options
 (vim.option.OptionDef) [
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RoutingPolicy",
      summary = "policy for interrupt routing, 1 for idle-routing, 2 for greedy routing, 0 to disable moving IRQs",
      key = "Irq.RoutingPolicy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BestVcpuRouting",
      summary = "",
      key = "Irq.BestVcpuRouting",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IRQRebalancePeriod",
      summary = "time in ms between attempts to rebalance interrupts",
      key = "Irq.IRQRebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 20000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IRQMaxLoadPct",
      summary = "maximum percentage of a cpu's resources that should be devoted to interrupts",
      key = "Irq.IRQMaxLoadPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 70,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogToFile",
      summary = "Send vmkernel log messages to /var/log/vmkernel",
      key = "Misc.LogToFile",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogToSerial",
      summary = "Send vmkernel log messages to the serial port",
      key = "Misc.LogToSerial",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogWldPrefix",
      summary = "Including running world on every log statement",
      key = "Misc.LogWldPrefix",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinimalPanic",
      summary = "Don't attempt to coredump after PSODing",
      key = "Misc.MinimalPanic",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BlueScreenTimeout",
      summary = "timeout in seconds, 0 is no timeout",
      key = "Misc.BlueScreenTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 65535,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatTimeout",
      summary = "Timeout in seconds, for sending NMI to the locked CPU",
      key = "Misc.HeartbeatTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatInterval",
      summary = "Interval in msec to check CPU lockups",
      key = "Misc.HeartbeatInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 86400000,
         defaultValue = 10000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatPanicTimeout",
      summary = "Interval in seconds after which to panic if no heartbeats received",
      key = "Misc.HeartbeatPanicTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatAnyPcpuPanic",
      summary = "Should we panic on any cpu lockups? (default we panic only for COS)",
      key = "Misc.HeartbeatAnyPcpuPanic",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MCEMonitorInterval",
      summary = "Interval[1 - 0x0xffffffff secs] to check Machine Check Errors",
      key = "Misc.MCEMonitorInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = -1,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DebugMemEnable",
      summary = "Enable memory debugging, 0 to disable",
      key = "Misc.DebugMemEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DebugBuddyEnable",
      summary = "Enable buddy debugging, 0 to disable",
      key = "Misc.DebugBuddyEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableHighDMA",
      summary = "Enable DMA above 4GB",
      key = "Misc.EnableHighDMA",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMinHardPeriod",
      summary = "Minimum hard timer interrupt period in microseconds",
      key = "Misc.TimerMinHardPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMaxHardPeriod",
      summary = "Maximum hard timer interrupt period in microseconds",
      key = "Misc.TimerMaxHardPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMinGuestPeriod",
      summary = "Minimum period for guest timer callbacks in microseconds",
      key = "Misc.TimerMinGuestPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 1000000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemAdmitMapEntriesMin",
      summary = "free KVMap entries required to power on VM",
      key = "Misc.MemAdmitMapEntriesMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemMapEntriesLow",
      summary = "Point at which to start conserving KVMap entries",
      key = "Misc.MemMapEntriesLow",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1024,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "KVMapGuardUncached",
      summary = "use guard pages around uncached kvmap mappings",
      key = "Misc.KVMapGuardUncached",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SerialPort",
      summary = "Which serial port (1 or 2) to use for logging, or 0 for neither.",
      key = "Misc.SerialPort",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SerialBaudRate",
      summary = "Baud rate",
      key = "Misc.SerialBaudRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 9600,
         max = 115200,
         defaultValue = 115200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "WatchdogBacktrace",
      summary = "Backtrace on every nth watchdog",
      key = "Misc.WatchdogBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BHTimeout",
      summary = "Timeout for bottom-half handlers in milliseconds",
      key = "Misc.BHTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BhTimeBound",
      summary = "Time bound on BH checking in us (microseconds).",
      key = "Misc.BhTimeBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 500000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IntTimeout",
      summary = "Timeout for interrupt handlers in milliseconds",
      key = "Misc.IntTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RunningVCpuLimit",
      summary = "The limit for the number of VCPUs",
      key = "Misc.RunningVCpuLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1024,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HordeEnabled",
      summary = "Enables horde mode",
      key = "Misc.HordeEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AckActual",
      summary = "Ack actual end",
      key = "Misc.AckActual",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NoWaitOnSocket",
      summary = "Don't wait on socket",
      key = "Misc.NoWaitOnSocket",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScreenSaverDelay",
      summary = "Delay in minutes before screensaver kicks in",
      key = "Misc.ScreenSaverDelay",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 60,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimEnabled",
      summary = "Enable CIM Service",
      key = "Misc.CimEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimOemProvidersEnabled",
      summary = "Enable OEM Providers",
      key = "Misc.CimOemProvidersEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimIHVProvidersEnabled",
      summary = "Enable IHV Providers",
      key = "Misc.CimIHVProvidersEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimWatchdogInterval",
      summary = "Seconds of delay between sfcbd poll",
      key = "Misc.CimWatchdogInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "FSSLightWeightProbe",
      summary = "Enable light-weight efficient probe of ESX supported datastores",
      key = "Misc.FSSLightWeightProbe",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ProcVerbose",
      summary = "option unused",
      key = "Misc.ProcVerbose",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPortRxQueueLen",
      summary = "Max length of the rx queue for virtual ports whose clients support queueing.",
      key = "Net.MaxPortRxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 500,
         defaultValue = 80,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxNetifRxQueueLen",
      summary = "Max length of the rx queue for the physical NICs.",
      key = "Net.MaxNetifRxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxNetifTxQueueLen",
      summary = "Max length of the tx queue for the physical NICs.",
      key = "Net.MaxNetifTxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "GuestTxCopyBreak",
      summary = "transmits smaller than this will be copied rather than mapped.",
      key = "Net.GuestTxCopyBreak",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = -1,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VmxnetTxCopySize",
      summary = "vmxnet tx &lt;= than this will be fully copied with no need for completion.",
      key = "Net.VmxnetTxCopySize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = -1,
         defaultValue = 256,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VmxnetWinUDPTxFullCopy",
      summary = "whether Windows vmxnet UDP tx is fullCopy.",
      key = "Net.VmxnetWinUDPTxFullCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseProc",
      summary = "whether or not to populate /proc/vmware/net. [0 = disabled, 1 = enabled]",
      key = "Net.UseProc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseLegacyProc",
      summary = "whether or not to populate legacy entries in /proc/vmware/net. [0 = disabled, 1 = enabled]",
      key = "Net.UseLegacyProc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NotifySwitch",
      summary = "Broadcasts an arp request on net handle enable. [0 = disabled, 1 = enabled]",
      key = "Net.NotifySwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetTxDontClusterSize",
      summary = "transmits smaller than this will not be subject to clustering/coalescing.",
      key = "Net.NetTxDontClusterSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8192,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetPktAllocTries",
      summary = "Number of tries for allocating pkt within the page.",
      key = "Net.NetPktAllocTries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceTxTimeout",
      summary = "set the coalesce timeout in micro-seconds.",
      key = "Net.CoalesceTxTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = -1,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceDefaultOn",
      summary = "whether dynamic coalescing is on by default. [0 = disabled by default, 1 = enabled by default]",
      key = "Net.CoalesceDefaultOn",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceLowTxMsRate",
      summary = "No tx coalescing calibration when the number of pkts tx per ms is lower than this number.",
      key = "Net.CoalesceLowTxMsRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 64,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceLowRxMsRate",
      summary = "No rx coalescing calibration when the number of pkts rx per ms is lower than this number.",
      key = "Net.CoalesceLowRxMsRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 64,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceHandlerPcpu",
      summary = "Pcpu that coalesce timeout handler runs on.",
      key = "Net.CoalesceHandlerPcpu",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceTxAlwaysPoll",
      summary = "Whether always poll Tx at coalesce timeout handler.",
      key = "Net.CoalesceTxAlwaysPoll",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "vmxnetBHNetPoll",
      summary = "Whether to poll for Tx in BH NetPoll.",
      key = "Net.vmxnetBHNetPoll",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "vmxnetThroughputWeight",
      summary = "How far to favor throughput in vmxnet behavior.",
      key = "Net.vmxnetThroughputWeight",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EtherswitchHashSize",
      summary = "number of ports on the switch x 2^N is the size of the hash table for looking up MACs.",
      key = "Net.EtherswitchHashSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NoLocalCSum",
      summary = "if set, don't bother checksumming local tx/rx frames.",
      key = "Net.NoLocalCSum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortSerializeInput",
      summary = "if enabled(1), input into port through appropriate calls are serialized to prevent out-of-order delivery.",
      key = "Net.PortSerializeInput",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortFlushIterLimit",
      summary = "when input is serialized, this bounds the number of times a thread flushes the deferred list.",
      key = "Net.PortFlushIterLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 127,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortFlushPktLimit",
      summary = "when input is serialized, this bounds the number of pkts a thread flushes from the deferred list.",
      key = "Net.PortFlushPktLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortTrackTxRace",
      summary = "if enabled(1), collect statistics on potential tx race between concurrent threads.",
      key = "Net.PortTrackTxRace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortKeepDetailedStats",
      summary = "if enabled(1), collect detailed statistics on port.",
      key = "Net.PortKeepDetailedStats",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortDisableTimeout",
      summary = "max timeout delay to wait for ports to complete I/O before disabling.",
      key = "Net.PortDisableTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipHeapSize",
      summary = "Initial size of the tcpip module heap in megabytes. (REQUIRES REBOOT!)",
      key = "Net.TcpipHeapSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 6,
         max = 30,
         defaultValue = 9,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipHeapMax",
      summary = "Max megabytes the tcpip module heap can grow to. (REQUIRES REBOOT!)",
      key = "Net.TcpipHeapMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 120,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPageInQueueLen",
      summary = "maximum number of pageing requests to queue for guest DMA.",
      key = "Net.MaxPageInQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxBeaconsAtOnce",
      summary = "maximum number of beacons to send in one beacon cycle.",
      key = "Net.MaxBeaconsAtOnce",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4096,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxBeaconVlans",
      summary = "maximum number of VLANs to probe with beacons.",
      key = "Net.MaxBeaconVlans",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4096,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipNoBcopyRx",
      summary = "Avoid bcopy in tcp rx.",
      key = "Net.TcpipNoBcopyRx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipCopySmallTx",
      summary = "Copy and tx complete small packets for tcp tx.",
      key = "Net.TcpipCopySmallTx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipLargeRx",
      summary = "Allow frames larger than mtu for tcp rx.",
      key = "Net.TcpipLargeRx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipMaxPktInFlight",
      summary = "Maximum zero copy mbuf packet in flight.",
      key = "Net.TcpipMaxPktInFlight",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipDelayedAck",
      summary = "Enable/Disable delayed ACKs.",
      key = "Net.TcpipDelayedAck",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LinkStatePollTimeout",
      summary = "Link State poll timer period in milliseconds.",
      key = "Net.LinkStatePollTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 90000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipUseIoat",
      summary = "Use IOAT chipset if present. (REQUIRES REBOOT!)",
      key = "Net.TcpipUseIoat",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipIoatAlwaysWakeup",
      summary = "Wakeup soreceive thread on every tcp packet (for IOAT only).",
      key = "Net.TcpipIoatAlwaysWakeup",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "E1000TxZeroCopy",
      summary = "Use tx zero copy for non-tso packets for e1000.",
      key = "Net.E1000TxZeroCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "E1000TxTsoZeroCopy",
      summary = "Use tx zero copy for tso packets for e1000.",
      key = "Net.E1000TxTsoZeroCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinEtherLen",
      summary = "Minimum size ethernet frame to transmit.",
      key = "Net.MinEtherLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1518,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPktRxListQueue",
      summary = "Maximum packet we can queue in rxList.",
      key = "Net.MaxPktRxListQueue",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 3500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxWorkBound",
      summary = "Maximum rx pkts processed in one NetBH invocation.",
      key = "Net.NetBHRxWorkBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 320,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxInputBound",
      summary = "Maximum rx pkts sent up an uplink at one go.",
      key = "Net.NetBHRxInputBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxStormThreshold",
      summary = "Declare Rx Storm after this number of consecutive rx pkt drops during queuing in NetBH rxList.",
      key = "Net.NetBHRxStormThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 320,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReversePathFwdCheck",
      summary = "Block the multicast/broadcast packets that come back from physical switches in a teamed environment.",
      key = "Net.ReversePathFwdCheck",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllowPromiscFilters",
      summary = "Block duplicate multicast/broadcast packet in a teamed environment when the virtual switch is set to Promiscuous mode.",
      key = "Net.AllowPromiscFilters",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Vmxnet2PinRxBuf",
      summary = "Pin RX buffers for vmxnet2 clients. (windows guest only)",
      key = "Net.Vmxnet2PinRxBuf",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TsoDumpPkt",
      summary = "detailed dump of every &lt;n&gt; pkts.",
      key = "Net.TsoDumpPkt",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPVersion",
      summary = "IGMP Version (2 or 3).",
      key = "Net.IGMPVersion",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 2,
         max = 3,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPQueries",
      summary = "Number of IGMP Queries to send during after VMotion/Teaming failover.",
      key = "Net.IGMPQueries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NcpLlcSap",
      summary = "beacon/color NCP messages created with this SAP (DSAP/SSAP)",
      key = "Net.NcpLlcSap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPRouterIP",
      summary = "Router IP Address for IGMP (generally not necessary to set this).",
      key = "Net.IGMPRouterIP",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "10.0.0.0",
         validCharacters = "10.0.0.0",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BalancePeriod",
      summary = "period in seconds, 0 to disable",
      key = "Mem.BalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 120,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SamplePeriod",
      summary = "period in seconds, 0 to disable",
      key = "Mem.SamplePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 180,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdleTax",
      summary = "idle memory tax rate",
      key = "Mem.IdleTax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 99,
         defaultValue = 75,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdleTaxType",
      summary = "idle tax type. 0=flat, 1=variable",
      key = "Mem.IdleTaxType",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SampleActivePctMin",
      summary = "lower bound for sampled active memory",
      key = "Mem.SampleActivePctMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareScanGHz",
      summary = "max page scan rate in MB/sec per GHz of host CPU, 0 to disable",
      key = "Mem.ShareScanGHz",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareScanTime",
      summary = "desired time in minutes to scan entire VM",
      key = "Mem.ShareScanTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 600,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareRateMax",
      summary = "per-VM upper limit on pshare scan/check rate in pages/sec. (0 to disable)",
      key = "Mem.ShareRateMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32768,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CtlMaxPercent",
      summary = "vmmemctl limit as percentage of VM max size",
      key = "Mem.CtlMaxPercent",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 75,
         defaultValue = 65,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocHighThreshold",
      summary = "Threshold (in MB) at which we start allocating memory above 4GB",
      key = "Mem.AllocHighThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 4096,
         defaultValue = 1500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocGuestLargePage",
      summary = "Enable large page backing of guest memory",
      key = "Mem.AllocGuestLargePage",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocUsePSharePool",
      summary = "Use pshare pool to allocate memory for shared pages",
      key = "Mem.AllocUsePSharePool",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocUseGuestPool",
      summary = "Use large page pool to allocate memory for guest pages",
      key = "Mem.AllocUseGuestPool",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AdmitHeapMin",
      summary = "free heap space required to power on VM, in KB",
      key = "Mem.AdmitHeapMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 256,
         max = 10240,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinFreePct",
      summary = "Minimum percent of memory that should be kept free",
      key = "Mem.MinFreePct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 6,
         max = 24,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareCOSBufSize",
      summary = "Specify number of MPNs to be used by COW P2M buffer",
      key = "Mem.ShareCOSBufSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 2,
         max = 8,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapIORetry",
      summary = "Number of retries for swap-in operation on I/O failures",
      key = "Mem.SwapIORetry",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TestOnAlloc",
      summary = "Check the newly allocated page for Memory Errors",
      key = "Mem.TestOnAlloc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimatePeriod",
      summary = "Sleep interval for pshare-est daemon world",
      key = "Mem.ShareEstimatePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 300000,
         defaultValue = 30000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimateProbe",
      summary = "Maximum per-VM page probes for pshare estimation",
      key = "Mem.ShareEstimateProbe",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 5000,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimateSamples",
      summary = "Minimum required per-VM page samples for pshare estimation",
      key = "Mem.ShareEstimateSamples",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 100,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "kernelResvPad",
      summary = "Extra padding (in MB) for MemSched's tracking of kernel memory usage",
      key = "Mem.kernelResvPad",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 128,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogLowMemoryStateUsage",
      summary = "Log memory usage of memclients during low memory state",
      key = "Mem.LogLowMemoryStateUsage",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogLowMemoryStateBT",
      summary = "Log back-trace of contexts that allocate MPNs during low memory state",
      key = "Mem.LogLowMemoryStateBT",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapDecayPct",
      summary = "Percentage of swap target to be proactively transferred to balloon target",
      key = "Mem.SwapDecayPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DesiredAllocEnable",
      summary = "Enable use of desired allocations when computing allocation targets",
      key = "Mem.DesiredAllocEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DesiredAllocPct",
      summary = "Percentage of consumed memory to be considered as the desired allocation target",
      key = "Mem.DesiredAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 200,
         defaultValue = 125,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BonusAllocPct",
      summary = "Percentage of group allocation to be distributed to children as bonus",
      key = "Mem.BonusAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapFilePersist",
      summary = "The swap file is not deleted when the VM powers off, 1 to enable",
      key = "Mem.SwapFilePersist",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapInBatchPages",
      summary = "Number of pages swapped in per batch during opportunistic prefaulting",
      key = "Mem.SwapInBatchPages",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 512,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapAsyncWritePages",
      summary = "Maximum allowed pending asynchronous swapout requests per VM",
      key = "Mem.SwapAsyncWritePages",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 16,
         max = 64,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HostLocalSwapDirEnabled",
      summary = "Enable use of host-local swap directory",
      key = "Mem.HostLocalSwapDirEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageAllocAllowance",
      summary = "Memory alloc allowance (in 4K pages) while usage is tracked via heartbeat or swap action post",
      key = "Mem.TrackUsageAllocAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 4096,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageSwapAllowance",
      summary = "Memory swap allowance (in 4K pages) while usage is tracked via heartbeat or swap action post",
      key = "Mem.TrackUsageSwapAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 4096,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageLPageAllowance",
      summary = "Memory large page alloc allowance (in 2M pages) while usage is tracked via heartbeat action post",
      key = "Mem.TrackUsageLPageAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageHeartbeatPeriod",
      summary = "Sleep interval in seconds for busmem heartbeat",
      key = "Mem.TrackUsageHeartbeatPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 300,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageHeartbeatEnable",
      summary = "Enable/disable MPN usage tracking via heartbeat monitor action (0 for disable)",
      key = "Mem.TrackUsageHeartbeatEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMOverheadGrowthLimit",
      summary = "Default limit (in MB) on VM overhead memory growth",
      key = "Mem.VMOverheadGrowthLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = -1,
         defaultValue = -1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HostLocalSwapDir",
      summary = "Host-local directory for VM swap files",
      key = "Mem.HostLocalSwapDir",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigratePeriod",
      summary = "milliseconds between opportunities to migrate across cpus",
      key = "Cpu.MigratePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CellMigratePeriod",
      summary = "milliseconds between opportunities to migrate across cells",
      key = "Cpu.CellMigratePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 60000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "WakeupMigrateIdle",
      summary = "migrate to idle package on wakeup, 0 to disable",
      key = "Cpu.WakeupMigrateIdle",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PcpuMigrateIdle",
      summary = "always migrate from remote pcpus when a core becomes idle, 0 to disable",
      key = "Cpu.PcpuMigrateIdle",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CreditAgePeriod",
      summary = "period in milliseconds",
      key = "Cpu.CreditAgePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 10000,
         defaultValue = 3000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BoundLagQuanta",
      summary = "number of global quanta before bound lag",
      key = "Cpu.BoundLagQuanta",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 100,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CacheStats",
      summary = "enable per-world cache data collection",
      key = "Cpu.CacheStats",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Quantum",
      summary = "quantum in milliseconds",
      key = "Cpu.Quantum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewPollUsec",
      summary = "interval between coscheduling skew checks, in usec",
      key = "Cpu.SkewPollUsec",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 5000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewInstanceThreshold",
      summary = "maximum individual skew between vcpus in usec, 0 to disable",
      key = "Cpu.SkewInstanceThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewCumulativeThreshold",
      summary = "maximum cumulative skew between vcpus in usec, 0 to disable",
      key = "Cpu.SkewCumulativeThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdlePackageRebalancePeriod",
      summary = "usec between chances to rebalance idle packages (0 to disable, 100000 max)",
      key = "Cpu.IdlePackageRebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 541,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IntraCoreMigrate",
      summary = " When to allow intra-core migrations [0:when inter-core migration allowed, 1:always]",
      key = "Cpu.IntraCoreMigrate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMotionMinAllocPct",
      summary = "Per-VM minimum CPU allocations (in %) for VMotion requirements",
      key = "Cpu.VMotionMinAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMAdmitCheckPerVcpuMin",
      summary = "Perform additional admission control check that per vcpu VM cpu min does not exceed the speed of a single physical  cpu. [0:dis",
      key = "Cpu.VMAdmitCheckPerVcpuMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },

   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoSchedIdleBalancePeriod",
      summary = "millisecs between opportunities to move co-scheduled vcpus to more idle cores and packages, 0 to disable",
      key = "Cpu.CoSchedIdleBalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalancePeriod",
      summary = "frequency of NUMA node rebalancing, in milliseconds",
      key = "Numa.RebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 60000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigImbalanceThreshold",
      summary = "minimum percent load imbalance between nodes to trigger migration",
      key = "Numa.MigImbalanceThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 200,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigThreshold",
      summary = "minimum percent load balance improvement to allow single migration/swap",
      key = "Numa.MigThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigThrashThreshold",
      summary = "maximum post-migration load imbalance, as percentage of pre-migration imbalance, to prevent thrashing",
      key = "Numa.MigThrashThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapLoadEnable",
      summary = "1 to enable VM swaps across nodes to balance CPU load, 0 to disable",
      key = "Numa.SwapLoadEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapLocalityEnable",
      summary = "1 to enable VM swaps across nodes to improve memory locality, 0 to disable",
      key = "Numa.SwapLocalityEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceEnable",
      summary = "1 to enable NUMA rebalancer, 0 to disable it",
      key = "Numa.RebalanceEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceCoresTotal",
      summary = "minimum number of total host cores required to enable NUMA rebalancer",
      key = "Numa.RebalanceCoresTotal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 32,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceCoresNode",
      summary = "minimum number of cores per node required to enable NUMA rebalancer",
      key = "Numa.RebalanceCoresNode",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 8,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MonMigEnable",
      summary = "1 to allow NUMASched monitor migrations, 0 to disallow",
      key = "Numa.MonMigEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AutoMemAffinity",
      summary = "1 to set mem affinity automatically based on cpu affinity, 0 to disable",
      key = "Numa.AutoMemAffinity",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageMigEnable",
      summary = "1 to permit NUMASched to manipulate page migration, 0 to disallow it",
      key = "Numa.PageMigEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PostMigUseActiveMetric",
      summary = "1 to use alternative migActive metric for post-migration imbalance prediction, 0 to use default migEntitlement metric",
      key = "Numa.PostMigUseActiveMetric",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragEnable",
      summary = "Enable large page defragmentation",
      key = "LPage.LPageDefragEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageMarkLowNodes",
      summary = "Enable marking of nodes with low large pages free",
      key = "LPage.LPageMarkLowNodes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragRateVM",
      summary = "Maximum number of lpage defrag attempts per second per VM",
      key = "LPage.LPageDefragRateVM",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragRateTotal",
      summary = "Maximum number of lpage defrag attempts per second ",
      key = "LPage.LPageDefragRateTotal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10240,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageAlwaysTryForNPT",
      summary = "Enable always try to alloc large page for NPT",
      key = "LPage.LPageAlwaysTryForNPT",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesNormal",
      summary = "shares for normal/default disk priority",
      key = "Disk.SharesNormal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesHigh",
      summary = "shares for high disk priority",
      key = "Disk.SharesHigh",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesLow",
      summary = "shares for low disk priority",
      key = "Disk.SharesLow",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BandwidthCap",
      summary = "cap on disk bandwidth (Kb/s) usage",
      key = "Disk.BandwidthCap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 2147483647,
         defaultValue = 2147483647,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ThroughputCap",
      summary = "cap on disk throughput (IO/S) usage",
      key = "Disk.ThroughputCap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 2147483647,
         defaultValue = 2147483647,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SectorMaxDiff",
      summary = "Distance in sectors at which disk BW sched affinity stops",
      key = "Disk.SectorMaxDiff",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2000000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQuantum",
      summary = "Number of consecutive requests from one World",
      key = "Disk.SchedQuantum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 64,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedNumReqOutstanding",
      summary = "Number of outstanding commands to a target with competing worlds",
      key = "Disk.SchedNumReqOutstanding",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQControlSeqReqs",
      summary = "Number of consecutive requests from a VM required to raise the outstanding commands to max",
      key = "Disk.SchedQControlSeqReqs",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2048,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQControlVMSwitches",
      summary = "Number of switches between commands issued by different VMs required to reduce outstanding commands to SchedNumReqOutstanding",
      key = "Disk.SchedQControlVMSwitches",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2048,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxLUN",
      summary = "Maximum LUN id that is scanned on a target",
      key = "Disk.MaxLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 256,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SupportSparseLUN",
      summary = "Support for sparse LUNs if set to one",
      key = "Disk.SupportSparseLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseReportLUN",
      summary = "Use the REPORT LUN command to speed up scanning for devices",
      key = "Disk.UseReportLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseDeviceReset",
      summary = "Use device reset (instead of bus reset) to reset a SCSI device",
      key = "Disk.UseDeviceReset",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseLunReset",
      summary = "Use LUN reset (instead of device/bus reset) to reset a SCSI device",
      key = "Disk.UseLunReset",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RetryUnitAttention",
      summary = "Retry all SCSI commands that return a unit attention error",
      key = "Disk.RetryUnitAttention",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetOnFailover",
      summary = "Issue a SCSI reset when failing over to an alternate HBA",
      key = "Disk.ResetOnFailover",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PathEvalTime",
      summary = "The number of seconds between FC path evaluations",
      key = "Disk.PathEvalTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 1500,
         defaultValue = 300,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxVCNotReadyTime",
      summary = "The number of seconds a VC path can report NOT READY status before being declared dead",
      key = "Disk.MaxVCNotReadyTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 15,
         max = 90,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxDS400NotReadyTime",
      summary = "The number of seconds a DS400 path can report IN TRANSITION before being declared dead",
      key = "Disk.MaxDS400NotReadyTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 15,
         max = 90,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableNaviReg",
      summary = "Enable automatic NaviAgent registration with CLARiiON and Invista (vmvisor only)",
      key = "Disk.EnableNaviReg",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DelayOnBusy",
      summary = "Delay in milliseconds for completion of commands with a BUSY status",
      key = "Disk.DelayOnBusy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 400,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetLatency",
      summary = "Delay in milliseconds between reset thread wake-ups",
      key = "Disk.ResetLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 600000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxResetLatency",
      summary = "Delay in milliseconds before logging warnings and spawning new reset worlds if a reset is overdue or taking too long",
      key = "Disk.MaxResetLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 600000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetPeriod",
      summary = "Delay in seconds between bus resets retries",
      key = "Disk.ResetPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 3600,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetMaxRetries",
      summary = "Max number of bus reset retries (0=infinite)",
      key = "Disk.ResetMaxRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadMin",
      summary = "Min number of reset handler threads",
      key = "Disk.ResetThreadMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadMax",
      summary = "Max number of reset handler threads",
      key = "Disk.ResetThreadMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadExpires",
      summary = "Life in seconds of an inactive reset handle thread",
      key = "Disk.ResetThreadExpires",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetOverdueLogPeriod",
      summary = "Delay in seconds between logs of overdue reset",
      key = "Disk.ResetOverdueLogPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SPBlksToSwitch",
      summary = "Number of blocks of I/O sent over a given path before a path switch (0=infinite)",
      key = "Disk.SPBlksToSwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000000,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SPCmdsToSwitch",
      summary = "Number of I/O commands sent over a given path before a path switch (0=infinite) ",
      key = "Disk.SPCmdsToSwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreventVMFSOverwrite",
      summary = "Prevent Console OS from overwriting VMFS partitions",
      key = "Disk.PreventVMFSOverwrite",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DumpMaxRetries",
      summary = "Max number of I/O retries during disk dump",
      key = "Disk.DumpMaxRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DiskMaxIOSize",
      summary = "Max Disk READ/WRITE I/O size before splitting (in KB)",
      key = "Disk.DiskMaxIOSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 32767,
         defaultValue = 32767,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaskLUNs",
      summary = "LUN's to mask from kernel. Format: &lt;adapter&gt;:&lt;target&gt;:&lt;comma separated LUN range list&gt;",
      key = "Disk.MaskLUNs",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SANDevicesWithAPFailover",
      summary = "SAN devices with Active/Passive Path Failover. Format: &lt;16 Character Device Id&gt;:&lt;16 Character Device Id&gt;:...",
      key = "Disk.SANDevicesWithAPFailover",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Enabled",
      summary = "Enable hot migration support",
      key = "Migrate.Enabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreCopyLeftMB",
      summary = "Maximum modified memory left over after pre-copy is done",
      key = "Migrate.PreCopyLeftMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreCopyMinProgressMB",
      summary = "Minimum reduction in modified memory after a pre-copy iteration",
      key = "Migrate.PreCopyMinProgressMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetTimeout",
      summary = "Timeout for migration network operations",
      key = "Migrate.NetTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 3600,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemChksum",
      summary = "Checksum VM's memory while migrating",
      key = "Migrate.MemChksum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TSMaster",
      summary = "Pseudo-synchronize clocks for migration to/from this machine",
      key = "Migrate.TSMaster",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInTimeout",
      summary = "Time in seconds to wait for page-in to finish",
      key = "Migrate.PageInTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 18000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInTimeoutResetOnProgress",
      summary = "Page-in progess will reset the page-in timeout",
      key = "Migrate.PageInTimeoutResetOnProgress",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInProgress",
      summary = "Time in seconds after which a page-in will be killed if there is no progress",
      key = "Migrate.PageInProgress",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 18000,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInBeforeResume",
      summary = "Wait for page-in to finish before resuming on the dest",
      key = "Migrate.PageInBeforeResume",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PassthroughLocking",
      summary = "Disable locking for scsi passthrough devices",
      key = "Scsi.PassthroughLocking",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ConflictRetries",
      summary = "Maximum number of retries when encountering reservation conflict.",
      key = "Scsi.ConflictRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 200,
         defaultValue = 80,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogMultiPath",
      summary = "Log path state changes",
      key = "Scsi.LogMultiPath",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogAborts",
      summary = "Log timing of aborted or reseted IOs",
      key = "Scsi.LogAborts",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PrintCmdErrors",
      summary = "Print the error to log on a SCSI command error.",
      key = "Scsi.PrintCmdErrors",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveTime",
      summary = "Maximum time (in msecs) a system-initiated reservation is normally held (debug only)",
      key = "Scsi.MaxReserveTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 50,
         max = 500,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveTotalTime",
      summary = "Maximum time (in msecs) a system-initiated reservation normally takes from issue to release (debug only)",
      key = "Scsi.MaxReserveTotalTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 50,
         max = 500,
         defaultValue = 250,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveBacktrace",
      summary = "Log a backtrace if caller exceeds SCSI_MAX_RESERVE_TIME or SCSI_MAX_RESERVE_TOTALTIME (debug only)",
      key = "Scsi.MaxReserveBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReserveBacktrace",
      summary = "Log a backtrace for all Reserve/Release pairs (debug only)",
      key = "Scsi.ReserveBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SCSITimeout_ScanTime",
      summary = "time (in ms) to sleep between checking for timed-out async IO",
      key = "Scsi.SCSITimeout_ScanTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 99999999,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SCSITimeout_ReabortTime",
      summary = "delay (in ms) after an abort due to timeout before the abort is re-issued",
      key = "Scsi.SCSITimeout_ReabortTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 99999999,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScanOnDriverLoad",
      summary = "Scan new SCSI buses on device driver load",
      key = "Scsi.ScanOnDriverLoad",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadMin",
      summary = "Min number of timeout task-mgmt handler threads",
      key = "Scsi.TimeoutTMThreadMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadMax",
      summary = "Max number of device task-mgmt handler threads",
      key = "Scsi.TimeoutTMThreadMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadExpires",
      summary = "Life in seconds of timeout task mgmt handler thread",
      key = "Scsi.TimeoutTMThreadExpires",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadRetry",
      summary = "Delay in milliseconds before retrying failed timeout taskmgmt",
      key = "Scsi.TimeoutTMThreadRetry",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 100000,
         defaultValue = 40000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadLatency",
      summary = "Delay in ms before waking up new task mgmt thread ",
      key = "Scsi.TimeoutTMThreadLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 600000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScsiRestartStalledQueueLatency",
      summary = "Delay in ms before restarting a stalled queue ",
      key = "Scsi.ScsiRestartStalledQueueLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 60000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CompareLUNNumber",
      summary = "Consider LUN number when determining LUN identity.",
      key = "Scsi.CompareLUNNumber",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScsiRescanAllHbas",
      summary = "During esxcfg-rescan, rescan all vmhbas at once rather than just a single vmhba",
      key = "Scsi.ScsiRescanAllHbas",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReaddirRetries",
      summary = "Maximum number of retries when reading entries from directories",
      key = "User.ReaddirRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 20,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CDROMSenseTimeout",
      summary = "Physical CDROM sense timeout (seconds)",
      key = "User.CDROMSenseTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PTEDisableNX",
      summary = "Disables the use of NX bit in user pagetable entries",
      key = "User.PTEDisableNX",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IndirectSend",
      summary = "Use NFS indirect send",
      key = "NFS.IndirectSend",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DiskFileLockUpdateFreq",
      summary = "Time (in seconds) between updates to a disk lock file [8-3600]",
      key = "NFS.DiskFileLockUpdateFreq",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 8,
         max = 3600,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockUpdateTimeout",
      summary = "Time (in seconds) before we abort an outstanding lock update",
      key = "NFS.LockUpdateTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockRenewMaxFailureNumber",
      summary = "Number of update failures before a disk file lock is declared stale",
      key = "NFS.LockRenewMaxFailureNumber",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockDisable",
      summary = "1 to disable NFS locking protocol",
      key = "NFS.LockDisable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatFrequency",
      summary = "Time in seconds between heartbeats",
      key = "NFS.HeartbeatFrequency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 86400,
         defaultValue = 9,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatTimeout",
      summary = "Time in seconds before we abort an outstanding hearbeat",
      key = "NFS.HeartbeatTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 3,
         max = 30,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatDelta",
      summary = "Time in seconds since the last successful update before we send a heartbeat",
      key = "NFS.HeartbeatDelta",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 3,
         max = 30,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatMaxFailures",
      summary = "Number of sequential failures before we mark a volume as down",
      key = "NFS.HeartbeatMaxFailures",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxVolumes",
      summary = "Maximum number of mounted NFS volumes",
      key = "NFS.MaxVolumes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 8,
         max = 32,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SendBufferSize",
      summary = "Default size of socket's send buffer in KB",
      key = "NFS.SendBufferSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 264,
         defaultValue = 264,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReceiveBufferSize",
      summary = "Default Size of socket's receive buffer in KB",
      key = "NFS.ReceiveBufferSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 264,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VolumeRemountFrequency",
      summary = "Time in seconds before attempting to remount a volume",
      key = "NFS.VolumeRemountFrequency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 3600,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UDPRetransmitDelay",
      summary = "Time in milliseconds retransmitting a UDP RPC",
      key = "NFS.UDPRetransmitDelay",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 2000,
         defaultValue = 700,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "OpenWithoutJournal",
      summary = "Open file system when out of space for journal allocation, allowing reads and no meta-data updates",
      key = "VMFS3.OpenWithoutJournal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxHeapSizeMB",
      summary = "Maximum size (in MB) to which the VMFS-3 heap is allowed to grow",
      key = "VMFS3.MaxHeapSizeMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 16,
         max = 128,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SoftMaxDirty",
      summary = "Flush immediately if this many buffers are dirty (percent)",
      key = "BufferCache.SoftMaxDirty",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HardMaxDirty",
      summary = "Block writers if this many buffers are dirty (percent)",
      key = "BufferCache.HardMaxDirty",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 95,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "FlushInterval",
      summary = "Flush periodically at this interval (msec)",
      key = "BufferCache.FlushInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 3600000,
         defaultValue = 30000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableResignature",
      summary = "Enable Volume Resignaturing",
      key = "LVM.EnableResignature",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DisallowSnapshotLun",
      summary = "Disallow access to snapshot LUN if resignaturing is off. This is ignored if resignaturing is on.",
      key = "LVM.DisallowSnapshotLun",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxHeapSizeMB",
      summary = "Maximum size (in MB) to which the COW heap is allowed to grow",
      key = "COW.MaxHeapSizeMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 192,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxDentryPerObj",
      summary = "Maximum directory entries cached per directory",
      key = "DirentryCache.MaxDentryPerObj",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = 30000,
         defaultValue = 2500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Annotations.WelcomeMessage",
      summary = "",
      key = "Annotations.WelcomeMessage",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.eax",
      summary = "CPUID override that may be applied to level 0 register eax; controlled by Config.Defaults.cpuidMask.mode.0.eax.",
      key = "Config.Defaults.cpuidMask.val.0.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.ebx",
      summary = "CPUID override that may be applied to level 0 register ebx; controlled by Config.Defaults.cpuidMask.mode.0.ebx.",
      key = "Config.Defaults.cpuidMask.val.0.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.ecx",
      summary = "CPUID override that may be applied to level 0 register ecx; controlled by Config.Defaults.cpuidMask.mode.0.ecx.",
      key = "Config.Defaults.cpuidMask.val.0.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.edx",
      summary = "CPUID override that may be applied to level 0 register edx; controlled by Config.Defaults.cpuidMask.mode.0.edx.",
      key = "Config.Defaults.cpuidMask.val.0.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.eax",
      summary = "CPUID override that may be applied to level 1 register eax; controlled by Config.Defaults.cpuidMask.mode.1.eax.",
      key = "Config.Defaults.cpuidMask.val.1.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.ebx",
      summary = "CPUID override that may be applied to level 1 register ebx; controlled by Config.Defaults.cpuidMask.mode.1.ebx.",
      key = "Config.Defaults.cpuidMask.val.1.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.ecx",
      summary = "CPUID override that may be applied to level 1 register ecx; controlled by Config.Defaults.cpuidMask.mode.1.ecx.",
      key = "Config.Defaults.cpuidMask.val.1.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.edx",
      summary = "CPUID override that may be applied to level 1 register edx; controlled by Config.Defaults.cpuidMask.mode.1.edx.",
      key = "Config.Defaults.cpuidMask.val.1.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.eax",
      summary = "CPUID override that may be applied to level 80000000 register eax; controlled by Config.Defaults.cpuidMask.mode.80000000.eax.",
      key = "Config.Defaults.cpuidMask.val.80000000.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.ebx",
      summary = "CPUID override that may be applied to level 80000000 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000000.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000000.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.ecx",
      summary = "CPUID override that may be applied to level 80000000 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000000.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000000.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.edx",
      summary = "CPUID override that may be applied to level 80000000 register edx; controlled by Config.Defaults.cpuidMask.mode.80000000.edx.",
      key = "Config.Defaults.cpuidMask.val.80000000.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.eax",
      summary = "CPUID override that may be applied to level 80000001 register eax; controlled by Config.Defaults.cpuidMask.mode.80000001.eax.",
      key = "Config.Defaults.cpuidMask.val.80000001.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.ebx",
      summary = "CPUID override that may be applied to level 80000001 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000001.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000001.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.ecx",
      summary = "CPUID override that may be applied to level 80000001 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000001.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000001.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.edx",
      summary = "CPUID override that may be applied to level 80000001 register edx; controlled by Config.Defaults.cpuidMask.mode.80000001.edx.",
      key = "Config.Defaults.cpuidMask.val.80000001.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.eax",
      summary = "CPUID override that may be applied to level 80000008 register eax; controlled by Config.Defaults.cpuidMask.mode.80000008.eax.",
      key = "Config.Defaults.cpuidMask.val.80000008.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.ebx",
      summary = "CPUID override that may be applied to level 80000008 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000008.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000008.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.ecx",
      summary = "CPUID override that may be applied to level 80000008 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000008.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000008.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.edx",
      summary = "CPUID override that may be applied to level 80000008 register edx; controlled by Config.Defaults.cpuidMask.mode.80000008.edx.",
      key = "Config.Defaults.cpuidMask.val.80000008.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.eax",
      summary = "CPUID override that may be applied to level 8000000A register eax; controlled by Config.Defaults.cpuidMask.mode.8000000A.eax.",
      key = "Config.Defaults.cpuidMask.val.8000000A.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.ebx",
      summary = "CPUID override that may be applied to level 8000000A register ebx; controlled by Config.Defaults.cpuidMask.mode.8000000A.ebx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.ecx",
      summary = "CPUID override that may be applied to level 8000000A register ecx; controlled by Config.Defaults.cpuidMask.mode.8000000A.ecx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.edx",
      summary = "CPUID override that may be applied to level 8000000A register edx; controlled by Config.Defaults.cpuidMask.mode.8000000A.edx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "security.host.ruissl",
      summary = "Require SSL to be used when communicating with the host over port 902.",
      key = "Config.Defaults.security.host.ruissl",
      optionType = (vim.option.BoolOption) {
         dynamicType = "",
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "guest.commands.sharedPolicyRefCount",
      summary = "Reference count to enable guest operations.",
      key = "Config.GlobalSettings.guest.commands.sharedPolicyRefCount",
      optionType = (vim.option.IntOption) {
         dynamicType = "",
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.ConfiguredScratchLocation",
      summary = "The directory configured to be used for scratch space.Changes will take effect on next reboot.",
      key = "ScratchConfig.ConfiguredScratchLocation",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.ConfiguredSwapState",
      summary = "Whether userwold swap is configured to be enabledChanges will take effect on next reboot.",
      key = "ScratchConfig.ConfiguredSwapState",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = false,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.CurrentScratchLocation",
      summary = "The directory currently being used for scratch space",
      key = "ScratchConfig.CurrentScratchLocation",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = true,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.CurrentSwapState",
      summary = "Whether userworld swap is currently enabled",
      key = "ScratchConfig.CurrentSwapState",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = true,
         supported = false,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Local.DatastorePath",
      summary = "Datastore path of file to which local syslogd data is written.",
      key = "Syslog.Local.DatastorePath",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Remote.Hostname",
      summary = "Hostname to which syslog data will be forwarded.  Disabled on null.",
      key = "Syslog.Remote.Hostname",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Remote.Port",
      summary = "Port to which syslog data will be forwarded.",
      key = "Syslog.Remote.Port",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 65535,
         defaultValue = 514,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.ACPI",
      summary = "Initialize ACPI CA.",
      key = "VMkernel.Boot.ACPI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.acpiDbgLevel",
      summary = "ACPI debug level",
      key = "VMkernel.Boot.acpiDbgLevel",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.assumeCommonBusClock",
      summary = "Assume all NUMA nodes run off a common, synchronous bus clock (normally autodetected).",
      key = "VMkernel.Boot.assumeCommonBusClock",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.assumePerNodeBusClock",
      summary = "Assume each NUMA node has a separate bus clock (normally autodetected).",
      key = "VMkernel.Boot.assumePerNodeBusClock",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.baudRate",
      summary = "Baud rate to run the serial port at.",
      key = "VMkernel.Boot.baudRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 115200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      summary = "Buddy physical mem debug info switch.",
      key = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.busSpeedMayVary",
      summary = "Allow different bus clock speeds, even within a single NUMA node or SMP system.",
      key = "VMkernel.Boot.busSpeedMayVary",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.busSpeedMayVaryPerNode",
      summary = "Allow substantially different bus clock speeds in different NUMA nodes.",
      key = "VMkernel.Boot.busSpeedMayVaryPerNode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.checkCPUIDLimit",
      summary = "Refuse to run on CPUID limited cpus.",
      key = "VMkernel.Boot.checkCPUIDLimit",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.clockMultiplierMayVary",
      summary = "Allow different CPU clock multipliers, even within a single NUMA node or SMP system.",
      key = "VMkernel.Boot.clockMultiplierMayVary",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      summary = "Allow different CPU clock multipliers in different NUMA nodes.",
      key = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.coresPerPkg",
      summary = "Number of cores per package that vmkernel should use",
      key = "VMkernel.Boot.coresPerPkg",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.correctBSPMTRRMasks",
      summary = "Correct BSP Variable MTRR masks to match the processor physical address bit support",
      key = "VMkernel.Boot.correctBSPMTRRMasks",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.cpuCellSize",
      summary = "Requested cpu scheduler cell size.",
      key = "VMkernel.Boot.cpuCellSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.debugBreak",
      summary = "Break into debugger during vmkernel initialization.",
      key = "VMkernel.Boot.debugBreak",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.dumpDiag",
      summary = "Dump diagnostics information.",
      key = "VMkernel.Boot.dumpDiag",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.executePOST",
      summary = "Run POST tests.",
      key = "VMkernel.Boot.executePOST",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fakeNUMAnodes",
      summary = "Fake # NUMA nodes on UMA systems.",
      key = "VMkernel.Boot.fakeNUMAnodes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fastHzEstimate",
      summary = "Use ACPI PM timer for frequency estimation at boot.",
      key = "VMkernel.Boot.fastHzEstimate",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.forceCRS",
      summary = "Always use IRQ from _CRS",
      key = "VMkernel.Boot.forceCRS",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fsCheck",
      summary = "Run filesystem checks on system partitions.",
      key = "VMkernel.Boot.fsCheck",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.hyperthreading",
      summary = "Enable hyperthreading if available.",
      key = "VMkernel.Boot.hyperthreading",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.ioapic",
      summary = "Use IOAPICs.",
      key = "VMkernel.Boot.ioapic",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logOnScreen",
      summary = "Display vmkernel log on screen.",
      key = "VMkernel.Boot.logOnScreen",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logSynchronous",
      summary = "Print log messages to screen and/or serial port synchronously.",
      key = "VMkernel.Boot.logSynchronous",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logicalApicId",
      summary = "Use logical not physical APIC IDs.",
      key = "VMkernel.Boot.logicalApicId",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.maxPCPUS",
      summary = "Number of PCPUs vmkernel should use.",
      key = "VMkernel.Boot.maxPCPUS",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memCheckEveryWord",
      summary = "Check every single word when checking mem.",
      key = "VMkernel.Boot.memCheckEveryWord",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      summary = "Maximum physical memory (in MB) recognized by kernel",
      key = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 262144,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memmapStressHighBitMPNs",
      summary = "Test &gt; 64GB physical RAM support by ignoring 4GB - 64GB range",
      key = "VMkernel.Boot.memmapStressHighBitMPNs",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.mpsIntRouting",
      summary = "Use MPS interrupt routing.",
      key = "VMkernel.Boot.mpsIntRouting",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netESX2LegacyMode",
      summary = "ESX2 Legacy networking config compatability.",
      key = "VMkernel.Boot.netESX2LegacyMode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      summary = "Maximum number of pkt buffers queued in each PCPU slab cache.",
      key = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNetqueueEnabled",
      summary = "Enable/Disable NetQueue support.",
      key = "VMkernel.Boot.netNetqueueEnabled",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNumGPBuffers",
      summary = "Number of general purpose buffers to allocate up front.",
      key = "VMkernel.Boot.netNumGPBuffers",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNumPortsets",
      summary = "Maximum number of portsets.",
      key = "VMkernel.Boot.netNumPortsets",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPanicBadDevOpen",
      summary = "panic if device has a bad open handler.",
      key = "VMkernel.Boot.netPanicBadDevOpen",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktBufUseSlab",
      summary = "Whether to allocate PktBufDescriptor from the pkt slab allocator.",
      key = "VMkernel.Boot.netPktBufUseSlab",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktHeapMaxSize",
      summary = "Maximum size in MB of the pkt buffer heap (advisory only).",
      key = "VMkernel.Boot.netPktHeapMaxSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktHeapMinSize",
      summary = "Minimum size in MB of the pkt buffer heap (advisory only).",
      key = "VMkernel.Boot.netPktHeapMinSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktNumSlabSizes",
      summary = "Number of different slab sizes for the allocator.",
      key = "VMkernel.Boot.netPktNumSlabSizes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netUseMemcpyNt",
      summary = "Enable/Disable non temporal memcpy in packet copy.",
      key = "VMkernel.Boot.netUseMemcpyNt",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netUseProc",
      summary = "Enable/Disable /proc nodes.",
      key = "VMkernel.Boot.netUseProc",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.oem",
      summary = "Enable OEM extensions.",
      key = "VMkernel.Boot.oem",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.overrideSerialPortAddr",
      summary = "UART I/O address",
      key = "VMkernel.Boot.overrideSerialPortAddr",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.pageSharing",
      summary = "Enable page sharing.",
      key = "VMkernel.Boot.pageSharing",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.panicOnVmkernelAbort",
      summary = "Panic if vmkernel aborts initialization.",
      key = "VMkernel.Boot.panicOnVmkernelAbort",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.realNMI",
      summary = "Use real NMI for LINT1.",
      key = "VMkernel.Boot.realNMI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.serialPort",
      summary = "0 = disable, 1 = COM1, 2 = COM2.",
      key = "VMkernel.Boot.serialPort",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.storageHeapMaxSize",
      summary = "Maximum size in bytes of the main storage heap",
      key = "VMkernel.Boot.storageHeapMaxSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.storageHeapMinSize",
      summary = "Minimum size in bytes of the main storage heap",
      key = "VMkernel.Boot.storageHeapMinSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.techSupportMode",
      summary = "Allow VMware Tech Support Mode access.",
      key = "VMkernel.Boot.techSupportMode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableACPI",
      summary = "Enable ACPI PM timer as system reference timer.",
      key = "VMkernel.Boot.timerEnableACPI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableHPET",
      summary = "Enable HPET as system reference timer.",
      key = "VMkernel.Boot.timerEnableHPET",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableMPMC",
      summary = "Enable Cyclone MPMC timer as system reference timer.",
      key = "VMkernel.Boot.timerEnableMPMC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableTSC",
      summary = "Enable TSC as system reference timer.",
      key = "VMkernel.Boot.timerEnableTSC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerForceTSC",
      summary = "Always use TSC as system reference timer.",
      key = "VMkernel.Boot.timerForceTSC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.usbBoot",
      summary = "Require USB boot if bootFS.",
      key = "VMkernel.Boot.usbBoot",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.useNUMAInfo",
      summary = "enable/disable NUMA-ness",
      key = "VMkernel.Boot.useNUMAInfo",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.useTSCForCPUHz",
      summary = "On systems where TSC and CPU frequencies are the same, determines whether to use TSC or the non-halted clock cycles MSR to determine CPU frequency.",
      key = "VMkernel.Boot.useTSCForCPUHz",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.uwSwap",
      summary = "Enable Userworld Swap.",
      key = "VMkernel.Boot.uwSwap",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.vmkKeyboard",
      summary = "Enable vmkernel keyboard driver.",
      key = "VMkernel.Boot.vmkKeyboard",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.vmkTerminals",
      summary = "Enable switching to vmkernel terminals.",
      key = "VMkernel.Boot.vmkTerminals",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.xapicAMDDetect",
      summary = "Detect xapic on opteron",
      key = "VMkernel.Boot.xapicAMDDetect",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.xapicForce",
      summary = "Force APIC ID to 8 bits",
      key = "VMkernel.Boot.xapicForce",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   }
 ]
 stop

example output ends

[[Category: Vimsh]]</text>
    <sha1>1227c10a1ec627b5bf7618d37c1e993d0255115a</sha1>
  </revision>
  <revision>
    <id>559</id>
    <parentid>558</parentid>
    <timestamp>2008-12-31T18:08:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>breaking it up on another part to fix the rendering issue</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155953" xml:space="preserve">==== vimsh hostsvc/advopt/options ====
Usage: Get the list of all supported options.
==== example output ====
Attached is some example output from a pristine ESX3.5i host.

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/advopt/options
 (vim.option.OptionDef) [
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RoutingPolicy",
      summary = "policy for interrupt routing, 1 for idle-routing, 2 for greedy routing, 0 to disable moving IRQs",
      key = "Irq.RoutingPolicy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BestVcpuRouting",
      summary = "",
      key = "Irq.BestVcpuRouting",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IRQRebalancePeriod",
      summary = "time in ms between attempts to rebalance interrupts",
      key = "Irq.IRQRebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 20000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IRQMaxLoadPct",
      summary = "maximum percentage of a cpu's resources that should be devoted to interrupts",
      key = "Irq.IRQMaxLoadPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 70,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogToFile",
      summary = "Send vmkernel log messages to /var/log/vmkernel",
      key = "Misc.LogToFile",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogToSerial",
      summary = "Send vmkernel log messages to the serial port",
      key = "Misc.LogToSerial",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogWldPrefix",
      summary = "Including running world on every log statement",
      key = "Misc.LogWldPrefix",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinimalPanic",
      summary = "Don't attempt to coredump after PSODing",
      key = "Misc.MinimalPanic",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BlueScreenTimeout",
      summary = "timeout in seconds, 0 is no timeout",
      key = "Misc.BlueScreenTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 65535,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatTimeout",
      summary = "Timeout in seconds, for sending NMI to the locked CPU",
      key = "Misc.HeartbeatTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatInterval",
      summary = "Interval in msec to check CPU lockups",
      key = "Misc.HeartbeatInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 86400000,
         defaultValue = 10000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatPanicTimeout",
      summary = "Interval in seconds after which to panic if no heartbeats received",
      key = "Misc.HeartbeatPanicTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatAnyPcpuPanic",
      summary = "Should we panic on any cpu lockups? (default we panic only for COS)",
      key = "Misc.HeartbeatAnyPcpuPanic",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MCEMonitorInterval",
      summary = "Interval[1 - 0x0xffffffff secs] to check Machine Check Errors",
      key = "Misc.MCEMonitorInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = -1,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DebugMemEnable",
      summary = "Enable memory debugging, 0 to disable",
      key = "Misc.DebugMemEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DebugBuddyEnable",
      summary = "Enable buddy debugging, 0 to disable",
      key = "Misc.DebugBuddyEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableHighDMA",
      summary = "Enable DMA above 4GB",
      key = "Misc.EnableHighDMA",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMinHardPeriod",
      summary = "Minimum hard timer interrupt period in microseconds",
      key = "Misc.TimerMinHardPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMaxHardPeriod",
      summary = "Maximum hard timer interrupt period in microseconds",
      key = "Misc.TimerMaxHardPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimerMinGuestPeriod",
      summary = "Minimum period for guest timer callbacks in microseconds",
      key = "Misc.TimerMinGuestPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 1000000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemAdmitMapEntriesMin",
      summary = "free KVMap entries required to power on VM",
      key = "Misc.MemAdmitMapEntriesMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemMapEntriesLow",
      summary = "Point at which to start conserving KVMap entries",
      key = "Misc.MemMapEntriesLow",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1024,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "KVMapGuardUncached",
      summary = "use guard pages around uncached kvmap mappings",
      key = "Misc.KVMapGuardUncached",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SerialPort",
      summary = "Which serial port (1 or 2) to use for logging, or 0 for neither.",
      key = "Misc.SerialPort",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SerialBaudRate",
      summary = "Baud rate",
      key = "Misc.SerialBaudRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 9600,
         max = 115200,
         defaultValue = 115200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "WatchdogBacktrace",
      summary = "Backtrace on every nth watchdog",
      key = "Misc.WatchdogBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BHTimeout",
      summary = "Timeout for bottom-half handlers in milliseconds",
      key = "Misc.BHTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BhTimeBound",
      summary = "Time bound on BH checking in us (microseconds).",
      key = "Misc.BhTimeBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 500000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IntTimeout",
      summary = "Timeout for interrupt handlers in milliseconds",
      key = "Misc.IntTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RunningVCpuLimit",
      summary = "The limit for the number of VCPUs",
      key = "Misc.RunningVCpuLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1024,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HordeEnabled",
      summary = "Enables horde mode",
      key = "Misc.HordeEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AckActual",
      summary = "Ack actual end",
      key = "Misc.AckActual",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NoWaitOnSocket",
      summary = "Don't wait on socket",
      key = "Misc.NoWaitOnSocket",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScreenSaverDelay",
      summary = "Delay in minutes before screensaver kicks in",
      key = "Misc.ScreenSaverDelay",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 60,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimEnabled",
      summary = "Enable CIM Service",
      key = "Misc.CimEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimOemProvidersEnabled",
      summary = "Enable OEM Providers",
      key = "Misc.CimOemProvidersEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimIHVProvidersEnabled",
      summary = "Enable IHV Providers",
      key = "Misc.CimIHVProvidersEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CimWatchdogInterval",
      summary = "Seconds of delay between sfcbd poll",
      key = "Misc.CimWatchdogInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "FSSLightWeightProbe",
      summary = "Enable light-weight efficient probe of ESX supported datastores",
      key = "Misc.FSSLightWeightProbe",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ProcVerbose",
      summary = "option unused",
      key = "Misc.ProcVerbose",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPortRxQueueLen",
      summary = "Max length of the rx queue for virtual ports whose clients support queueing.",
      key = "Net.MaxPortRxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 500,
         defaultValue = 80,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxNetifRxQueueLen",
      summary = "Max length of the rx queue for the physical NICs.",
      key = "Net.MaxNetifRxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxNetifTxQueueLen",
      summary = "Max length of the tx queue for the physical NICs.",
      key = "Net.MaxNetifTxQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "GuestTxCopyBreak",
      summary = "transmits smaller than this will be copied rather than mapped.",
      key = "Net.GuestTxCopyBreak",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = -1,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VmxnetTxCopySize",
      summary = "vmxnet tx &lt;= than this will be fully copied with no need for completion.",
      key = "Net.VmxnetTxCopySize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = -1,
         defaultValue = 256,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VmxnetWinUDPTxFullCopy",
      summary = "whether Windows vmxnet UDP tx is fullCopy.",
      key = "Net.VmxnetWinUDPTxFullCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseProc",
      summary = "whether or not to populate /proc/vmware/net. [0 = disabled, 1 = enabled]",
      key = "Net.UseProc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseLegacyProc",
      summary = "whether or not to populate legacy entries in /proc/vmware/net. [0 = disabled, 1 = enabled]",
      key = "Net.UseLegacyProc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NotifySwitch",
      summary = "Broadcasts an arp request on net handle enable. [0 = disabled, 1 = enabled]",
      key = "Net.NotifySwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetTxDontClusterSize",
      summary = "transmits smaller than this will not be subject to clustering/coalescing.",
      key = "Net.NetTxDontClusterSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8192,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetPktAllocTries",
      summary = "Number of tries for allocating pkt within the page.",
      key = "Net.NetPktAllocTries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceTxTimeout",
      summary = "set the coalesce timeout in micro-seconds.",
      key = "Net.CoalesceTxTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = -1,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceDefaultOn",
      summary = "whether dynamic coalescing is on by default. [0 = disabled by default, 1 = enabled by default]",
      key = "Net.CoalesceDefaultOn",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceLowTxMsRate",
      summary = "No tx coalescing calibration when the number of pkts tx per ms is lower than this number.",
      key = "Net.CoalesceLowTxMsRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 64,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceLowRxMsRate",
      summary = "No rx coalescing calibration when the number of pkts rx per ms is lower than this number.",
      key = "Net.CoalesceLowRxMsRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 64,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceHandlerPcpu",
      summary = "Pcpu that coalesce timeout handler runs on.",
      key = "Net.CoalesceHandlerPcpu",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoalesceTxAlwaysPoll",
      summary = "Whether always poll Tx at coalesce timeout handler.",
      key = "Net.CoalesceTxAlwaysPoll",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "vmxnetBHNetPoll",
      summary = "Whether to poll for Tx in BH NetPoll.",
      key = "Net.vmxnetBHNetPoll",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "vmxnetThroughputWeight",
      summary = "How far to favor throughput in vmxnet behavior.",
      key = "Net.vmxnetThroughputWeight",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EtherswitchHashSize",
      summary = "number of ports on the switch x 2^N is the size of the hash table for looking up MACs.",
      key = "Net.EtherswitchHashSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NoLocalCSum",
      summary = "if set, don't bother checksumming local tx/rx frames.",
      key = "Net.NoLocalCSum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortSerializeInput",
      summary = "if enabled(1), input into port through appropriate calls are serialized to prevent out-of-order delivery.",
      key = "Net.PortSerializeInput",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortFlushIterLimit",
      summary = "when input is serialized, this bounds the number of times a thread flushes the deferred list.",
      key = "Net.PortFlushIterLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 127,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortFlushPktLimit",
      summary = "when input is serialized, this bounds the number of pkts a thread flushes from the deferred list.",
      key = "Net.PortFlushPktLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortTrackTxRace",
      summary = "if enabled(1), collect statistics on potential tx race between concurrent threads.",
      key = "Net.PortTrackTxRace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortKeepDetailedStats",
      summary = "if enabled(1), collect detailed statistics on port.",
      key = "Net.PortKeepDetailedStats",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PortDisableTimeout",
      summary = "max timeout delay to wait for ports to complete I/O before disabling.",
      key = "Net.PortDisableTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipHeapSize",
      summary = "Initial size of the tcpip module heap in megabytes. (REQUIRES REBOOT!)",
      key = "Net.TcpipHeapSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 6,
         max = 30,
         defaultValue = 9,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipHeapMax",
      summary = "Max megabytes the tcpip module heap can grow to. (REQUIRES REBOOT!)",
      key = "Net.TcpipHeapMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 120,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPageInQueueLen",
      summary = "maximum number of pageing requests to queue for guest DMA.",
      key = "Net.MaxPageInQueueLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxBeaconsAtOnce",
      summary = "maximum number of beacons to send in one beacon cycle.",
      key = "Net.MaxBeaconsAtOnce",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4096,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxBeaconVlans",
      summary = "maximum number of VLANs to probe with beacons.",
      key = "Net.MaxBeaconVlans",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 4096,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipNoBcopyRx",
      summary = "Avoid bcopy in tcp rx.",
      key = "Net.TcpipNoBcopyRx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipCopySmallTx",
      summary = "Copy and tx complete small packets for tcp tx.",
      key = "Net.TcpipCopySmallTx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipLargeRx",
      summary = "Allow frames larger than mtu for tcp rx.",
      key = "Net.TcpipLargeRx",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipMaxPktInFlight",
      summary = "Maximum zero copy mbuf packet in flight.",
      key = "Net.TcpipMaxPktInFlight",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipDelayedAck",
      summary = "Enable/Disable delayed ACKs.",
      key = "Net.TcpipDelayedAck",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LinkStatePollTimeout",
      summary = "Link State poll timer period in milliseconds.",
      key = "Net.LinkStatePollTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 90000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipUseIoat",
      summary = "Use IOAT chipset if present. (REQUIRES REBOOT!)",
      key = "Net.TcpipUseIoat",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TcpipIoatAlwaysWakeup",
      summary = "Wakeup soreceive thread on every tcp packet (for IOAT only).",
      key = "Net.TcpipIoatAlwaysWakeup",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "E1000TxZeroCopy",
      summary = "Use tx zero copy for non-tso packets for e1000.",
      key = "Net.E1000TxZeroCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "E1000TxTsoZeroCopy",
      summary = "Use tx zero copy for tso packets for e1000.",
      key = "Net.E1000TxTsoZeroCopy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinEtherLen",
      summary = "Minimum size ethernet frame to transmit.",
      key = "Net.MinEtherLen",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1518,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxPktRxListQueue",
      summary = "Maximum packet we can queue in rxList.",
      key = "Net.MaxPktRxListQueue",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 3500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxWorkBound",
      summary = "Maximum rx pkts processed in one NetBH invocation.",
      key = "Net.NetBHRxWorkBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 320,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxInputBound",
      summary = "Maximum rx pkts sent up an uplink at one go.",
      key = "Net.NetBHRxInputBound",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetBHRxStormThreshold",
      summary = "Declare Rx Storm after this number of consecutive rx pkt drops during queuing in NetBH rxList.",
      key = "Net.NetBHRxStormThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200000,
         defaultValue = 320,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReversePathFwdCheck",
      summary = "Block the multicast/broadcast packets that come back from physical switches in a teamed environment.",
      key = "Net.ReversePathFwdCheck",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllowPromiscFilters",
      summary = "Block duplicate multicast/broadcast packet in a teamed environment when the virtual switch is set to Promiscuous mode.",
      key = "Net.AllowPromiscFilters",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Vmxnet2PinRxBuf",
      summary = "Pin RX buffers for vmxnet2 clients. (windows guest only)",
      key = "Net.Vmxnet2PinRxBuf",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TsoDumpPkt",
      summary = "detailed dump of every &lt;n&gt; pkts.",
      key = "Net.TsoDumpPkt",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPVersion",
      summary = "IGMP Version (2 or 3).",
      key = "Net.IGMPVersion",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 2,
         max = 3,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPQueries",
      summary = "Number of IGMP Queries to send during after VMotion/Teaming failover.",
      key = "Net.IGMPQueries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NcpLlcSap",
      summary = "beacon/color NCP messages created with this SAP (DSAP/SSAP)",
      key = "Net.NcpLlcSap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IGMPRouterIP",
      summary = "Router IP Address for IGMP (generally not necessary to set this).",
      key = "Net.IGMPRouterIP",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "10.0.0.0",
         validCharacters = "10.0.0.0",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BalancePeriod",
      summary = "period in seconds, 0 to disable",
      key = "Mem.BalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 120,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SamplePeriod",
      summary = "period in seconds, 0 to disable",
      key = "Mem.SamplePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 180,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdleTax",
      summary = "idle memory tax rate",
      key = "Mem.IdleTax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 99,
         defaultValue = 75,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdleTaxType",
      summary = "idle tax type. 0=flat, 1=variable",
      key = "Mem.IdleTaxType",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SampleActivePctMin",
      summary = "lower bound for sampled active memory",
      key = "Mem.SampleActivePctMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareScanGHz",
      summary = "max page scan rate in MB/sec per GHz of host CPU, 0 to disable",
      key = "Mem.ShareScanGHz",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareScanTime",
      summary = "desired time in minutes to scan entire VM",
      key = "Mem.ShareScanTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 600,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareRateMax",
      summary = "per-VM upper limit on pshare scan/check rate in pages/sec. (0 to disable)",
      key = "Mem.ShareRateMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 32768,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CtlMaxPercent",
      summary = "vmmemctl limit as percentage of VM max size",
      key = "Mem.CtlMaxPercent",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 75,
         defaultValue = 65,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocHighThreshold",
      summary = "Threshold (in MB) at which we start allocating memory above 4GB",
      key = "Mem.AllocHighThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 4096,
         defaultValue = 1500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocGuestLargePage",
      summary = "Enable large page backing of guest memory",
      key = "Mem.AllocGuestLargePage",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocUsePSharePool",
      summary = "Use pshare pool to allocate memory for shared pages",
      key = "Mem.AllocUsePSharePool",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AllocUseGuestPool",
      summary = "Use large page pool to allocate memory for guest pages",
      key = "Mem.AllocUseGuestPool",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AdmitHeapMin",
      summary = "free heap space required to power on VM, in KB",
      key = "Mem.AdmitHeapMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 256,
         max = 10240,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MinFreePct",
      summary = "Minimum percent of memory that should be kept free",
      key = "Mem.MinFreePct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 6,
         max = 24,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareCOSBufSize",
      summary = "Specify number of MPNs to be used by COW P2M buffer",
      key = "Mem.ShareCOSBufSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 2,
         max = 8,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapIORetry",
      summary = "Number of retries for swap-in operation on I/O failures",
      key = "Mem.SwapIORetry",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TestOnAlloc",
      summary = "Check the newly allocated page for Memory Errors",
      key = "Mem.TestOnAlloc",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimatePeriod",
      summary = "Sleep interval for pshare-est daemon world",
      key = "Mem.ShareEstimatePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 300000,
         defaultValue = 30000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimateProbe",
      summary = "Maximum per-VM page probes for pshare estimation",
      key = "Mem.ShareEstimateProbe",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 5000,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ShareEstimateSamples",
      summary = "Minimum required per-VM page samples for pshare estimation",
      key = "Mem.ShareEstimateSamples",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 100,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "kernelResvPad",
      summary = "Extra padding (in MB) for MemSched's tracking of kernel memory usage",
      key = "Mem.kernelResvPad",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 128,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogLowMemoryStateUsage",
      summary = "Log memory usage of memclients during low memory state",
      key = "Mem.LogLowMemoryStateUsage",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogLowMemoryStateBT",
      summary = "Log back-trace of contexts that allocate MPNs during low memory state",
      key = "Mem.LogLowMemoryStateBT",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapDecayPct",
      summary = "Percentage of swap target to be proactively transferred to balloon target",
      key = "Mem.SwapDecayPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DesiredAllocEnable",
      summary = "Enable use of desired allocations when computing allocation targets",
      key = "Mem.DesiredAllocEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DesiredAllocPct",
      summary = "Percentage of consumed memory to be considered as the desired allocation target",
      key = "Mem.DesiredAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 200,
         defaultValue = 125,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BonusAllocPct",
      summary = "Percentage of group allocation to be distributed to children as bonus",
      key = "Mem.BonusAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapFilePersist",
      summary = "The swap file is not deleted when the VM powers off, 1 to enable",
      key = "Mem.SwapFilePersist",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapInBatchPages",
      summary = "Number of pages swapped in per batch during opportunistic prefaulting",
      key = "Mem.SwapInBatchPages",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 512,
         defaultValue = 64,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapAsyncWritePages",
      summary = "Maximum allowed pending asynchronous swapout requests per VM",
      key = "Mem.SwapAsyncWritePages",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 16,
         max = 64,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HostLocalSwapDirEnabled",
      summary = "Enable use of host-local swap directory",
      key = "Mem.HostLocalSwapDirEnabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageAllocAllowance",
      summary = "Memory alloc allowance (in 4K pages) while usage is tracked via heartbeat or swap action post",
      key = "Mem.TrackUsageAllocAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 4096,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageSwapAllowance",
      summary = "Memory swap allowance (in 4K pages) while usage is tracked via heartbeat or swap action post",
      key = "Mem.TrackUsageSwapAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 4096,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageLPageAllowance",
      summary = "Memory large page alloc allowance (in 2M pages) while usage is tracked via heartbeat action post",
      key = "Mem.TrackUsageLPageAllowance",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageHeartbeatPeriod",
      summary = "Sleep interval in seconds for busmem heartbeat",
      key = "Mem.TrackUsageHeartbeatPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 300,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TrackUsageHeartbeatEnable",
      summary = "Enable/disable MPN usage tracking via heartbeat monitor action (0 for disable)",
      key = "Mem.TrackUsageHeartbeatEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMOverheadGrowthLimit",
      summary = "Default limit (in MB) on VM overhead memory growth",
      key = "Mem.VMOverheadGrowthLimit",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = -1,
         defaultValue = -1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HostLocalSwapDir",
      summary = "Host-local directory for VM swap files",
      key = "Mem.HostLocalSwapDir",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigratePeriod",
      summary = "milliseconds between opportunities to migrate across cpus",
      key = "Cpu.MigratePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CellMigratePeriod",
      summary = "milliseconds between opportunities to migrate across cells",
      key = "Cpu.CellMigratePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 60000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "WakeupMigrateIdle",
      summary = "migrate to idle package on wakeup, 0 to disable",
      key = "Cpu.WakeupMigrateIdle",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PcpuMigrateIdle",
      summary = "always migrate from remote pcpus when a core becomes idle, 0 to disable",
      key = "Cpu.PcpuMigrateIdle",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CreditAgePeriod",
      summary = "period in milliseconds",
      key = "Cpu.CreditAgePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 10000,
         defaultValue = 3000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BoundLagQuanta",
      summary = "number of global quanta before bound lag",
      key = "Cpu.BoundLagQuanta",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 100,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CacheStats",
      summary = "enable per-world cache data collection",
      key = "Cpu.CacheStats",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Quantum",
      summary = "quantum in milliseconds",
      key = "Cpu.Quantum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewPollUsec",
      summary = "interval between coscheduling skew checks, in usec",
      key = "Cpu.SkewPollUsec",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 5000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewInstanceThreshold",
      summary = "maximum individual skew between vcpus in usec, 0 to disable",
      key = "Cpu.SkewInstanceThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SkewCumulativeThreshold",
      summary = "maximum cumulative skew between vcpus in usec, 0 to disable",
      key = "Cpu.SkewCumulativeThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IdlePackageRebalancePeriod",
      summary = "usec between chances to rebalance idle packages (0 to disable, 100000 max)",
      key = "Cpu.IdlePackageRebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 541,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IntraCoreMigrate",
      summary = " When to allow intra-core migrations [0:when inter-core migration allowed, 1:always]",
      key = "Cpu.IntraCoreMigrate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMotionMinAllocPct",
      summary = "Per-VM minimum CPU allocations (in %) for VMotion requirements",
      key = "Cpu.VMotionMinAllocPct",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 200,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMAdmitCheckPerVcpuMin",
      summary = "Perform additional admission control check that per vcpu VM cpu min does not exceed the speed of a single physical  cpu. [0:dis",
      key = "Cpu.VMAdmitCheckPerVcpuMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },

   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CoSchedIdleBalancePeriod",
      summary = "millisecs between opportunities to move co-scheduled vcpus to more idle cores and packages, 0 to disable",
      key = "Cpu.CoSchedIdleBalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalancePeriod",
      summary = "frequency of NUMA node rebalancing, in milliseconds",
      key = "Numa.RebalancePeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 60000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigImbalanceThreshold",
      summary = "minimum percent load imbalance between nodes to trigger migration",
      key = "Numa.MigImbalanceThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 200,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigThreshold",
      summary = "minimum percent load balance improvement to allow single migration/swap",
      key = "Numa.MigThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MigThrashThreshold",
      summary = "maximum post-migration load imbalance, as percentage of pre-migration imbalance, to prevent thrashing",
      key = "Numa.MigThrashThreshold",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapLoadEnable",
      summary = "1 to enable VM swaps across nodes to balance CPU load, 0 to disable",
      key = "Numa.SwapLoadEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SwapLocalityEnable",
      summary = "1 to enable VM swaps across nodes to improve memory locality, 0 to disable",
      key = "Numa.SwapLocalityEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceEnable",
      summary = "1 to enable NUMA rebalancer, 0 to disable it",
      key = "Numa.RebalanceEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceCoresTotal",
      summary = "minimum number of total host cores required to enable NUMA rebalancer",
      key = "Numa.RebalanceCoresTotal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 32,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RebalanceCoresNode",
      summary = "minimum number of cores per node required to enable NUMA rebalancer",
      key = "Numa.RebalanceCoresNode",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 8,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MonMigEnable",
      summary = "1 to allow NUMASched monitor migrations, 0 to disallow",
      key = "Numa.MonMigEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "AutoMemAffinity",
      summary = "1 to set mem affinity automatically based on cpu affinity, 0 to disable",
      key = "Numa.AutoMemAffinity",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageMigEnable",
      summary = "1 to permit NUMASched to manipulate page migration, 0 to disallow it",
      key = "Numa.PageMigEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PostMigUseActiveMetric",
      summary = "1 to use alternative migActive metric for post-migration imbalance prediction, 0 to use default migEntitlement metric",
      key = "Numa.PostMigUseActiveMetric",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragEnable",
      summary = "Enable large page defragmentation",
      key = "LPage.LPageDefragEnable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageMarkLowNodes",
      summary = "Enable marking of nodes with low large pages free",
      key = "LPage.LPageMarkLowNodes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragRateVM",
      summary = "Maximum number of lpage defrag attempts per second per VM",
      key = "LPage.LPageDefragRateVM",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageDefragRateTotal",
      summary = "Maximum number of lpage defrag attempts per second ",
      key = "LPage.LPageDefragRateTotal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10240,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LPageAlwaysTryForNPT",
      summary = "Enable always try to alloc large page for NPT",
      key = "LPage.LPageAlwaysTryForNPT",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesNormal",
      summary = "shares for normal/default disk priority",
      key = "Disk.SharesNormal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesHigh",
      summary = "shares for high disk priority",
      key = "Disk.SharesHigh",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SharesLow",
      summary = "shares for low disk priority",
      key = "Disk.SharesLow",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 10000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "BandwidthCap",
      summary = "cap on disk bandwidth (Kb/s) usage",
      key = "Disk.BandwidthCap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 2147483647,
         defaultValue = 2147483647,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ThroughputCap",
      summary = "cap on disk throughput (IO/S) usage",
      key = "Disk.ThroughputCap",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 2147483647,
         defaultValue = 2147483647,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SectorMaxDiff",
      summary = "Distance in sectors at which disk BW sched affinity stops",
      key = "Disk.SectorMaxDiff",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2000000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQuantum",
      summary = "Number of consecutive requests from one World",
      key = "Disk.SchedQuantum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 64,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedNumReqOutstanding",
      summary = "Number of outstanding commands to a target with competing worlds",
      key = "Disk.SchedNumReqOutstanding",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQControlSeqReqs",
      summary = "Number of consecutive requests from a VM required to raise the outstanding commands to max",
      key = "Disk.SchedQControlSeqReqs",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2048,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SchedQControlVMSwitches",
      summary = "Number of switches between commands issued by different VMs required to reduce outstanding commands to SchedNumReqOutstanding",
      key = "Disk.SchedQControlVMSwitches",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2048,
         defaultValue = 6,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxLUN",
      summary = "Maximum LUN id that is scanned on a target",
      key = "Disk.MaxLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 256,
         defaultValue = 256,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SupportSparseLUN",
      summary = "Support for sparse LUNs if set to one",
      key = "Disk.SupportSparseLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseReportLUN",
      summary = "Use the REPORT LUN command to speed up scanning for devices",
      key = "Disk.UseReportLUN",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseDeviceReset",
      summary = "Use device reset (instead of bus reset) to reset a SCSI device",
      key = "Disk.UseDeviceReset",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UseLunReset",
      summary = "Use LUN reset (instead of device/bus reset) to reset a SCSI device",
      key = "Disk.UseLunReset",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "RetryUnitAttention",
      summary = "Retry all SCSI commands that return a unit attention error",
      key = "Disk.RetryUnitAttention",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetOnFailover",
      summary = "Issue a SCSI reset when failing over to an alternate HBA",
      key = "Disk.ResetOnFailover",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PathEvalTime",
      summary = "The number of seconds between FC path evaluations",
      key = "Disk.PathEvalTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 1500,
         defaultValue = 300,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxVCNotReadyTime",
      summary = "The number of seconds a VC path can report NOT READY status before being declared dead",
      key = "Disk.MaxVCNotReadyTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 15,
         max = 90,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxDS400NotReadyTime",
      summary = "The number of seconds a DS400 path can report IN TRANSITION before being declared dead",
      key = "Disk.MaxDS400NotReadyTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 15,
         max = 90,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableNaviReg",
      summary = "Enable automatic NaviAgent registration with CLARiiON and Invista (vmvisor only)",
      key = "Disk.EnableNaviReg",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DelayOnBusy",
      summary = "Delay in milliseconds for completion of commands with a BUSY status",
      key = "Disk.DelayOnBusy",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 5000,
         defaultValue = 400,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetLatency",
      summary = "Delay in milliseconds between reset thread wake-ups",
      key = "Disk.ResetLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 600000,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxResetLatency",
      summary = "Delay in milliseconds before logging warnings and spawning new reset worlds if a reset is overdue or taking too long",
      key = "Disk.MaxResetLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 500,
         max = 600000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetPeriod",
      summary = "Delay in seconds between bus resets retries",
      key = "Disk.ResetPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 3600,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetMaxRetries",
      summary = "Max number of bus reset retries (0=infinite)",
      key = "Disk.ResetMaxRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 10000,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadMin",
      summary = "Min number of reset handler threads",
      key = "Disk.ResetThreadMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadMax",
      summary = "Max number of reset handler threads",
      key = "Disk.ResetThreadMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetThreadExpires",
      summary = "Life in seconds of an inactive reset handle thread",
      key = "Disk.ResetThreadExpires",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ResetOverdueLogPeriod",
      summary = "Delay in seconds between logs of overdue reset",
      key = "Disk.ResetOverdueLogPeriod",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 86400,
         defaultValue = 60,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SPBlksToSwitch",
      summary = "Number of blocks of I/O sent over a given path before a path switch (0=infinite)",
      key = "Disk.SPBlksToSwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000000,
         defaultValue = 2048,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SPCmdsToSwitch",
      summary = "Number of I/O commands sent over a given path before a path switch (0=infinite) ",
      key = "Disk.SPCmdsToSwitch",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000000,
         defaultValue = 50,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreventVMFSOverwrite",
      summary = "Prevent Console OS from overwriting VMFS partitions",
      key = "Disk.PreventVMFSOverwrite",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DumpMaxRetries",
      summary = "Max number of I/O retries during disk dump",
      key = "Disk.DumpMaxRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1000,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DiskMaxIOSize",
      summary = "Max Disk READ/WRITE I/O size before splitting (in KB)",
      key = "Disk.DiskMaxIOSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 32767,
         defaultValue = 32767,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaskLUNs",
      summary = "LUN's to mask from kernel. Format: &lt;adapter&gt;:&lt;target&gt;:&lt;comma separated LUN range list&gt;",
      key = "Disk.MaskLUNs",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SANDevicesWithAPFailover",
      summary = "SAN devices with Active/Passive Path Failover. Format: &lt;16 Character Device Id&gt;:&lt;16 Character Device Id&gt;:...",
      key = "Disk.SANDevicesWithAPFailover",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "**",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Enabled",
      summary = "Enable hot migration support",
      key = "Migrate.Enabled",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreCopyLeftMB",
      summary = "Maximum modified memory left over after pre-copy is done",
      key = "Migrate.PreCopyLeftMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PreCopyMinProgressMB",
      summary = "Minimum reduction in modified memory after a pre-copy iteration",
      key = "Migrate.PreCopyMinProgressMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 1024,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "NetTimeout",
      summary = "Timeout for migration network operations",
      key = "Migrate.NetTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 3600,
         defaultValue = 20,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MemChksum",
      summary = "Checksum VM's memory while migrating",
      key = "Migrate.MemChksum",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TSMaster",
      summary = "Pseudo-synchronize clocks for migration to/from this machine",
      key = "Migrate.TSMaster",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInTimeout",
      summary = "Time in seconds to wait for page-in to finish",
      key = "Migrate.PageInTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 10,
         max = 18000,
         defaultValue = 100,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInTimeoutResetOnProgress",
      summary = "Page-in progess will reset the page-in timeout",
      key = "Migrate.PageInTimeoutResetOnProgress",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInProgress",
      summary = "Time in seconds after which a page-in will be killed if there is no progress",
      key = "Migrate.PageInProgress",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 18000,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PageInBeforeResume",
      summary = "Wait for page-in to finish before resuming on the dest",
      key = "Migrate.PageInBeforeResume",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PassthroughLocking",
      summary = "Disable locking for scsi passthrough devices",
      key = "Scsi.PassthroughLocking",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ConflictRetries",
      summary = "Maximum number of retries when encountering reservation conflict.",
      key = "Scsi.ConflictRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 200,
         defaultValue = 80,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogMultiPath",
      summary = "Log path state changes",
      key = "Scsi.LogMultiPath",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LogAborts",
      summary = "Log timing of aborted or reseted IOs",
      key = "Scsi.LogAborts",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PrintCmdErrors",
      summary = "Print the error to log on a SCSI command error.",
      key = "Scsi.PrintCmdErrors",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveTime",
      summary = "Maximum time (in msecs) a system-initiated reservation is normally held (debug only)",
      key = "Scsi.MaxReserveTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 50,
         max = 500,
         defaultValue = 200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveTotalTime",
      summary = "Maximum time (in msecs) a system-initiated reservation normally takes from issue to release (debug only)",
      key = "Scsi.MaxReserveTotalTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 50,
         max = 500,
         defaultValue = 250,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxReserveBacktrace",
      summary = "Log a backtrace if caller exceeds SCSI_MAX_RESERVE_TIME or SCSI_MAX_RESERVE_TOTALTIME (debug only)",
      key = "Scsi.MaxReserveBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReserveBacktrace",
      summary = "Log a backtrace for all Reserve/Release pairs (debug only)",
      key = "Scsi.ReserveBacktrace",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SCSITimeout_ScanTime",
      summary = "time (in ms) to sleep between checking for timed-out async IO",
      key = "Scsi.SCSITimeout_ScanTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 99999999,
         defaultValue = 1000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SCSITimeout_ReabortTime",
      summary = "delay (in ms) after an abort due to timeout before the abort is re-issued",
      key = "Scsi.SCSITimeout_ReabortTime",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 99999999,
         defaultValue = 5000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScanOnDriverLoad",
      summary = "Scan new SCSI buses on device driver load",
      key = "Scsi.ScanOnDriverLoad",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadMin",
      summary = "Min number of timeout task-mgmt handler threads",
      key = "Scsi.TimeoutTMThreadMin",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadMax",
      summary = "Max number of device task-mgmt handler threads",
      key = "Scsi.TimeoutTMThreadMax",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 16,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadExpires",
      summary = "Life in seconds of timeout task mgmt handler thread",
      key = "Scsi.TimeoutTMThreadExpires",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 86400,
         defaultValue = 1800,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadRetry",
      summary = "Delay in milliseconds before retrying failed timeout taskmgmt",
      key = "Scsi.TimeoutTMThreadRetry",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1000,
         max = 100000,
         defaultValue = 40000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "TimeoutTMThreadLatency",
      summary = "Delay in ms before waking up new task mgmt thread ",
      key = "Scsi.TimeoutTMThreadLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 600000,
         defaultValue = 2000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScsiRestartStalledQueueLatency",
      summary = "Delay in ms before restarting a stalled queue ",
      key = "Scsi.ScsiRestartStalledQueueLatency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 60000,
         defaultValue = 500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CompareLUNNumber",
      summary = "Consider LUN number when determining LUN identity.",
      key = "Scsi.CompareLUNNumber",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScsiRescanAllHbas",
      summary = "During esxcfg-rescan, rescan all vmhbas at once rather than just a single vmhba",
      key = "Scsi.ScsiRescanAllHbas",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReaddirRetries",
      summary = "Maximum number of retries when reading entries from directories",
      key = "User.ReaddirRetries",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 20,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "CDROMSenseTimeout",
      summary = "Physical CDROM sense timeout (seconds)",
      key = "User.CDROMSenseTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "PTEDisableNX",
      summary = "Disables the use of NX bit in user pagetable entries",
      key = "User.PTEDisableNX",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "IndirectSend",
      summary = "Use NFS indirect send",
      key = "NFS.IndirectSend",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DiskFileLockUpdateFreq",
      summary = "Time (in seconds) between updates to a disk lock file [8-3600]",
      key = "NFS.DiskFileLockUpdateFreq",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 8,
         max = 3600,
         defaultValue = 10,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockUpdateTimeout",
      summary = "Time (in seconds) before we abort an outstanding lock update",
      key = "NFS.LockUpdateTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 8,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockRenewMaxFailureNumber",
      summary = "Number of update failures before a disk file lock is declared stale",
      key = "NFS.LockRenewMaxFailureNumber",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "LockDisable",
      summary = "1 to disable NFS locking protocol",
      key = "NFS.LockDisable",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatFrequency",
      summary = "Time in seconds between heartbeats",
      key = "NFS.HeartbeatFrequency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 5,
         max = 86400,
         defaultValue = 9,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatTimeout",
      summary = "Time in seconds before we abort an outstanding hearbeat",
      key = "NFS.HeartbeatTimeout",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 3,
         max = 30,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatDelta",
      summary = "Time in seconds since the last successful update before we send a heartbeat",
      key = "NFS.HeartbeatDelta",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 3,
         max = 30,
         defaultValue = 5,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HeartbeatMaxFailures",
      summary = "Number of sequential failures before we mark a volume as down",
      key = "NFS.HeartbeatMaxFailures",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 10,
         defaultValue = 3,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxVolumes",
      summary = "Maximum number of mounted NFS volumes",
      key = "NFS.MaxVolumes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 8,
         max = 32,
         defaultValue = 8,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SendBufferSize",
      summary = "Default size of socket's send buffer in KB",
      key = "NFS.SendBufferSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 264,
         defaultValue = 264,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ReceiveBufferSize",
      summary = "Default Size of socket's receive buffer in KB",
      key = "NFS.ReceiveBufferSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 64,
         max = 264,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VolumeRemountFrequency",
      summary = "Time in seconds before attempting to remount a volume",
      key = "NFS.VolumeRemountFrequency",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 30,
         max = 3600,
         defaultValue = 30,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "UDPRetransmitDelay",
      summary = "Time in milliseconds retransmitting a UDP RPC",
      key = "NFS.UDPRetransmitDelay",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 2000,
         defaultValue = 700,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "OpenWithoutJournal",
      summary = "Open file system when out of space for journal allocation, allowing reads and no meta-data updates",
      key = "VMFS3.OpenWithoutJournal",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxHeapSizeMB",
      summary = "Maximum size (in MB) to which the VMFS-3 heap is allowed to grow",
      key = "VMFS3.MaxHeapSizeMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 16,
         max = 128,
         defaultValue = 16,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "SoftMaxDirty",
      summary = "Flush immediately if this many buffers are dirty (percent)",
      key = "BufferCache.SoftMaxDirty",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 15,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "HardMaxDirty",
      summary = "Block writers if this many buffers are dirty (percent)",
      key = "BufferCache.HardMaxDirty",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 100,
         defaultValue = 95,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "FlushInterval",
      summary = "Flush periodically at this interval (msec)",
      key = "BufferCache.FlushInterval",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 100,
         max = 3600000,
         defaultValue = 30000,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "EnableResignature",
      summary = "Enable Volume Resignaturing",
      key = "LVM.EnableResignature",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "DisallowSnapshotLun",
      summary = "Disallow access to snapshot LUN if resignaturing is off. This is ignored if resignaturing is on.",
      key = "LVM.DisallowSnapshotLun",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 1,
         defaultValue = 1,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxHeapSizeMB",
      summary = "Maximum size (in MB) to which the COW heap is allowed to grow",
      key = "COW.MaxHeapSizeMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 32,
         max = 192,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "MaxDentryPerObj",
      summary = "Maximum directory entries cached per directory",
      key = "DirentryCache.MaxDentryPerObj",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 60,
         max = 30000,
         defaultValue = 2500,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Annotations.WelcomeMessage",
      summary = "",
      key = "Annotations.WelcomeMessage",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.0.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.0.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.0.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.1.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.1.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.1.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000000.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000000.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000000.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },

   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000001.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000001.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000001.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.80000008.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.80000008.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.80000008.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.eax",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.eax; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.ebx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.ebx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.ecx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.ecx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.mode.8000000A.edx",
      summary = "Controls the use of Config.Defaults.cpuidMask.val.8000000A.edx; legal values "mask", "clobber", or "disable".",
      key = "Config.Defaults.cpuidMask.mode.8000000A.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "disable",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.eax",
      summary = "CPUID override that may be applied to level 0 register eax; controlled by Config.Defaults.cpuidMask.mode.0.eax.",
      key = "Config.Defaults.cpuidMask.val.0.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.ebx",
      summary = "CPUID override that may be applied to level 0 register ebx; controlled by Config.Defaults.cpuidMask.mode.0.ebx.",
      key = "Config.Defaults.cpuidMask.val.0.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.ecx",
      summary = "CPUID override that may be applied to level 0 register ecx; controlled by Config.Defaults.cpuidMask.mode.0.ecx.",
      key = "Config.Defaults.cpuidMask.val.0.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.0.edx",
      summary = "CPUID override that may be applied to level 0 register edx; controlled by Config.Defaults.cpuidMask.mode.0.edx.",
      key = "Config.Defaults.cpuidMask.val.0.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.eax",
      summary = "CPUID override that may be applied to level 1 register eax; controlled by Config.Defaults.cpuidMask.mode.1.eax.",
      key = "Config.Defaults.cpuidMask.val.1.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.ebx",
      summary = "CPUID override that may be applied to level 1 register ebx; controlled by Config.Defaults.cpuidMask.mode.1.ebx.",
      key = "Config.Defaults.cpuidMask.val.1.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.ecx",
      summary = "CPUID override that may be applied to level 1 register ecx; controlled by Config.Defaults.cpuidMask.mode.1.ecx.",
      key = "Config.Defaults.cpuidMask.val.1.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.1.edx",
      summary = "CPUID override that may be applied to level 1 register edx; controlled by Config.Defaults.cpuidMask.mode.1.edx.",
      key = "Config.Defaults.cpuidMask.val.1.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.eax",
      summary = "CPUID override that may be applied to level 80000000 register eax; controlled by Config.Defaults.cpuidMask.mode.80000000.eax.",
      key = "Config.Defaults.cpuidMask.val.80000000.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.ebx",
      summary = "CPUID override that may be applied to level 80000000 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000000.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000000.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.ecx",
      summary = "CPUID override that may be applied to level 80000000 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000000.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000000.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000000.edx",
      summary = "CPUID override that may be applied to level 80000000 register edx; controlled by Config.Defaults.cpuidMask.mode.80000000.edx.",
      key = "Config.Defaults.cpuidMask.val.80000000.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.eax",
      summary = "CPUID override that may be applied to level 80000001 register eax; controlled by Config.Defaults.cpuidMask.mode.80000001.eax.",
      key = "Config.Defaults.cpuidMask.val.80000001.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.ebx",
      summary = "CPUID override that may be applied to level 80000001 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000001.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000001.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.ecx",
      summary = "CPUID override that may be applied to level 80000001 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000001.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000001.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000001.edx",
      summary = "CPUID override that may be applied to level 80000001 register edx; controlled by Config.Defaults.cpuidMask.mode.80000001.edx.",
      key = "Config.Defaults.cpuidMask.val.80000001.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.eax",
      summary = "CPUID override that may be applied to level 80000008 register eax; controlled by Config.Defaults.cpuidMask.mode.80000008.eax.",
      key = "Config.Defaults.cpuidMask.val.80000008.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.ebx",
      summary = "CPUID override that may be applied to level 80000008 register ebx; controlled by Config.Defaults.cpuidMask.mode.80000008.ebx.",
      key = "Config.Defaults.cpuidMask.val.80000008.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.ecx",
      summary = "CPUID override that may be applied to level 80000008 register ecx; controlled by Config.Defaults.cpuidMask.mode.80000008.ecx.",
      key = "Config.Defaults.cpuidMask.val.80000008.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.80000008.edx",
      summary = "CPUID override that may be applied to level 80000008 register edx; controlled by Config.Defaults.cpuidMask.mode.80000008.edx.",
      key = "Config.Defaults.cpuidMask.val.80000008.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.eax",
      summary = "CPUID override that may be applied to level 8000000A register eax; controlled by Config.Defaults.cpuidMask.mode.8000000A.eax.",
      key = "Config.Defaults.cpuidMask.val.8000000A.eax",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.ebx",
      summary = "CPUID override that may be applied to level 8000000A register ebx; controlled by Config.Defaults.cpuidMask.mode.8000000A.ebx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.ebx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.ecx",
      summary = "CPUID override that may be applied to level 8000000A register ecx; controlled by Config.Defaults.cpuidMask.mode.8000000A.ecx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.ecx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "cpuidMask.val.8000000A.edx",
      summary = "CPUID override that may be applied to level 8000000A register edx; controlled by Config.Defaults.cpuidMask.mode.8000000A.edx.",
      key = "Config.Defaults.cpuidMask.val.8000000A.edx",
      optionType = (vim.option.StringOption) {
         dynamicType = "",
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = "",
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "security.host.ruissl",
      summary = "Require SSL to be used when communicating with the host over port 902.",
      key = "Config.Defaults.security.host.ruissl",
      optionType = (vim.option.BoolOption) {
         dynamicType = "",
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = "",
      label = "guest.commands.sharedPolicyRefCount",
      summary = "Reference count to enable guest operations.",
      key = "Config.GlobalSettings.guest.commands.sharedPolicyRefCount",
      optionType = (vim.option.IntOption) {
         dynamicType = "",
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.ConfiguredScratchLocation",
      summary = "The directory configured to be used for scratch space.Changes will take effect on next reboot.",
      key = "ScratchConfig.ConfiguredScratchLocation",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.ConfiguredSwapState",
      summary = "Whether userwold swap is configured to be enabledChanges will take effect on next reboot.",
      key = "ScratchConfig.ConfiguredSwapState",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = false,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.CurrentScratchLocation",
      summary = "The directory currently being used for scratch space",
      key = "ScratchConfig.CurrentScratchLocation",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = true,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "ScratchConfig.CurrentSwapState",
      summary = "Whether userworld swap is currently enabled",
      key = "ScratchConfig.CurrentSwapState",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = true,
         supported = false,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Local.DatastorePath",
      summary = "Datastore path of file to which local syslogd data is written.",
      key = "Syslog.Local.DatastorePath",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Remote.Hostname",
      summary = "Hostname to which syslog data will be forwarded.  Disabled on null.",
      key = "Syslog.Remote.Hostname",
      optionType = (vim.option.StringOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         defaultValue = "",
         validCharacters = &lt;unset&gt;,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "Syslog.Remote.Port",
      summary = "Port to which syslog data will be forwarded.",
      key = "Syslog.Remote.Port",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 1,
         max = 65535,
         defaultValue = 514,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.ACPI",
      summary = "Initialize ACPI CA.",
      key = "VMkernel.Boot.ACPI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.acpiDbgLevel",
      summary = "ACPI debug level",
      key = "VMkernel.Boot.acpiDbgLevel",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.assumeCommonBusClock",
      summary = "Assume all NUMA nodes run off a common, synchronous bus clock (normally autodetected).",
      key = "VMkernel.Boot.assumeCommonBusClock",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.assumePerNodeBusClock",
      summary = "Assume each NUMA node has a separate bus clock (normally autodetected).",
      key = "VMkernel.Boot.assumePerNodeBusClock",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.baudRate",
      summary = "Baud rate to run the serial port at.",
      key = "VMkernel.Boot.baudRate",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 115200,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      summary = "Buddy physical mem debug info switch.",
      key = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.busSpeedMayVary",
      summary = "Allow different bus clock speeds, even within a single NUMA node or SMP system.",
      key = "VMkernel.Boot.busSpeedMayVary",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.busSpeedMayVaryPerNode",
      summary = "Allow substantially different bus clock speeds in different NUMA nodes.",
      key = "VMkernel.Boot.busSpeedMayVaryPerNode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.checkCPUIDLimit",
      summary = "Refuse to run on CPUID limited cpus.",
      key = "VMkernel.Boot.checkCPUIDLimit",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.clockMultiplierMayVary",
      summary = "Allow different CPU clock multipliers, even within a single NUMA node or SMP system.",
      key = "VMkernel.Boot.clockMultiplierMayVary",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      summary = "Allow different CPU clock multipliers in different NUMA nodes.",
      key = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.coresPerPkg",
      summary = "Number of cores per package that vmkernel should use",
      key = "VMkernel.Boot.coresPerPkg",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.correctBSPMTRRMasks",
      summary = "Correct BSP Variable MTRR masks to match the processor physical address bit support",
      key = "VMkernel.Boot.correctBSPMTRRMasks",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.cpuCellSize",
      summary = "Requested cpu scheduler cell size.",
      key = "VMkernel.Boot.cpuCellSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.debugBreak",
      summary = "Break into debugger during vmkernel initialization.",
      key = "VMkernel.Boot.debugBreak",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.dumpDiag",
      summary = "Dump diagnostics information.",
      key = "VMkernel.Boot.dumpDiag",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.executePOST",
      summary = "Run POST tests.",
      key = "VMkernel.Boot.executePOST",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fakeNUMAnodes",
      summary = "Fake # NUMA nodes on UMA systems.",
      key = "VMkernel.Boot.fakeNUMAnodes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fastHzEstimate",
      summary = "Use ACPI PM timer for frequency estimation at boot.",
      key = "VMkernel.Boot.fastHzEstimate",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.forceCRS",
      summary = "Always use IRQ from _CRS",
      key = "VMkernel.Boot.forceCRS",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.fsCheck",
      summary = "Run filesystem checks on system partitions.",
      key = "VMkernel.Boot.fsCheck",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.hyperthreading",
      summary = "Enable hyperthreading if available.",
      key = "VMkernel.Boot.hyperthreading",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.ioapic",
      summary = "Use IOAPICs.",
      key = "VMkernel.Boot.ioapic",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logOnScreen",
      summary = "Display vmkernel log on screen.",
      key = "VMkernel.Boot.logOnScreen",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logSynchronous",
      summary = "Print log messages to screen and/or serial port synchronously.",
      key = "VMkernel.Boot.logSynchronous",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.logicalApicId",
      summary = "Use logical not physical APIC IDs.",
      key = "VMkernel.Boot.logicalApicId",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.maxPCPUS",
      summary = "Number of PCPUs vmkernel should use.",
      key = "VMkernel.Boot.maxPCPUS",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 32,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memCheckEveryWord",
      summary = "Check every single word when checking mem.",
      key = "VMkernel.Boot.memCheckEveryWord",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      summary = "Maximum physical memory (in MB) recognized by kernel",
      key = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 262144,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.memmapStressHighBitMPNs",
      summary = "Test &gt; 64GB physical RAM support by ignoring 4GB - 64GB range",
      key = "VMkernel.Boot.memmapStressHighBitMPNs",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.mpsIntRouting",
      summary = "Use MPS interrupt routing.",
      key = "VMkernel.Boot.mpsIntRouting",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netESX2LegacyMode",
      summary = "ESX2 Legacy networking config compatability.",
      key = "VMkernel.Boot.netESX2LegacyMode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      summary = "Maximum number of pkt buffers queued in each PCPU slab cache.",
      key = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNetqueueEnabled",
      summary = "Enable/Disable NetQueue support.",
      key = "VMkernel.Boot.netNetqueueEnabled",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNumGPBuffers",
      summary = "Number of general purpose buffers to allocate up front.",
      key = "VMkernel.Boot.netNumGPBuffers",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 1024,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netNumPortsets",
      summary = "Maximum number of portsets.",
      key = "VMkernel.Boot.netNumPortsets",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 128,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPanicBadDevOpen",
      summary = "panic if device has a bad open handler.",
      key = "VMkernel.Boot.netPanicBadDevOpen",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktBufUseSlab",
      summary = "Whether to allocate PktBufDescriptor from the pkt slab allocator.",
      key = "VMkernel.Boot.netPktBufUseSlab",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktHeapMaxSize",
      summary = "Maximum size in MB of the pkt buffer heap (advisory only).",
      key = "VMkernel.Boot.netPktHeapMaxSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktHeapMinSize",
      summary = "Minimum size in MB of the pkt buffer heap (advisory only).",
      key = "VMkernel.Boot.netPktHeapMinSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 2,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netPktNumSlabSizes",
      summary = "Number of different slab sizes for the allocator.",
      key = "VMkernel.Boot.netPktNumSlabSizes",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 4,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netUseMemcpyNt",
      summary = "Enable/Disable non temporal memcpy in packet copy.",
      key = "VMkernel.Boot.netUseMemcpyNt",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.netUseProc",
      summary = "Enable/Disable /proc nodes.",
      key = "VMkernel.Boot.netUseProc",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.oem",
      summary = "Enable OEM extensions.",
      key = "VMkernel.Boot.oem",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.overrideSerialPortAddr",
      summary = "UART I/O address",
      key = "VMkernel.Boot.overrideSerialPortAddr",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.pageSharing",
      summary = "Enable page sharing.",
      key = "VMkernel.Boot.pageSharing",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.panicOnVmkernelAbort",
      summary = "Panic if vmkernel aborts initialization.",
      key = "VMkernel.Boot.panicOnVmkernelAbort",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.realNMI",
      summary = "Use real NMI for LINT1.",
      key = "VMkernel.Boot.realNMI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.serialPort",
      summary = "0 = disable, 1 = COM1, 2 = COM2.",
      key = "VMkernel.Boot.serialPort",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 255,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.storageHeapMaxSize",
      summary = "Maximum size in bytes of the main storage heap",
      key = "VMkernel.Boot.storageHeapMaxSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.storageHeapMinSize",
      summary = "Minimum size in bytes of the main storage heap",
      key = "VMkernel.Boot.storageHeapMinSize",
      optionType = (vim.option.IntOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         min = 0,
         max = 2147483647,
         defaultValue = 0,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.techSupportMode",
      summary = "Allow VMware Tech Support Mode access.",
      key = "VMkernel.Boot.techSupportMode",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableACPI",
      summary = "Enable ACPI PM timer as system reference timer.",
      key = "VMkernel.Boot.timerEnableACPI",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableHPET",
      summary = "Enable HPET as system reference timer.",
      key = "VMkernel.Boot.timerEnableHPET",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableMPMC",
      summary = "Enable Cyclone MPMC timer as system reference timer.",
      key = "VMkernel.Boot.timerEnableMPMC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerEnableTSC",
      summary = "Enable TSC as system reference timer.",
      key = "VMkernel.Boot.timerEnableTSC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.timerForceTSC",
      summary = "Always use TSC as system reference timer.",
      key = "VMkernel.Boot.timerForceTSC",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.usbBoot",
      summary = "Require USB boot if bootFS.",
      key = "VMkernel.Boot.usbBoot",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.useNUMAInfo",
      summary = "enable/disable NUMA-ness",
      key = "VMkernel.Boot.useNUMAInfo",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.useTSCForCPUHz",
      summary = "On systems where TSC and CPU frequencies are the same, determines whether to use TSC or the non-halted clock cycles MSR to determine CPU frequency.",
      key = "VMkernel.Boot.useTSCForCPUHz",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.uwSwap",
      summary = "Enable Userworld Swap.",
      key = "VMkernel.Boot.uwSwap",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.vmkKeyboard",
      summary = "Enable vmkernel keyboard driver.",
      key = "VMkernel.Boot.vmkKeyboard",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.vmkTerminals",
      summary = "Enable switching to vmkernel terminals.",
      key = "VMkernel.Boot.vmkTerminals",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.xapicAMDDetect",
      summary = "Detect xapic on opteron",
      key = "VMkernel.Boot.xapicAMDDetect",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = true,
      },
   },
   (vim.option.OptionDef) {
      dynamicType = &lt;unset&gt;,
      label = "VMkernel.Boot.xapicForce",
      summary = "Force APIC ID to 8 bits",
      key = "VMkernel.Boot.xapicForce",
      optionType = (vim.option.BoolOption) {
         dynamicType = &lt;unset&gt;,
         valueIsReadonly = false,
         supported = true,
         defaultValue = false,
      },
   }
 ]
 

The example output has been broken up in 3 isolated parts so that it renders properly. This was too much content for our poor wiki engine to display in one go.

[[Category: Vimsh]]</text>
    <sha1>4a4c953ff9bad34ebe1b6afff17fca89f7a88e4b</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/advopt/settings</title>
  <ns>0</ns>
  <id>290</id>
  <revision>
    <id>560</id>
    <timestamp>2008-12-31T18:12:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/advopt/settings ==== Usage: Get the list of all current settings.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="105" xml:space="preserve">==== vimsh hostsvc/advopt/settings ====
Usage: Get the list of all current settings.

[[Category: Vimsh]]</text>
    <sha1>bd8b700aa33661d05d65c807672e5eb383d1cdb4</sha1>
  </revision>
  <revision>
    <id>563</id>
    <parentid>560</parentid>
    <timestamp>2008-12-31T18:15:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48170" xml:space="preserve">==== vimsh hostsvc/advopt/settings ====
Usage: Get the list of all current settings.
==== Example output ====
Example output from a pristine ESX 3.5i host.
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/advopt/settings
 (vim.option.OptionValue) [
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Irq.RoutingPolicy",
      value = 2,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Irq.BestVcpuRouting",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Irq.IRQRebalancePeriod",
      value = 50,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Irq.IRQMaxLoadPct",
      value = 70,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.LogToFile",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.LogToSerial",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.LogWldPrefix",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.MinimalPanic",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.BlueScreenTimeout",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.HeartbeatTimeout",
      value = 60,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.HeartbeatInterval",
      value = 10000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.HeartbeatPanicTimeout",
      value = 1800,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.HeartbeatAnyPcpuPanic",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.MCEMonitorInterval",
      value = 15,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.DebugMemEnable",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.DebugBuddyEnable",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.EnableHighDMA",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.TimerMinHardPeriod",
      value = 100,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.TimerMaxHardPeriod",
      value = 2000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.TimerMinGuestPeriod",
      value = 100,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.MemAdmitMapEntriesMin",
      value = 30,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.MemMapEntriesLow",
      value = 200,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.KVMapGuardUncached",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.SerialPort",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.SerialBaudRate",
      value = 115200,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.WatchdogBacktrace",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.BHTimeout",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.BhTimeBound",
      value = 2000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.IntTimeout",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.RunningVCpuLimit",
      value = 128,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.HordeEnabled",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.AckActual",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.NoWaitOnSocket",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.ScreenSaverDelay",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.CimEnabled",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.CimOemProvidersEnabled",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.CimIHVProvidersEnabled",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.CimWatchdogInterval",
      value = 60,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.FSSLightWeightProbe",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Misc.ProcVerbose",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.MaxPortRxQueueLen",
      value = 80,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.MaxNetifRxQueueLen",
      value = 100,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.MaxNetifTxQueueLen",
      value = 200,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.GuestTxCopyBreak",
      value = 64,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.VmxnetTxCopySize",
      value = 256,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.VmxnetWinUDPTxFullCopy",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.UseProc",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.UseLegacyProc",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.NotifySwitch",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.NetTxDontClusterSize",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.NetPktAllocTries",
      value = 5,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.CoalesceTxTimeout",
      value = 2000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.CoalesceDefaultOn",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.CoalesceLowTxMsRate",
      value = 4,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.CoalesceLowRxMsRate",
      value = 6,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.CoalesceHandlerPcpu",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.CoalesceTxAlwaysPoll",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.vmxnetBHNetPoll",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.vmxnetThroughputWeight",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.EtherswitchHashSize",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.NoLocalCSum",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.PortSerializeInput",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.PortFlushIterLimit",
      value = 2,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.PortFlushPktLimit",
      value = 64,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.PortTrackTxRace",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.PortKeepDetailedStats",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.PortDisableTimeout",
      value = 5000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipHeapSize",
      value = 9,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipHeapMax",
      value = 30,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.MaxPageInQueueLen",
      value = 500,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.MaxBeaconsAtOnce",
      value = 100,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.MaxBeaconVlans",
      value = 100,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipNoBcopyRx",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipCopySmallTx",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipLargeRx",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipMaxPktInFlight",
      value = 1000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipDelayedAck",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.LinkStatePollTimeout",
      value = 5000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipUseIoat",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TcpipIoatAlwaysWakeup",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.E1000TxZeroCopy",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.E1000TxTsoZeroCopy",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.MinEtherLen",
      value = 60,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.MaxPktRxListQueue",
      value = 3500,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.NetBHRxWorkBound",
      value = 320,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.NetBHRxInputBound",
      value = 64,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.NetBHRxStormThreshold",
      value = 320,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.ReversePathFwdCheck",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.AllowPromiscFilters",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.Vmxnet2PinRxBuf",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.TsoDumpPkt",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.IGMPVersion",
      value = 3,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.IGMPQueries",
      value = 2,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.NcpLlcSap",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Net.IGMPRouterIP",
      value = "10.0.0.0",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.BalancePeriod",
      value = 15,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.SamplePeriod",
      value = 60,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.IdleTax",
      value = 75,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.IdleTaxType",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.SampleActivePctMin",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.ShareScanGHz",
      value = 4,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.ShareScanTime",
      value = 60,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.ShareRateMax",
      value = 1024,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.CtlMaxPercent",
      value = 65,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.AllocHighThreshold",
      value = 1500,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.AllocGuestLargePage",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.AllocUsePSharePool",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.AllocUseGuestPool",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.AdmitHeapMin",
      value = 1024,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.MinFreePct",
      value = 6,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.ShareCOSBufSize",
      value = 2,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.SwapIORetry",
      value = 5000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.TestOnAlloc",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.ShareEstimatePeriod",
      value = 30000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.ShareEstimateProbe",
      value = 200,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.ShareEstimateSamples",
      value = 100,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.kernelResvPad",
      value = 16,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.LogLowMemoryStateUsage",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.LogLowMemoryStateBT",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.SwapDecayPct",
      value = 5,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.DesiredAllocEnable",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.DesiredAllocPct",
      value = 125,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.BonusAllocPct",
      value = 5,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.SwapFilePersist",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.SwapInBatchPages",
      value = 64,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.SwapAsyncWritePages",
      value = 20,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.HostLocalSwapDirEnabled",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.TrackUsageAllocAllowance",
      value = 2048,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.TrackUsageSwapAllowance",
      value = 2048,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.TrackUsageLPageAllowance",
      value = 8,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.TrackUsageHeartbeatPeriod",
      value = 30,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.TrackUsageHeartbeatEnable",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.VMOverheadGrowthLimit",
      value = -1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Mem.HostLocalSwapDir",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.MigratePeriod",
      value = 20,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.CellMigratePeriod",
      value = 1000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.WakeupMigrateIdle",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.PcpuMigrateIdle",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.CreditAgePeriod",
      value = 3000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.BoundLagQuanta",
      value = 8,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.CacheStats",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.Quantum",
      value = 50,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.SkewPollUsec",
      value = 1000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.SkewInstanceThreshold",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.SkewCumulativeThreshold",
      value = 5000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.IdlePackageRebalancePeriod",
      value = 541,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.IntraCoreMigrate",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.VMotionMinAllocPct",
      value = 30,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.VMAdmitCheckPerVcpuMin",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Cpu.CoSchedIdleBalancePeriod",
      value = 1000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.RebalancePeriod",
      value = 2000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.MigImbalanceThreshold",
      value = 10,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.MigThreshold",
      value = 2,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.MigThrashThreshold",
      value = 50,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.SwapLoadEnable",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.SwapLocalityEnable",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.RebalanceEnable",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.RebalanceCoresTotal",
      value = 4,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.RebalanceCoresNode",
      value = 2,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.MonMigEnable",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.AutoMemAffinity",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.PageMigEnable",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Numa.PostMigUseActiveMetric",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "LPage.LPageDefragEnable",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "LPage.LPageMarkLowNodes",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "LPage.LPageDefragRateVM",
      value = 2,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "LPage.LPageDefragRateTotal",
      value = 8,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "LPage.LPageAlwaysTryForNPT",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SharesNormal",
      value = 1000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SharesHigh",
      value = 2000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SharesLow",
      value = 500,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.BandwidthCap",
      value = 2147483647,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ThroughputCap",
      value = 2147483647,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SectorMaxDiff",
      value = 2000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SchedQuantum",
      value = 8,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SchedNumReqOutstanding",
      value = 32,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SchedQControlSeqReqs",
      value = 128,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SchedQControlVMSwitches",
      value = 6,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.MaxLUN",
      value = 256,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SupportSparseLUN",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.UseReportLUN",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.UseDeviceReset",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.UseLunReset",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.RetryUnitAttention",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ResetOnFailover",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.PathEvalTime",
      value = 300,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.MaxVCNotReadyTime",
      value = 60,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.MaxDS400NotReadyTime",
      value = 60,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.EnableNaviReg",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.DelayOnBusy",
      value = 400,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ResetLatency",
      value = 1000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.MaxResetLatency",
      value = 2000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ResetPeriod",
      value = 30,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ResetMaxRetries",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ResetThreadMin",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ResetThreadMax",
      value = 16,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ResetThreadExpires",
      value = 1800,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.ResetOverdueLogPeriod",
      value = 60,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SPBlksToSwitch",
      value = 2048,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SPCmdsToSwitch",
      value = 50,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.PreventVMFSOverwrite",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.DumpMaxRetries",
      value = 10,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.DiskMaxIOSize",
      value = 32767,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.MaskLUNs",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Disk.SANDevicesWithAPFailover",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.Enabled",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.PreCopyLeftMB",
      value = 16,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.PreCopyMinProgressMB",
      value = 16,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.NetTimeout",
      value = 20,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.MemChksum",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.TSMaster",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.PageInTimeout",
      value = 100,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.PageInTimeoutResetOnProgress",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.PageInProgress",
      value = 15,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Migrate.PageInBeforeResume",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.PassthroughLocking",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.ConflictRetries",
      value = 80,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.LogMultiPath",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.LogAborts",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.PrintCmdErrors",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.MaxReserveTime",
      value = 200,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.MaxReserveTotalTime",
      value = 250,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.MaxReserveBacktrace",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.ReserveBacktrace",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.SCSITimeout_ScanTime",
      value = 1000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.SCSITimeout_ReabortTime",
      value = 5000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.ScanOnDriverLoad",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.TimeoutTMThreadMin",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.TimeoutTMThreadMax",
      value = 16,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.TimeoutTMThreadExpires",
      value = 1800,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.TimeoutTMThreadRetry",
      value = 40000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.TimeoutTMThreadLatency",
      value = 2000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.ScsiRestartStalledQueueLatency",
      value = 500,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.CompareLUNNumber",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Scsi.ScsiRescanAllHbas",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "User.ReaddirRetries",
      value = 10,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "User.CDROMSenseTimeout",
      value = 4,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "User.PTEDisableNX",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.IndirectSend",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.DiskFileLockUpdateFreq",
      value = 10,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.LockUpdateTimeout",
      value = 5,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.LockRenewMaxFailureNumber",
      value = 3,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.LockDisable",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.HeartbeatFrequency",
      value = 9,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.HeartbeatTimeout",
      value = 5,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.HeartbeatDelta",
      value = 5,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.HeartbeatMaxFailures",
      value = 3,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.MaxVolumes",
      value = 8,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.SendBufferSize",
      value = 264,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.ReceiveBufferSize",
      value = 128,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.VolumeRemountFrequency",
      value = 30,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "NFS.UDPRetransmitDelay",
      value = 700,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMFS3.OpenWithoutJournal",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMFS3.MaxHeapSizeMB",
      value = 16,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "BufferCache.SoftMaxDirty",
      value = 15,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "BufferCache.HardMaxDirty",
      value = 95,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "BufferCache.FlushInterval",
      value = 30000,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "LVM.EnableResignature",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "LVM.DisallowSnapshotLun",
      value = 1,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "COW.MaxHeapSizeMB",
      value = 32,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "DirentryCache.MaxDentryPerObj",
      value = 2500,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Annotations.WelcomeMessage",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.0.eax",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.0.ebx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.0.ecx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.0.edx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.1.eax",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.1.ebx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.1.ecx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.1.edx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000000.eax",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000000.ebx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000000.ecx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000000.edx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000001.eax",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000001.ebx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000001.ecx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000001.edx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000008.eax",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000008.ebx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000008.ecx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.80000008.edx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.8000000A.eax",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.8000000A.ebx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.8000000A.ecx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.mode.8000000A.edx",
      value = "disable",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.0.eax",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.0.ebx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.0.ecx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.0.edx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.1.eax",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.1.ebx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.1.ecx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.1.edx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000000.eax",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000000.ebx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000000.ecx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000000.edx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000001.eax",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000001.ebx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000001.ecx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000001.edx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000008.eax",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000008.ebx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000008.ecx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.80000008.edx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.8000000A.eax",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.8000000A.ebx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.8000000A.ecx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.cpuidMask.val.8000000A.edx",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.Defaults.security.host.ruissl",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Config.GlobalSettings.guest.commands.sharedPolicyRefCount",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "ScratchConfig.ConfiguredScratchLocation",
      value = "/vmfs/volumes/492b0150-606332e0-01e6-000c291cbde9",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "ScratchConfig.ConfiguredSwapState",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "ScratchConfig.CurrentScratchLocation",
      value = "/vmfs/volumes/492b0150-606332e0-01e6-000c291cbde9",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "ScratchConfig.CurrentSwapState",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Syslog.Local.DatastorePath",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Syslog.Remote.Hostname",
      value = "",
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "Syslog.Remote.Port",
      value = 514,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.ACPI",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.acpiDbgLevel",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.assumeCommonBusClock",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.assumePerNodeBusClock",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.baudRate",
      value = 115200,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.buddyPhysicalMemoryDebugStruct",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.busSpeedMayVary",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.busSpeedMayVaryPerNode",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.checkCPUIDLimit",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.clockMultiplierMayVary",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.clockMultiplierMayVaryPerNode",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.coresPerPkg",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.correctBSPMTRRMasks",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.cpuCellSize",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.debugBreak",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.dumpDiag",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.executePOST",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.fakeNUMAnodes",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.fastHzEstimate",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.forceCRS",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.fsCheck",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.hyperthreading",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.ioapic",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.logOnScreen",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.logSynchronous",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.logicalApicId",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.maxPCPUS",
      value = 32,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.memCheckEveryWord",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.memmapMaxPhysicalMemMB",
      value = 262144,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.memmapStressHighBitMPNs",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.mpsIntRouting",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netESX2LegacyMode",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netMaxPCPUPktCacheSize",
      value = 128,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netNetqueueEnabled",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netNumGPBuffers",
      value = 1024,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netNumPortsets",
      value = 128,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netPanicBadDevOpen",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netPktBufUseSlab",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netPktHeapMaxSize",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netPktHeapMinSize",
      value = 2,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netPktNumSlabSizes",
      value = 4,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netUseMemcpyNt",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.netUseProc",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.oem",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.overrideSerialPortAddr",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.pageSharing",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.panicOnVmkernelAbort",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.realNMI",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.serialPort",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.storageHeapMaxSize",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.storageHeapMinSize",
      value = 0,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.techSupportMode",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.timerEnableACPI",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.timerEnableHPET",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.timerEnableMPMC",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.timerEnableTSC",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.timerForceTSC",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.usbBoot",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.useNUMAInfo",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.useTSCForCPUHz",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.uwSwap",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.vmkKeyboard",
      value = false,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.vmkTerminals",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.xapicAMDDetect",
      value = true,
   },
   (vim.option.OptionValue) {
      dynamicType = &lt;unset&gt;,
      key = "VMkernel.Boot.xapicForce",
      value = false,
   }
 ]

[[Category: Vimsh]]</text>
    <sha1>65c6a069b1ddb752b07115c83d9ffdbfa35cce56</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/advopt/update</title>
  <ns>0</ns>
  <id>291</id>
  <revision>
    <id>561</id>
    <timestamp>2008-12-31T18:12:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/advopt/update ==== Usage: update key type value  Update the value of an option.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="119" xml:space="preserve">==== vimsh hostsvc/advopt/update ====
Usage: update key type value

Update the value of an option.

[[Category: Vimsh]]</text>
    <sha1>34abf82111a21a20345f0bc4bd76d9046719d20e</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/advopt/view</title>
  <ns>0</ns>
  <id>292</id>
  <revision>
    <id>562</id>
    <timestamp>2008-12-31T18:13:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/advopt/view ==== Usage: view key  Get a specific node or subtree of the option hierarchy.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="123" xml:space="preserve">==== hostsvc/advopt/view ====
Usage: view key

Get a specific node or subtree of the option hierarchy.

[[Category: Vimsh]]</text>
    <sha1>b093228f98e1a16d373c2ec3e79f03102ca060e5</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/autostartmanager/</title>
  <ns>0</ns>
  <id>293</id>
  <revision>
    <id>564</id>
    <timestamp>2008-12-31T18:19:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/autostartmanager/ ====   [[hostsvc/autostartmanager/autostart]]  [[hostsvc/autostartmanager/autostop]]  [[hostsvc/autostartmanager/enable_autostart]]  [[hostsvc/autostar...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="377" xml:space="preserve">==== vimsh hostsvc/autostartmanager/ ====

 [[hostsvc/autostartmanager/autostart]]
 [[hostsvc/autostartmanager/autostop]]
 [[hostsvc/autostartmanager/enable_autostart]]
 [[hostsvc/autostartmanager/get_autostartseq]]
 [[hostsvc/autostartmanager/get_defaults]]
 [[hostsvc/autostartmanager/update_autostartentry]]
 [[hostsvc/autostartmanager/update_defaults]]

[[Category: Vimsh]]</text>
    <sha1>877178357a7c54fcc5c4ff7165492bd90c096540</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/autostartmanager/autostart</title>
  <ns>0</ns>
  <id>294</id>
  <revision>
    <id>565</id>
    <timestamp>2008-12-31T18:20:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/autostartmanager/autostart ====  Usage: autostart  Starts up VMs in the AutoStart sequence    [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== vimsh hostsvc/autostartmanager/autostart ====

Usage: autostart

Starts up VMs in the AutoStart sequence


[[Category: Vimsh]]</text>
    <sha1>203f277a790583adf4571f1aabad5ffa7d068f12</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/autostartmanager/autostop</title>
  <ns>0</ns>
  <id>295</id>
  <revision>
    <id>566</id>
    <timestamp>2008-12-31T18:21:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/autostartmanager/autostop ====  Usage: autostop  Shuts down VMs in the AutoStart sequence  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="129" xml:space="preserve">==== vimsh hostsvc/autostartmanager/autostop ====

Usage: autostop

Shuts down VMs in the AutoStart sequence

[[Category: Vimsh]]</text>
    <sha1>8c532304dd2d7d785c1151c6af0c2cda7d248acf</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/autostartmanager/enable autostart</title>
  <ns>0</ns>
  <id>296</id>
  <revision>
    <id>567</id>
    <timestamp>2008-12-31T18:22:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/autostartmanager/enable_autostart ==== Usage: enable_autostart EnableAutoStart  Enable or disable AutoStart.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="148" xml:space="preserve">==== vimsh hostsvc/autostartmanager/enable_autostart ====
Usage: enable_autostart EnableAutoStart

Enable or disable AutoStart.

[[Category: Vimsh]]</text>
    <sha1>ffbd5dbf3eab461edb6a63f6442cb14783820eb5</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/autostartmanager/get autostartseq</title>
  <ns>0</ns>
  <id>297</id>
  <revision>
    <id>568</id>
    <timestamp>2008-12-31T18:23:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/autostartmanager/get_autostartseq ==== Usage: Get the current VM Autostart sequence.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">==== vimsh hostsvc/autostartmanager/get_autostartseq ====
Usage: Get the current VM Autostart sequence.


[[Category: Vimsh]]</text>
    <sha1>b9c7793fc89b602bc43ab70322141e3e3b756c86</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/autostartmanager/get defaults</title>
  <ns>0</ns>
  <id>298</id>
  <revision>
    <id>569</id>
    <timestamp>2008-12-31T18:23:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/autostartmanager/get_defaults ==== Usage: Get the AutoStart system defaults.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="110" xml:space="preserve">==== hostsvc/autostartmanager/get_defaults ====
Usage: Get the AutoStart system defaults.

[[Category: Vimsh]]</text>
    <sha1>b8a30aa4953aad776fbc2035dc90b8fdadc09ec9</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/autostartmanager/update autostartentry</title>
  <ns>0</ns>
  <id>299</id>
  <revision>
    <id>570</id>
    <timestamp>2008-12-31T18:24:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/autostartmanager/update_autostartentry ==== Usage: update_autostartentry VMId StartAction StartDelay StartOrder StopAction StopDelay WaitForHeartbeat  Updates a single V...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="229" xml:space="preserve">==== vimsh hostsvc/autostartmanager/update_autostartentry ====
Usage: update_autostartentry VMId StartAction StartDelay StartOrder StopAction StopDelay WaitForHeartbeat

Updates a single VM's AutoStart entry.

[[Category: Vimsh]]</text>
    <sha1>f32b208246ae61f81bcb71f3d4f610c488e60d51</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/autostartmanager/update defaults</title>
  <ns>0</ns>
  <id>300</id>
  <revision>
    <id>571</id>
    <timestamp>2008-12-31T18:25:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/autostartmanager/update_defaults ==== Usage: update_defaults StartDelay [StopDelay] [StopAction] [WaitForHeartbeat]  Updates AutoStart system defaults.  [[Category: Vims...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="191" xml:space="preserve">==== vimsh hostsvc/autostartmanager/update_defaults ====
Usage: update_defaults StartDelay [StopDelay] [StopAction] [WaitForHeartbeat]

Updates AutoStart system defaults.

[[Category: Vimsh]]</text>
    <sha1>2c30fdc36615beb8b16c82a8d4cca64b47808ca3</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/</title>
  <ns>0</ns>
  <id>301</id>
  <revision>
    <id>572</id>
    <timestamp>2008-12-31T18:47:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/ ====   [[hostsvc/datastore/capabilities]]  [[hostsvc/datastore/destroy]]  [[hostsvc/datastore/info]]  [[hostsvc/datastore/listsummary]]  [[hostsvc/datastore/l...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="626" xml:space="preserve">==== vimsh hostsvc/datastore/ ====

 [[hostsvc/datastore/capabilities]]
 [[hostsvc/datastore/destroy]]
 [[hostsvc/datastore/info]]
 [[hostsvc/datastore/listsummary]]
 [[hostsvc/datastore/listvm]]
 [[hostsvc/datastore/localds_create]]
 [[hostsvc/datastore/nas_create]]
 [[hostsvc/datastore/refresh]]
 [[hostsvc/datastore/remove]]
 [[hostsvc/datastore/rename]]
 [[hostsvc/datastore/summary]]
 [[hostsvc/datastore/vmfs_create]]
 [[hostsvc/datastore/vmfs_extend]]
 [[hostsvc/datastore/vmfs_queryAvailableDisks]]
 [[hostsvc/datastore/vmfs_query_create_options]]
 [[hostsvc/datastore/vmfs_query_extend_options]]

[[Category: Vimsh]]</text>
    <sha1>680124767daf91b8e5e130c71256757beda10790</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/capabilities</title>
  <ns>0</ns>
  <id>302</id>
  <revision>
    <id>573</id>
    <timestamp>2008-12-31T18:49:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/datastore/capabilities ==== Usage: List the capabilities supported by the datastore system.  [[category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">==== hostsvc/datastore/capabilities ====
Usage: List the capabilities supported by the datastore system.

[[category: Vimsh]]</text>
    <sha1>de574107dd748875f98671b77a4ae723fa17e639</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/destroy</title>
  <ns>0</ns>
  <id>303</id>
  <revision>
    <id>574</id>
    <timestamp>2008-12-31T18:50:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/destroy ==== Usage: destroy name  Destroy a datastore.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="104" xml:space="preserve">==== vimsh hostsvc/datastore/destroy ====
Usage: destroy name

Destroy a datastore.

[[Category: Vimsh]]</text>
    <sha1>78319bdd7b328514c76fb74df5354b87911d6d18</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/info</title>
  <ns>0</ns>
  <id>304</id>
  <revision>
    <id>575</id>
    <timestamp>2008-12-31T18:51:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/datastore/info ==== Usage: info name  Retrieve the information of a datastore by name.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="121" xml:space="preserve">==== hostsvc/datastore/info ====
Usage: info name

Retrieve the information of a datastore by name.


[[Category: Vimsh]]</text>
    <sha1>cc99a7eead227d2f4aa009f6760391e6fafe3985</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/listsummary</title>
  <ns>0</ns>
  <id>305</id>
  <revision>
    <id>576</id>
    <timestamp>2008-12-31T18:52:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/datastore/listsummary ==== Usage: List a summary of all datastores available.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="111" xml:space="preserve">==== hostsvc/datastore/listsummary ====
Usage: List a summary of all datastores available.

[[Category: Vimsh]]</text>
    <sha1>ec851168ad83aeee7bd47c1eaff79ba8dc29b63c</sha1>
  </revision>
  <revision>
    <id>577</id>
    <parentid>576</parentid>
    <timestamp>2008-12-31T18:52:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="117" xml:space="preserve">==== vimsh hostsvc/datastore/listsummary ====
Usage: List a summary of all datastores available.

[[Category: Vimsh]]</text>
    <sha1>e2cbe00584539a3e2211ec27ddb602d012fb14f5</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/listvm</title>
  <ns>0</ns>
  <id>306</id>
  <revision>
    <id>578</id>
    <timestamp>2008-12-31T18:53:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/listvm ==== Usage: listvm name  Retrieve the virtual machines stored on the datastore.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="136" xml:space="preserve">==== vimsh hostsvc/datastore/listvm ====
Usage: listvm name

Retrieve the virtual machines stored on the datastore.

[[Category: Vimsh]]</text>
    <sha1>5e36dc94d761abfdfcf89c8b03dc820ec59370c8</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/localds create</title>
  <ns>0</ns>
  <id>307</id>
  <revision>
    <id>579</id>
    <timestamp>2008-12-31T18:54:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/datastore/localds_create ==== Usage: localds_create name localPath  Add a local datastore.  [[category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="124" xml:space="preserve">==== hostsvc/datastore/localds_create ====
Usage: localds_create name localPath

Add a local datastore.

[[category: Vimsh]]</text>
    <sha1>28eea1d181f1a63c2e9cfb10a778b7c468b104f2</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/nas create</title>
  <ns>0</ns>
  <id>308</id>
  <revision>
    <id>580</id>
    <timestamp>2008-12-31T18:55:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/nas_create ==== Usage: nas_create name remoteHost remotePath readonly  Add a NAS datastore. readonly is a boolean value, 1 for readonly and 0 for rw access.  [...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="206" xml:space="preserve">==== vimsh hostsvc/datastore/nas_create ====
Usage: nas_create name remoteHost remotePath readonly

Add a NAS datastore.
readonly is a boolean value, 1 for readonly and 0 for rw access.

[[Category: Vimsh]]</text>
    <sha1>43c43ab2dd04dff2abd6859c4d14b64c800bb64b</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/refresh</title>
  <ns>0</ns>
  <id>309</id>
  <revision>
    <id>581</id>
    <timestamp>2008-12-31T18:56:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/refresh ==== Usage: refresh name  Refresh a datastore.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="105" xml:space="preserve">==== vimsh hostsvc/datastore/refresh ====
Usage: refresh name

Refresh a datastore.


[[Category: Vimsh]]</text>
    <sha1>dcc12b8632a421e350745e91997226a34117e38c</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/remove</title>
  <ns>0</ns>
  <id>310</id>
  <revision>
    <id>582</id>
    <timestamp>2008-12-31T18:57:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/remove ==== Usage: remove name  Remove a datastore.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="101" xml:space="preserve">==== vimsh hostsvc/datastore/remove ====
Usage: remove name

Remove a datastore.

[[Category: Vimsh]]</text>
    <sha1>b56dbec1a2097beb95747ead3e82a08f0f738bf5</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/rename</title>
  <ns>0</ns>
  <id>311</id>
  <revision>
    <id>583</id>
    <timestamp>2008-12-31T18:58:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/rename ==== Usage: rename name newname  Rename a datastore.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">==== vimsh hostsvc/datastore/rename ====
Usage: rename name newname

Rename a datastore.

[[Category: Vimsh]]</text>
    <sha1>2ca391062fda91abeba1520f6bc0b1e57c78b164</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/summary</title>
  <ns>0</ns>
  <id>312</id>
  <revision>
    <id>584</id>
    <timestamp>2008-12-31T18:59:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/summary ==== Usage: summary name  Retrieve the summary of a datastore by name.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="128" xml:space="preserve">==== vimsh hostsvc/datastore/summary ====
Usage: summary name

Retrieve the summary of a datastore by name.

[[Category: Vimsh]]</text>
    <sha1>71479c2023de8f62ee426837e62e4535eceed94f</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/vmfs create</title>
  <ns>0</ns>
  <id>313</id>
  <revision>
    <id>585</id>
    <timestamp>2008-12-31T19:00:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastoree/vmfs_create ==== Usage: vmfs_create [OPTIONS] name devId volumeName blockSizeMb majorVersion head  Add a VMFS datastore.   Options:    --partition=int        ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1162" xml:space="preserve">==== vimsh hostsvc/datastoree/vmfs_create ====
Usage: vmfs_create [OPTIONS] name devId volumeName blockSizeMb majorVersion head

Add a VMFS datastore.

 Options:
   --partition=int
       Partition  number.
 
   --startector=int
       Start sector.
 
   --endsector=int
       End sector.
 
   --typeid=fs_type
       Type of data in the file system.
 
   --logical=bool
       If it is logical partition.
 
   --attributes=byte
       Partition attributes.
 
   --partition2=int
       Partition  number.
 
   --startector2=int
       Start sector.
 
   --endsector2=int
       End sector.
 
   --typeid2=byte
       Type of data in the file system.
 
   --logical2=bool
       If it is logical partition.
 
   --attributes2=byte
       Partition attributes.
 
   --partition3=int
       Partition  number.
 
   --startector3=int
       Start sector.
 
   --endsector3=int
       End sector.
 
   --typeid3=byte
       Type of data in the file system.
 
   --logical3=bool
       If it is logical partition.
 
   --attributes3=byte
       Partition attributes.
 
   --extentIds=partition_list
       List of partitions to extent the VMFS.


[[Category: Vimsh]]</text>
    <sha1>4ca307b1f00f2fe9ae2151637540fbd709554282</sha1>
  </revision>
  <revision>
    <id>586</id>
    <parentid>585</parentid>
    <timestamp>2008-12-31T19:01:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1161" xml:space="preserve">==== vimsh hostsvc/datastore/vmfs_create ====
Usage: vmfs_create [OPTIONS] name devId volumeName blockSizeMb majorVersion head

Add a VMFS datastore.

 Options:
   --partition=int
       Partition  number.
 
   --startector=int
       Start sector.
 
   --endsector=int
       End sector.
 
   --typeid=fs_type
       Type of data in the file system.
 
   --logical=bool
       If it is logical partition.
 
   --attributes=byte
       Partition attributes.
 
   --partition2=int
       Partition  number.
 
   --startector2=int
       Start sector.
 
   --endsector2=int
       End sector.
 
   --typeid2=byte
       Type of data in the file system.
 
   --logical2=bool
       If it is logical partition.
 
   --attributes2=byte
       Partition attributes.
 
   --partition3=int
       Partition  number.
 
   --startector3=int
       Start sector.
 
   --endsector3=int
       End sector.
 
   --typeid3=byte
       Type of data in the file system.
 
   --logical3=bool
       If it is logical partition.
 
   --attributes3=byte
       Partition attributes.
 
   --extentIds=partition_list
       List of partitions to extent the VMFS.


[[Category: Vimsh]]</text>
    <sha1>7bd2b4914e6e7bf03a4e553b877e7421cdbe339e</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>VMWareTasks</title>
  <ns>0</ns>
  <id>273</id>
  <revision>
    <id>587</id>
    <parentid>498</parentid>
    <timestamp>2008-12-31T19:03:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="536" xml:space="preserve">====VMWareTasks====

VMWareTasks is a C# library on top of the VIX API. It exposes a better programming model for the 99% of those synchronous VMWare scenarios where you don't want to deal with jobs or other more complex constructs.

====Project====
* http://www.codeproject.com/KB/library/VMWareTasks.aspx

* http://code.dblock.org/ShowPost.aspx?id=25

====See also====
* [http://communities.vmware.com/thread/186164 VMWareTasks: A VIX API C# Library (let's reinvent less wheels)]


[[Category: VIX]][[Category: SDK]][[Category: .net]]</text>
    <sha1>5599550a84ca6eee58fc9e7779eca7d88d464bf0</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>VixCOMWrapper</title>
  <ns>0</ns>
  <id>274</id>
  <revision>
    <id>588</id>
    <parentid>497</parentid>
    <timestamp>2008-12-31T19:03:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="380" xml:space="preserve">====vixCOMWrapper====
Simplify dealing with the VIX API when using C# and make common tasks (powering on/off, copying files) a lot easier. 

====Project====
* http://www.codeplex.com/VixCOMWrapper

====See also====
* [http://communities.vmware.com/thread/186164 VMWareTasks: A VIX API C# Library (let's reinvent less wheels)]


[[Category: VIX]][[Category: SDK]][[Category: .net]]</text>
    <sha1>f1985a6f4049b872472019378bbe800867012309</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/vmfs extend</title>
  <ns>0</ns>
  <id>314</id>
  <revision>
    <id>589</id>
    <timestamp>2009-01-01T22:35:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/vmfs_extend ==== Usage: vmfs_extend [OPTIONS] name devId  Extend a VMFS datastore.   Options:    --partition=int        Partition  number.      --startector=in...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1123" xml:space="preserve">==== vimsh hostsvc/datastore/vmfs_extend ====
Usage: vmfs_extend [OPTIONS] name devId

Extend a VMFS datastore.

 Options:
   --partition=int
       Partition  number.
 
   --startector=int
       Start sector.
 
   --endsector=int
       End sector.
 
   --typeid=fs_type
       Type of data in the file system.
 
   --logical=bool
       If it is logical partition.
 
   --attributes=byte
       Partition attributes.
 
   --partition2=int
       Partition  number.
 
   --startector2=int
       Start sector.
 
   --endsector2=int
       End sector.
 
   --typeid2=byte
       Type of data in the file system.
 
   --logical2=bool
       If it is logical partition.
 
   --attributes2=byte
       Partition attributes.
 
   --partition3=int
       Partition  number.
 
   --startector3=int
       Start sector.
 
   --endsector3=int
       End sector.
 
   --typeid3=byte
       Type of data in the file system.
 
   --logical3=bool
       If it is logical partition.
 
   --attributes3=byte
       Partition attributes.
 
   --extentIds=partition_list
       List of partitions to extent the VMFS.
 
[[Category: Vimsh]]</text>
    <sha1>45c17d040509879cfff15c7a7dc31d35c793c4ee</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/vmfs queryAvailableDisks</title>
  <ns>0</ns>
  <id>315</id>
  <revision>
    <id>590</id>
    <timestamp>2009-01-01T22:36:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/vmfs_queryAvailableDisks ==== Usage: vmfs_queryAvailableDisks [datastore]  Gets the list of disks available for creating or extending a vmfs datastore.  [[Cate...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="201" xml:space="preserve">==== vimsh hostsvc/datastore/vmfs_queryAvailableDisks ====
Usage: vmfs_queryAvailableDisks [datastore]

Gets the list of disks available for creating or extending a vmfs datastore.

[[Category: Vimsh]]</text>
    <sha1>2712a9db9cb5fea58661af4bd4899b4df5639978</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/vmfs query create options</title>
  <ns>0</ns>
  <id>316</id>
  <revision>
    <id>591</id>
    <timestamp>2009-01-01T22:37:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/vmfs_query_create_options ==== Usage: vmfs_query_create_options devName  Queries options for creating a new VMFS datastore for a disk.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="184" xml:space="preserve">==== vimsh hostsvc/datastore/vmfs_query_create_options ====
Usage: vmfs_query_create_options devName

Queries options for creating a new VMFS datastore for a disk.

[[Category: Vimsh]]</text>
    <sha1>93cf219f329a335ec5a5e752e3b2bc268bd7a626</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastore/vmfs query extend options</title>
  <ns>0</ns>
  <id>317</id>
  <revision>
    <id>592</id>
    <timestamp>2009-01-01T22:38:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastore/vmfs_query_extend_options ==== Usage: vmfs_query_extend_options vmfsDatastore devName  Queries options for extending a new VMFS datastore for a disk.  [[Catego...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="199" xml:space="preserve">==== vimsh hostsvc/datastore/vmfs_query_extend_options ====
Usage: vmfs_query_extend_options vmfsDatastore devName

Queries options for extending a new VMFS datastore for a disk.

[[Category: Vimsh]]</text>
    <sha1>8fb599aea248233d047b9f0a52c0ad4b96067900</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastorebrowser/</title>
  <ns>0</ns>
  <id>318</id>
  <revision>
    <id>593</id>
    <timestamp>2009-01-01T22:40:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: === vimsh hostsvc/datastorebrowser/ ====   [[hostsvc/datastorebrowser/deleteFile]]  [[hostsvc/datastorebrowser/disksearch]]  [[hostsvc/datastorebrowser/list]]  [[hostsvc/datastorebrowser/s...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="263" xml:space="preserve">=== vimsh hostsvc/datastorebrowser/ ====

 [[hostsvc/datastorebrowser/deleteFile]]
 [[hostsvc/datastorebrowser/disksearch]]
 [[hostsvc/datastorebrowser/list]]
 [[hostsvc/datastorebrowser/search]]
 [[hostsvc/datastorebrowser/searchsubfolders]]

[[Category: Vimsh]]</text>
    <sha1>0c2723bfb9560ff65db7b06f6d1a16a0777d13e3</sha1>
  </revision>
  <revision>
    <id>594</id>
    <parentid>593</parentid>
    <timestamp>2009-01-01T22:41:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="264" xml:space="preserve">==== vimsh hostsvc/datastorebrowser/ ====

 [[hostsvc/datastorebrowser/deleteFile]]
 [[hostsvc/datastorebrowser/disksearch]]
 [[hostsvc/datastorebrowser/list]]
 [[hostsvc/datastorebrowser/search]]
 [[hostsvc/datastorebrowser/searchsubfolders]]

[[Category: Vimsh]]</text>
    <sha1>4b26cdf0db54f5a48c2cff29831e241ec393b5a8</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastorebrowser/deleteFile</title>
  <ns>0</ns>
  <id>319</id>
  <revision>
    <id>595</id>
    <timestamp>2009-01-01T22:41:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastorebrowser/deletefile ==== Usage: deleteFile BrowserType DatastorePath  Deletes a file from the given datastore path.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">==== vimsh hostsvc/datastorebrowser/deletefile ====
Usage: deleteFile BrowserType DatastorePath

Deletes a file from the given datastore path.

[[Category: Vimsh]]</text>
    <sha1>203993f00614e072731429fedb111951bbeab264</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastorebrowser/disksearch</title>
  <ns>0</ns>
  <id>320</id>
  <revision>
    <id>596</id>
    <timestamp>2009-01-01T22:43:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastorebrowser/disksearch ==== Usage: disksearch DatastorePath  Searches the given datastore path for disks.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="150" xml:space="preserve">==== vimsh hostsvc/datastorebrowser/disksearch ====
Usage: disksearch DatastorePath

Searches the given datastore path for disks.

[[Category: Vimsh]]</text>
    <sha1>6ad2c2dfaef6db431192af774125742f28daeab1</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastorebrowser/list</title>
  <ns>0</ns>
  <id>321</id>
  <revision>
    <id>597</id>
    <timestamp>2009-01-01T22:43:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/datastorebrowser/list ==== Usage: list BrowserType BrwsrFrmDatastores  Lists all the datastores.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="130" xml:space="preserve">==== hostsvc/datastorebrowser/list ====
Usage: list BrowserType BrwsrFrmDatastores

Lists all the datastores.

[[Category: Vimsh]]</text>
    <sha1>764c658d16d8c68d0b369a14211ea0407f0ec5a9</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastorebrowser/search</title>
  <ns>0</ns>
  <id>322</id>
  <revision>
    <id>598</id>
    <timestamp>2009-01-01T22:44:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastorebrowser/search ==== Usage: search BrowserType DatastorePath  Searches the given datastore path.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">==== vimsh hostsvc/datastorebrowser/search ====
Usage: search BrowserType DatastorePath

Searches the given datastore path.

[[Category: Vimsh]]</text>
    <sha1>835cadef8096d8e378efd7c3ddb11b8b3466f113</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/datastorebrowser/searchsubfolders</title>
  <ns>0</ns>
  <id>323</id>
  <revision>
    <id>599</id>
    <timestamp>2009-01-01T22:45:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/datastorebrowser/searchsubfolders ==== Usage: searchsubfolders BrowserType DatastorePath  Searches the given datastore path.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="164" xml:space="preserve">==== vimsh hostsvc/datastorebrowser/searchsubfolders ====
Usage: searchsubfolders BrowserType DatastorePath

Searches the given datastore path.

[[Category: Vimsh]]</text>
    <sha1>b97852b2811835945adf21ec20b2dc857e349563</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/rsrc/</title>
  <ns>0</ns>
  <id>324</id>
  <revision>
    <id>600</id>
    <timestamp>2009-01-01T22:48:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/ ====   [[hostsvc/rsrc/create]]  [[hostsvc/rsrc/destroy]]  [[hostsvc/rsrc/destroy_children]]  [[hostsvc/rsrc/pool_config_get]]  [[hostsvc/rsrc/pool_config_set]]  [[...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="383" xml:space="preserve">==== vimsh hostsvc/rsrc/ ====

 [[hostsvc/rsrc/create]]
 [[hostsvc/rsrc/destroy]]
 [[hostsvc/rsrc/destroy_children]]
 [[hostsvc/rsrc/pool_config_get]]
 [[hostsvc/rsrc/pool_config_set]]
 [[hostsvc/rsrc/pool_runtime_get]]
 [[hostsvc/rsrc/pools_get]]
 [[hostsvc/rsrc/rename]]
 [[hostsvc/rsrc/vm_config_get]]
 [[hostsvc/rsrc/vm_config_set]]
 [[hostsvc/rsrc/vms_get]]

[[Category: Vimsh]]</text>
    <sha1>08ff6f381832610ef88a2a6479842e18878812c9</sha1>
  </revision>
  <revision>
    <id>602</id>
    <parentid>600</parentid>
    <timestamp>2009-01-01T23:32:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="399" xml:space="preserve">==== vimsh hostsvc/rsrc/ ====

Resource pools

 [[hostsvc/rsrc/create]]
 [[hostsvc/rsrc/destroy]]
 [[hostsvc/rsrc/destroy_children]]
 [[hostsvc/rsrc/pool_config_get]]
 [[hostsvc/rsrc/pool_config_set]]
 [[hostsvc/rsrc/pool_runtime_get]]
 [[hostsvc/rsrc/pools_get]]
 [[hostsvc/rsrc/rename]]
 [[hostsvc/rsrc/vm_config_get]]
 [[hostsvc/rsrc/vm_config_set]]
 [[hostsvc/rsrc/vms_get]]

[[Category: Vimsh]]</text>
    <sha1>c72049b12ed7ecaa7ab4af0f4a0b6e217cf448f9</sha1>
  </revision>
</page>
<page arvcontinue="20081230123837|553">
  <title>Hostsvc/rsrc/create</title>
  <ns>0</ns>
  <id>325</id>
  <revision>
    <id>601</id>
    <timestamp>2009-01-01T23:31:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/create ==== Usage: create [OPTIONS] poolId poolName  Create a child pool with default resource settings under the specified pool.  Options:    --cpu-min=int        ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="688" xml:space="preserve">==== vimsh hostsvc/rsrc/create ====
Usage: create [OPTIONS] poolId poolName

Create a child pool with default resource settings under the specified pool.

Options:
   --cpu-min=int
       CPU minimum (in MHz).
 
   --cpu-min-expandable=bool
       Can pool borrow CPU resources from parent?
 
   --cpu-max=int
       CPU maximum (in MHz).
 
   --cpu-shares=string
       CPU shares (low/normal/high/&lt;custom&gt;).
 
   --mem-min=int
       Memory minimum (in MB).
 
   --mem-min-expandable=bool
       Can pool borrow memory resources from parent?
 
   --mem-max=int
       Memory maximum (in MB).
 
   --mem-shares=string
       Memory shares (low/normal/high/&lt;custom&gt;).

[[Category: Vimsh]]</text>
    <sha1>dc510d80b49121e0cdec9429cc768d5eca4c5fa9</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/destroy</title>
  <ns>0</ns>
  <id>326</id>
  <revision>
    <id>603</id>
    <timestamp>2009-01-01T23:33:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/destroy ==== Usage: destroy poolId  Destroy the specified resource pool, reparenting any VMs to its parent.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="153" xml:space="preserve">==== vimsh hostsvc/rsrc/destroy ====
Usage: destroy poolId

Destroy the specified resource pool, reparenting any VMs to its parent.


[[Category: Vimsh]]</text>
    <sha1>ff0ff5cd4548774f35253a4cbb65140381477f05</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/destroy children</title>
  <ns>0</ns>
  <id>327</id>
  <revision>
    <id>604</id>
    <timestamp>2009-01-01T23:34:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/destroy_children ==== Usage: destroy_children poolId  Destroy the child pools of the specified pool, reparenting any VMs to this pool.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="179" xml:space="preserve">==== vimsh hostsvc/rsrc/destroy_children ====
Usage: destroy_children poolId

Destroy the child pools of the specified pool, reparenting any VMs to this pool.

[[Category: Vimsh]]</text>
    <sha1>b10d64303e125b72f1e1a29ea30c14624af951dc</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/pool config get</title>
  <ns>0</ns>
  <id>328</id>
  <revision>
    <id>605</id>
    <timestamp>2009-01-01T23:35:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/pool_config_get ==== Usage: pool_config_get poolId  Get the configuration of the specified pool.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="142" xml:space="preserve">==== vimsh hostsvc/rsrc/pool_config_get ====
Usage: pool_config_get poolId

Get the configuration of the specified pool.


[[Category: Vimsh]]</text>
    <sha1>7486d7444904911053315d089ec61b8e893d5afc</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/pool config set</title>
  <ns>0</ns>
  <id>329</id>
  <revision>
    <id>606</id>
    <timestamp>2009-01-01T23:36:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/pool_config_set ==== Usage: pool_config_set [OPTIONS] poolId  Update the configuration of the specified pool.  Options:    --cpu-min=int        CPU minimum (in MHz)...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="670" xml:space="preserve">==== vimsh hostsvc/rsrc/pool_config_set ====
Usage: pool_config_set [OPTIONS] poolId

Update the configuration of the specified pool.

Options:
   --cpu-min=int
       CPU minimum (in MHz).
 
   --cpu-min-expandable=bool
       Can pool borrow CPU resources from parent?
 
   --cpu-max=int
       CPU maximum (in MHz).
 
   --cpu-shares=string
       CPU shares (low/normal/high/&lt;custom&gt;).
 
   --mem-min=int
       Memory minimum (in MB).
 
   --mem-min-expandable=bool
       Can pool borrow memory resources from parent?
 
   --mem-max=int
       Memory maximum (in MB).
 
   --mem-shares=string
       Memory shares (low/normal/high/&lt;custom&gt;).
 

[[Category: Vimsh]]</text>
    <sha1>42eea84799027d6e853518881ce27995598d9095</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/pool runtime get</title>
  <ns>0</ns>
  <id>330</id>
  <revision>
    <id>607</id>
    <timestamp>2009-01-01T23:37:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/pool_runtime_get ==== Usage: pool_runtime_get poolId  Get the runtime info for the specified pool.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">==== vimsh hostsvc/rsrc/pool_runtime_get ====
Usage: pool_runtime_get poolId

Get the runtime info for the specified pool.


[[Category: Vimsh]]</text>
    <sha1>994ca07fb3bf82410520b836bd4a63b721f1128f</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/pools get</title>
  <ns>0</ns>
  <id>331</id>
  <revision>
    <id>608</id>
    <timestamp>2009-01-01T23:38:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/pools_get ==== Usage: pools_get poolId  Get the list of pools nested within the specified pool.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="141" xml:space="preserve">==== vimsh hostsvc/rsrc/pools_get ====
Usage: pools_get poolId

Get the list of pools nested within the specified pool.


[[Category: Vimsh]]</text>
    <sha1>db8b0356960ed1416a0e138d882258b8f29332f5</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/rename</title>
  <ns>0</ns>
  <id>332</id>
  <revision>
    <id>609</id>
    <timestamp>2009-01-01T23:39:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/rename ==== Usage: rename poolId poolName  Renames the specified pool  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="114" xml:space="preserve">==== vimsh hostsvc/rsrc/rename ====
Usage: rename poolId poolName

Renames the specified pool

[[Category: Vimsh]]</text>
    <sha1>eab5eb6aafced929d2c105c053f681dfa4299240</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/vm config get</title>
  <ns>0</ns>
  <id>333</id>
  <revision>
    <id>610</id>
    <timestamp>2009-01-01T23:40:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/vm_config_get ==== Usage: vm_config_get vmCfgPath  Get the configuration of the specified virtual machine.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">==== vimsh hostsvc/rsrc/vm_config_get ====
Usage: vm_config_get vmCfgPath

Get the configuration of the specified virtual machine.

[[Category: Vimsh]]</text>
    <sha1>f6346a51d7ba8f9d6faa5adf4d9341e1ca7939b9</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/vm config set</title>
  <ns>0</ns>
  <id>334</id>
  <revision>
    <id>611</id>
    <timestamp>2009-01-01T23:41:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/rsrc/vm_config_set ==== Usage: vm_config_set [OPTIONS] vmCfgPath  Update the configuration of the specified virtual machine.  Options:    --cpu-min=int        CPU minimum (in ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="672" xml:space="preserve">==== hostsvc/rsrc/vm_config_set ====
Usage: vm_config_set [OPTIONS] vmCfgPath

Update the configuration of the specified virtual machine.

Options:
   --cpu-min=int
       CPU minimum (in MHz).
 
   --cpu-min-expandable=bool
       Can pool borrow CPU resources from parent?
 
   --cpu-max=int
       CPU maximum (in MHz).
 
   --cpu-shares=string
       CPU shares (low/normal/high/&lt;custom&gt;).
 
   --mem-min=int
       Memory minimum (in MB).
 
   --mem-min-expandable=bool
       Can pool borrow memory resources from parent?
 
   --mem-max=int
       Memory maximum (in MB).
 
   --mem-shares=string
       Memory shares (low/normal/high/&lt;custom&gt;).

[[Category: Vimsh]]</text>
    <sha1>d44b1e1d5cf4e179f0122410a580f84fa21cbf55</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/rsrc/vms get</title>
  <ns>0</ns>
  <id>335</id>
  <revision>
    <id>612</id>
    <timestamp>2009-01-01T23:42:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/rsrc/vms_get ==== Usage: vms_get poolId  Get the list of VMs within the specified pool.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="128" xml:space="preserve">==== vimsh hostsvc/rsrc/vms_get ====
Usage: vms_get poolId

Get the list of VMs within the specified pool.


[[Category: Vimsh]]</text>
    <sha1>cf6983902253df895b762b8507482e4886847c89</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/</title>
  <ns>0</ns>
  <id>336</id>
  <revision>
    <id>613</id>
    <timestamp>2009-01-01T23:47:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/ ====   [[hostsvc/storage/diagnostic/]]  [[hostsvc/storage/mockup/]]  [[hostsvc/storage/provider/]]  [[hostsvc/storage/datastore_browser_search]]  [[hostsvc/stor...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1525" xml:space="preserve">==== vimsh hostsvc/storage/ ====

 [[hostsvc/storage/diagnostic/]]
 [[hostsvc/storage/mockup/]]
 [[hostsvc/storage/provider/]]
 [[hostsvc/storage/datastore_browser_search]]
 [[hostsvc/storage/fs_info]]
 [[hostsvc/storage/hba_info]]
 [[hostsvc/storage/hba_rescan]]
 [[hostsvc/storage/info]]
 [[hostsvc/storage/iscsi_add_send_target]]
 [[hostsvc/storage/iscsi_add_static_target]]
 [[hostsvc/storage/iscsi_disable_chap]]
 [[hostsvc/storage/iscsi_discovery]]
 [[hostsvc/storage/iscsi_enable_chap]]
 [[hostsvc/storage/iscsi_ip_config]]
 [[hostsvc/storage/iscsi_ip_use_dhcp]]
 [[hostsvc/storage/iscsi_remove_send_target]]
 [[hostsvc/storage/iscsi_remove_static_target]]
 [[hostsvc/storage/iscsi_set_alias]]
 [[hostsvc/storage/iscsi_set_name]]
 [[hostsvc/storage/multipath_info]]
 [[hostsvc/storage/multipath_lun_setpolicy]]
 [[hostsvc/storage/multipath_path_disable]]
 [[hostsvc/storage/multipath_path_enable]]
 [[hostsvc/storage/partition_get]]
 [[hostsvc/storage/partition_layout_add]]
 [[hostsvc/storage/partition_layout_get]]
 [[hostsvc/storage/partition_layout_set]]
 [[hostsvc/storage/partition_remove]]
 [[hostsvc/storage/partition_spec_add]]
 [[hostsvc/storage/partition_spec_get]]
 [[hostsvc/storage/refresh]]
 [[hostsvc/storage/scsilun_info]]
 [[hostsvc/storage/software_iscsi_enabled]]
 [[hostsvc/storage/topology_info]]
 [[hostsvc/storage/upgrade_vm_layout]]
 [[hostsvc/storage/vmfs_attach_extent]]
 [[hostsvc/storage/vmfs_format]]
 [[hostsvc/storage/vmfs_rescan]]
 [[hostsvc/storage/vmfs_upgrade]]

[[Category: Vimsh]]</text>
    <sha1>54831e3ddfab98c7e33c8b564470fefa0fb6d0d0</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Vimsh: solo/</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>614</id>
    <parentid>552</parentid>
    <timestamp>2009-01-01T23:51:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="307" xml:space="preserve">==== vimsh solo/ ====
VirtualCenter solo allows a VirtualCenter based HostClient to connect directly to a  single VMware Server or ESX Server.

 [[solo/connect]]
 [[solo/environment]]
 [[solo/login]]
 [[solo/logout]]
 [[solo/querycfgopt]] 
 [[solo/querycfgoptdesc]]
 [[solo/registervm]]

[[Category: Vimsh]]</text>
    <sha1>3a0d14f541b5f0733e93436e325471ed05b8876b</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/net/pnic info</title>
  <ns>0</ns>
  <id>114</id>
  <revision>
    <id>615</id>
    <parentid>261</parentid>
    <timestamp>2009-01-02T00:10:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1833" xml:space="preserve">==== vimsh hostsvc/net/pnic_info ====
Usage: pnic_info [pnic]

Sets and displays the IP configuration for a physical network.
====example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/net/pnic_info
 (vim.host.PhysicalNic) [
   (vim.host.PhysicalNic) {
      dynamicType = &lt;unset&gt;,
      key = "key-vim.host.PhysicalNic-vmnic0",
      device = "vmnic0",
      pci = "02:00.0",
      driver = "e1000",
      linkSpeed = (vim.host.PhysicalNic.LinkSpeedDuplex) {
         dynamicType = &lt;unset&gt;,
         speedMb = 1000,
         duplex = true,
      },
      validLinkSpecification = (vim.host.PhysicalNic.LinkSpeedDuplex) [
         (vim.host.PhysicalNic.LinkSpeedDuplex) {
            dynamicType = &lt;unset&gt;,
            speedMb = 10,
            duplex = false,
         },
         (vim.host.PhysicalNic.LinkSpeedDuplex) {
            dynamicType = &lt;unset&gt;,
            speedMb = 10,
            duplex = true,
         },
         (vim.host.PhysicalNic.LinkSpeedDuplex) {
            dynamicType = &lt;unset&gt;,
            speedMb = 100,
            duplex = false,
         },
         (vim.host.PhysicalNic.LinkSpeedDuplex) {
            dynamicType = &lt;unset&gt;,
            speedMb = 100,
            duplex = true,
         },
         (vim.host.PhysicalNic.LinkSpeedDuplex) {
            dynamicType = &lt;unset&gt;,
            speedMb = 1000,
            duplex = true,
         }
      ],
      spec = (vim.host.PhysicalNic.Specification) {
         dynamicType = &lt;unset&gt;,
         ip = (vim.host.IpConfig) {
            dynamicType = &lt;unset&gt;,
            dhcp = false,
            ipAddress = "",
            subnetMask = "",
         },
         linkSpeed = (vim.host.PhysicalNic.LinkSpeedDuplex) null,
      },
      wakeOnLanSupported = false,
      mac = "00:0c:29:2e:a7:1d",
   }
 ]


[[Category: Vimsh]]</text>
    <sha1>66d080a12aab416daf7dbb260e6a53388cd01992</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/datastore browser search</title>
  <ns>0</ns>
  <id>337</id>
  <revision>
    <id>616</id>
    <timestamp>2009-01-02T05:11:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/datastore_browser_search ==== Usage: datastore_browser_search datastore  Search for files using the datastore browser.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="166" xml:space="preserve">==== vimsh hostsvc/storage/datastore_browser_search ====
Usage: datastore_browser_search datastore

Search for files using the datastore browser.

[[Category: vimsh]]</text>
    <sha1>fabb52dbab796c4729a33c650fb205f578bc2e8c</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/fs info</title>
  <ns>0</ns>
  <id>338</id>
  <revision>
    <id>617</id>
    <timestamp>2009-01-02T05:12:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/fs_info ==== Usage: fs_info  info Get the file system volume information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="121" xml:space="preserve">==== vimsh hostsvc/storage/fs_info ====
Usage: fs_info

info
Get the file system volume information.

[[Category: Vimsh]]</text>
    <sha1>323d47d1a7f7c9edb7e5e70933432a959031bd8d</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/hba info</title>
  <ns>0</ns>
  <id>339</id>
  <revision>
    <id>618</id>
    <timestamp>2009-01-02T05:13:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/storage/hba_info ==== Usage: hba_info  Get storage vmhba information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="103" xml:space="preserve">==== hostsvc/storage/hba_info ====
Usage: hba_info

Get storage vmhba information.

[[Category: Vimsh]]</text>
    <sha1>933b9c8f4d8558c6fd0137ee064cada795bdb565</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/hba rescan</title>
  <ns>0</ns>
  <id>340</id>
  <revision>
    <id>619</id>
    <timestamp>2009-01-02T05:14:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostvc/storage/hba_rescan ==== Usage: hba_rescan id  Set the iSCSI name for an iSCSI Hba.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="121" xml:space="preserve">==== vimsh hostvc/storage/hba_rescan ====
Usage: hba_rescan id

Set the iSCSI name for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>689d77c2d8fafd95775f9c73e09f1d141eaf297e</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/info</title>
  <ns>0</ns>
  <id>341</id>
  <revision>
    <id>620</id>
    <timestamp>2009-01-02T05:15:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/info ==== Usage: info  Get the storage system information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="106" xml:space="preserve">==== vimsh hostsvc/storage/info ====
Usage: info

Get the storage system information.

[[Category: Vimsh]]</text>
    <sha1>40918f10956411654fbeb4a0586089962736d7e3</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi add send target</title>
  <ns>0</ns>
  <id>342</id>
  <revision>
    <id>621</id>
    <timestamp>2009-01-02T05:16:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_add_send_target ==== Usage: iscsi_add_send_target iSCSIID address [port]  Add an iSCSI Send target entry for an iSCSI Hba.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="176" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_add_send_target ====
Usage: iscsi_add_send_target iSCSIID address [port]

Add an iSCSI Send target entry for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>3d5ef53aeab03bd1fb02eea54a0c7f98b4833d56</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi add static target</title>
  <ns>0</ns>
  <id>343</id>
  <revision>
    <id>622</id>
    <timestamp>2009-01-02T05:18:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_add_static_target ==== Usage: iscsi_add_static_target iSCSIID address name [port]  Add an iSCSI static target entry for an iSCSI Hba.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="187" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_add_static_target ====
Usage: iscsi_add_static_target iSCSIID address name [port]

Add an iSCSI static target entry for an iSCSI Hba.

[[Category: vimsh]]</text>
    <sha1>f6bb94e422e979d3cbe9a3beacccb6769050509b</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi disable chap</title>
  <ns>0</ns>
  <id>344</id>
  <revision>
    <id>623</id>
    <timestamp>2009-01-02T05:19:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_disable_chap ==== Usage: iscsi_disable_chap iSCSIID  Disable CHAP for an iSCSI Hba.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="137" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_disable_chap ====
Usage: iscsi_disable_chap iSCSIID

Disable CHAP for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>fbd29e21c19d9d154e269d12f0752301d2aa7943</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi discovery</title>
  <ns>0</ns>
  <id>345</id>
  <revision>
    <id>624</id>
    <timestamp>2009-01-02T05:20:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_discovery ==== Usage: iscsi_discovery iSCSIID sendTargetsEnabled staticTargetsEnabled  Update discovery settings for an iSCSI Hba.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="184" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_discovery ====
Usage: iscsi_discovery iSCSIID sendTargetsEnabled staticTargetsEnabled

Update discovery settings for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>a732c1cf240fba23e6a139d8159bd772f28e6df4</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi enable chap</title>
  <ns>0</ns>
  <id>346</id>
  <revision>
    <id>625</id>
    <timestamp>2009-01-02T05:21:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_enable_chap ==== Usage: iscsi_enable_chap iSCSIID name secret  Enable CHAP for an iSCSI Hba.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="146" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_enable_chap ====
Usage: iscsi_enable_chap iSCSIID name secret

Enable CHAP for an iSCSI Hba.

[[Category: vimsh]]</text>
    <sha1>65642d41693a83413660e723cca9c2d805e9bafc</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi ip config</title>
  <ns>0</ns>
  <id>347</id>
  <revision>
    <id>626</id>
    <timestamp>2009-01-02T05:22:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/storage/iscsi_ip_config ==== Usage: iscsi_ip_config iSCSIID address netmask gateway dns1 [dns2]  Update IP settings for an iSCSI Hba.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="167" xml:space="preserve">==== hostsvc/storage/iscsi_ip_config ====
Usage: iscsi_ip_config iSCSIID address netmask gateway dns1 [dns2]

Update IP settings for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>cbcb0b3d748c104fd1fe3d20878ceb2e6f1d4ffe</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi ip use dhcp</title>
  <ns>0</ns>
  <id>348</id>
  <revision>
    <id>627</id>
    <timestamp>2009-01-02T05:23:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_ip_use_dhcp ==== Usage: iscsi_ip_use_dhcp iSCSIID  Configure an iSCSI Hba to use DHCP for its IP configuration.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="165" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_ip_use_dhcp ====
Usage: iscsi_ip_use_dhcp iSCSIID

Configure an iSCSI Hba to use DHCP for its IP configuration.

[[Category: Vimsh]]</text>
    <sha1>023dca967bae0b92caad47b1a859a3f6e1e1645a</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi remove send target</title>
  <ns>0</ns>
  <id>349</id>
  <revision>
    <id>628</id>
    <timestamp>2009-01-02T05:24:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_remove_send_target ==== Usage: iscsi_remove_send_target iSCSIID address [port]  Remove an iSCSI send target for an iSCSI Hba.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="179" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_remove_send_target ====
Usage: iscsi_remove_send_target iSCSIID address [port]

Remove an iSCSI send target for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>2aa911b538d947f1901430c5475254b234ccf48c</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi remove static target</title>
  <ns>0</ns>
  <id>350</id>
  <revision>
    <id>629</id>
    <timestamp>2009-01-02T05:25:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_remove_static_target ==== Usage: iscsi_remove_static_target iSCSIID address name [port]  Remove an iSCSI static target for an iSCSI Hba.  [[Category: Vimsh...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="190" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_remove_static_target ====
Usage: iscsi_remove_static_target iSCSIID address name [port]

Remove an iSCSI static target for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>bb4ed32d7513255d4c69c08e519bacb76bc183d4</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi set alias</title>
  <ns>0</ns>
  <id>351</id>
  <revision>
    <id>630</id>
    <timestamp>2009-01-02T05:26:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_set_alias ==== Usage: iscsi_set_alias iSCSIID alias  Set the iSCSI name for an iSCSI Hba.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="143" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_set_alias ====
Usage: iscsi_set_alias iSCSIID alias

Set the iSCSI name for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>8647e039c0eb700e5607fec834b39cf9e723be90</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/iscsi set name</title>
  <ns>0</ns>
  <id>352</id>
  <revision>
    <id>631</id>
    <timestamp>2009-01-02T05:27:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/iscsi_set_name ==== Usage: iscsi_set_name iSCSIID name  Set the iSCSI name for an iSCSI Hba.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="140" xml:space="preserve">==== vimsh hostsvc/storage/iscsi_set_name ====
Usage: iscsi_set_name iSCSIID name

Set the iSCSI name for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>d0097aa5f910f097d1ee446484e06449711cb4d1</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/multipath info</title>
  <ns>0</ns>
  <id>353</id>
  <revision>
    <id>632</id>
    <timestamp>2009-01-02T05:29:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/multipath_info ==== Usage: multipath_info  Get storage multipath information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">==== vimsh hostsvc/storage/multipath_info ====
Usage: multipath_info

Get storage multipath information.

[[Category: Vimsh]]</text>
    <sha1>31ca142c13fc46788bf58877a2e8fbb3e56dbd3f</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/multipath lun setpolicy</title>
  <ns>0</ns>
  <id>354</id>
  <revision>
    <id>633</id>
    <timestamp>2009-01-02T05:30:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/multipath_lun_setpolicy ==== Usage: multipath_lun_setpolicy lunId policy prefer  Set the multipath policy for a lun.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="164" xml:space="preserve">==== vimsh hostsvc/storage/multipath_lun_setpolicy ====
Usage: multipath_lun_setpolicy lunId policy prefer

Set the multipath policy for a lun.

[[Category: Vimsh]]</text>
    <sha1>1356216f2bfdd6120fafdc041516f9302093dd8e</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/multipath path disable</title>
  <ns>0</ns>
  <id>355</id>
  <revision>
    <id>634</id>
    <timestamp>2009-01-02T05:30:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/storage/multipath_path_disable ==== Usage: multipath_path_disable path  Disable an enabled path for a lun.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="140" xml:space="preserve">==== hostsvc/storage/multipath_path_disable ====
Usage: multipath_path_disable path

Disable an enabled path for a lun.

[[Category: Vimsh]]</text>
    <sha1>dc7fc0e0c991a8be4e9c8fbca80e9c0361915aa9</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/multipath path enable</title>
  <ns>0</ns>
  <id>356</id>
  <revision>
    <id>635</id>
    <timestamp>2009-01-02T05:32:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/multipath_path_enable ==== Usage: multipath_path_enable path  Enable a disabled path for a Lun.   [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">==== vimsh hostsvc/storage/multipath_path_enable ====
Usage: multipath_path_enable path

Enable a disabled path for a Lun.


[[Category: Vimsh]]</text>
    <sha1>4f2af481ed798be3b3c88b5208d845084a7d38f1</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/partition get</title>
  <ns>0</ns>
  <id>357</id>
  <revision>
    <id>636</id>
    <timestamp>2009-01-02T05:33:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/partition_get ==== Usage: partition_get devname  Get the partition specification of a physical disk.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="148" xml:space="preserve">==== vimsh hostsvc/storage/partition_get ====
Usage: partition_get devname

Get the partition specification of a physical disk.

[[Category: Vimsh]]</text>
    <sha1>fad76c62e95175fbf5c1abf00801ce79b301d27f</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/partition layout add</title>
  <ns>0</ns>
  <id>358</id>
  <revision>
    <id>637</id>
    <timestamp>2009-01-02T05:35:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/partition_layout_add ==== Usage: partition_layout_add devname startBlock endBlock partitionType  Add a partition to a physical disk using layout format.  [[Categ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="200" xml:space="preserve">==== vimsh hostsvc/storage/partition_layout_add ====
Usage: partition_layout_add devname startBlock endBlock partitionType

Add a partition to a physical disk using layout format.

[[Category: Vimsh]]</text>
    <sha1>8113abc2828e49b8e7d207bd71651b4270243fee</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/partition layout get</title>
  <ns>0</ns>
  <id>359</id>
  <revision>
    <id>638</id>
    <timestamp>2009-01-02T05:35:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/partition_layout_get ==== Usage: partition_layout_get devname  Get the partition layout of a physical disk.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve">==== vimsh hostsvc/storage/partition_layout_get ====
Usage: partition_layout_get devname

Get the partition layout of a physical disk.

[[Category: Vimsh]]</text>
    <sha1>813fb44a581563cc3da5bcba94eccb867ea2984c</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/partition layout set</title>
  <ns>0</ns>
  <id>360</id>
  <revision>
    <id>639</id>
    <timestamp>2009-01-02T05:37:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/partition_layout_set ==== Usage: partition_layout_set devname layout  Set the partition layout on the disk. partition_layout_set /vmfs/devices/disk/vml.8888  0-1...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="233" xml:space="preserve">==== vimsh hostsvc/storage/partition_layout_set ====
Usage: partition_layout_set devname layout

Set the partition layout on the disk.
partition_layout_set /vmfs/devices/disk/vml.8888  0-1000-vmfs:1001-5000-vmfs:

[[Category: Vimsh]]</text>
    <sha1>ba20b8d9c350e6a7f84f3e13a1c660c6a7c85dde</sha1>
  </revision>
  <revision>
    <id>640</id>
    <parentid>639</parentid>
    <timestamp>2009-01-02T05:37:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="234" xml:space="preserve">==== vimsh hostsvc/storage/partition_layout_set ====
Usage: partition_layout_set devname layout

Set the partition layout on the disk.

partition_layout_set /vmfs/devices/disk/vml.8888  0-1000-vmfs:1001-5000-vmfs:

[[Category: Vimsh]]</text>
    <sha1>94c66c30100e8150a5335f391555e9f21a01c54c</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/partition remove</title>
  <ns>0</ns>
  <id>361</id>
  <revision>
    <id>641</id>
    <timestamp>2009-01-02T05:38:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/partition_remove ==== Usage: partition_remove devname int  Remove a partition from a physical disk.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="147" xml:space="preserve">==== vimsh hostsvc/storage/partition_remove ====
Usage: partition_remove devname int

Remove a partition from a physical disk.

[[Category: Vimsh]]</text>
    <sha1>baef420a4137fc1fb57ec1d689e16e52b5f7a508</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/partition spec add</title>
  <ns>0</ns>
  <id>362</id>
  <revision>
    <id>642</id>
    <timestamp>2009-01-02T05:40:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/partition_spec_add ==== Usage: partition_spec_add [OPTIONS] devname  Add a partition to a physical disk using specification format.   Options:    --partition=int...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="487" xml:space="preserve">==== vimsh hostsvc/storage/partition_spec_add ====
Usage: partition_spec_add [OPTIONS] devname

Add a partition to a physical disk using specification format.

 Options:
   --partition=int
       Partition  number.
 
   --startector=int
       Start sector.
 
   --endsector=int
       End sector.
 
   --typeid=fs_type
       Type of data in the file system.
 
   --logical=bool
       If it is logical partition.
 
   --attributes=byte
       Partition attributes.

[[Category: Vimsh]]</text>
    <sha1>6a7190e18073b05c8152bf4dadb8a3c50fb2da04</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/partition spec get</title>
  <ns>0</ns>
  <id>363</id>
  <revision>
    <id>643</id>
    <timestamp>2009-01-02T05:41:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/partition_spec_get ==== Usage: partition_spec_get devname  Get the partition specification of a physical disk.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="158" xml:space="preserve">==== vimsh hostsvc/storage/partition_spec_get ====
Usage: partition_spec_get devname

Get the partition specification of a physical disk.

[[Category: Vimsh]]</text>
    <sha1>450224df0227ff96210808bde9d317393df3b83e</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/refresh</title>
  <ns>0</ns>
  <id>364</id>
  <revision>
    <id>644</id>
    <timestamp>2009-01-02T05:42:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/refresh ==== Usage: refresh  Refresh storage system properties.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="111" xml:space="preserve">==== vimsh hostsvc/storage/refresh ====
Usage: refresh

Refresh storage system properties.

[[Category: Vimsh]]</text>
    <sha1>e1ba066d77146fabc7cfaf700f648837dd453f3e</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/scsilun info</title>
  <ns>0</ns>
  <id>365</id>
  <revision>
    <id>645</id>
    <timestamp>2009-01-02T05:43:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/scsilun_info ==== Usage: scsilun_info  Get storage vmhba information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="117" xml:space="preserve">==== vimsh hostsvc/storage/scsilun_info ====
Usage: scsilun_info

Get storage vmhba information.

[[Category: Vimsh]]</text>
    <sha1>8ba6de310b8252d052563eff6150355fda1289e4</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/software iscsi enabled</title>
  <ns>0</ns>
  <id>366</id>
  <revision>
    <id>646</id>
    <timestamp>2009-01-02T05:44:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/software_iscsi_enabled ==== Usage: software_iscsi_enabled enabled  Add an iSCSI Send target entry for an iSCSI Hba.  [[Category; Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">==== vimsh hostsvc/storage/software_iscsi_enabled ====
Usage: software_iscsi_enabled enabled

Add an iSCSI Send target entry for an iSCSI Hba.

[[Category; Vimsh]]</text>
    <sha1>08aa2cba8a794894d6ed922675fd432dddadc068</sha1>
  </revision>
  <revision>
    <id>647</id>
    <parentid>646</parentid>
    <timestamp>2009-01-02T05:44:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">==== vimsh hostsvc/storage/software_iscsi_enabled ====
Usage: software_iscsi_enabled enabled

Add an iSCSI Send target entry for an iSCSI Hba.

[[Category: Vimsh]]</text>
    <sha1>c2861cb3616933043c3c654ae7155ecba5e18a09</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/topology info</title>
  <ns>0</ns>
  <id>367</id>
  <revision>
    <id>648</id>
    <timestamp>2009-01-02T05:45:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/topology_info ==== Usage: topology_info  Get storage topology information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">==== vimsh hostsvc/storage/topology_info ====
Usage: topology_info

Get storage topology information.

[[Category: Vimsh]]</text>
    <sha1>ef4782f1ecc5d6f63253a09c7f16343db2d315ef</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/upgrade vm layout</title>
  <ns>0</ns>
  <id>368</id>
  <revision>
    <id>649</id>
    <timestamp>2009-01-02T05:46:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/upgrade_vm_layout ==== Usage: upgrade_vm_layout  Relayout all legacy Vms from COS to a VMFS volume.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="147" xml:space="preserve">==== vimsh hostsvc/storage/upgrade_vm_layout ====
Usage: upgrade_vm_layout

Relayout all legacy Vms from COS to a VMFS volume.

[[Category: Vimsh]]</text>
    <sha1>d393a1c97ab44c8f4ea9bd63a1fae7fa8eecf843</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/vmfs attach extent</title>
  <ns>0</ns>
  <id>369</id>
  <revision>
    <id>650</id>
    <timestamp>2009-01-02T05:47:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/vmfs_attach_extent ==== Usage: vmfs_attach_extent VmfsName scsiDiskName partitionNum  Extend the VMFS by attaching a new extent.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="176" xml:space="preserve">==== vimsh hostsvc/storage/vmfs_attach_extent ====
Usage: vmfs_attach_extent VmfsName scsiDiskName partitionNum

Extend the VMFS by attaching a new extent.

[[Category: Vimsh]]</text>
    <sha1>364699d453e726a9933ac08ca3cdb4602dc25994</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/vmfs format</title>
  <ns>0</ns>
  <id>370</id>
  <revision>
    <id>651</id>
    <timestamp>2009-01-02T05:48:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/vmfs_format ==== Usage: vmfs_format volumeName blockSizeMb majorVersion scsiDiskId partitionNum  Format a new VMFS on a scsi partition.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="183" xml:space="preserve">==== vimsh hostsvc/storage/vmfs_format ====
Usage: vmfs_format volumeName blockSizeMb majorVersion scsiDiskId partitionNum

Format a new VMFS on a scsi partition.

[[Category: Vimsh]]</text>
    <sha1>4e3587139964898f4431babeae383b650fe36c6f</sha1>
  </revision>
</page>
<page arvcontinue="20090101233309|603">
  <title>Hostsvc/storage/vmfs rescan</title>
  <ns>0</ns>
  <id>371</id>
  <revision>
    <id>652</id>
    <timestamp>2009-01-02T05:49:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/vmfs_rescan ==== Usage: vmfs_rescan  Rescan the vmfs file system volume information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== vimsh hostsvc/storage/vmfs_rescan ====
Usage: vmfs_rescan

Rescan the vmfs file system volume information.

[[Category: Vimsh]]</text>
    <sha1>902d500d3b5acbde8714ef3d8bf20a639319124a</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/vmfs upgrade</title>
  <ns>0</ns>
  <id>372</id>
  <revision>
    <id>653</id>
    <timestamp>2009-01-02T05:50:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/vmfs_upgrade ==== Usage: vmfs_upgrade VmfsName  Upgrade a VMFS2 volume to VMFS3.  [Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="127" xml:space="preserve">==== vimsh hostsvc/storage/vmfs_upgrade ====
Usage: vmfs_upgrade VmfsName

Upgrade a VMFS2 volume to VMFS3.

[Category: Vimsh]]</text>
    <sha1>5112c81a44c7eb48d6641f999ca854e4df51a286</sha1>
  </revision>
  <revision>
    <id>654</id>
    <parentid>653</parentid>
    <timestamp>2009-01-02T05:50:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="128" xml:space="preserve">==== vimsh hostsvc/storage/vmfs_upgrade ====
Usage: vmfs_upgrade VmfsName

Upgrade a VMFS2 volume to VMFS3.

[[Category: Vimsh]]</text>
    <sha1>42f06c5cb6e0525c6a4ae00c148334244160f241</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/diagnostic/</title>
  <ns>0</ns>
  <id>373</id>
  <revision>
    <id>655</id>
    <timestamp>2009-01-02T05:53:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/diagnostic/ ====   [[hostsvc/storage/diagnostic/activate]]  [[hostsvc/storage/diagnostic/create]]  [[hostsvc/storage/diagnostic/deactivate]]  [[hostsvc/storage/d...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="381" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/ ====

 [[hostsvc/storage/diagnostic/activate]]
 [[hostsvc/storage/diagnostic/create]]
 [[hostsvc/storage/diagnostic/deactivate]]
 [[hostsvc/storage/diagnostic/get_active]]
 [[hostsvc/storage/diagnostic/query_available]]
 [[hostsvc/storage/diagnostic/query_create_desc]]
 [[hostsvc/storage/diagnostic/query_create_option]]

[[Category: Vimsh]]</text>
    <sha1>af08a13952a90dd925112f12036d17e59206f0f2</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/diagnostic/activate</title>
  <ns>0</ns>
  <id>374</id>
  <revision>
    <id>656</id>
    <timestamp>2009-01-02T22:14:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/diagnostic/activate ==== Usage: activate diskName partition  Activate a vmkernel diagnostic paritition.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/activate ====
Usage: activate diskName partition

Activate a vmkernel diagnostic paritition.

[[Category: Vimsh]]</text>
    <sha1>21a9ce95109d7ad5f84529119102eeeb6b3ce460</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/diagnostic/create</title>
  <ns>0</ns>
  <id>375</id>
  <revision>
    <id>657</id>
    <timestamp>2009-01-02T22:15:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/diagnostic/create ==== Usage: create diskName storage-type  Create a diagnostic partition according to specification.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="165" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/create ====
Usage: create diskName storage-type

Create a diagnostic partition according to specification.

[[Category: Vimsh]]</text>
    <sha1>b69c7e84b3f1670c64d8c3f17e5ec30f612a2fe9</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/diagnostic/deactivate</title>
  <ns>0</ns>
  <id>376</id>
  <revision>
    <id>658</id>
    <timestamp>2009-01-02T22:16:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/storage/diagnostic/deactivate ==== Usage: deactivate  Deactivate a vmkernel diagnostic paritition.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== hostsvc/storage/diagnostic/deactivate ====
Usage: deactivate

Deactivate a vmkernel diagnostic paritition.

[[Category: Vimsh]]</text>
    <sha1>ec622cc4acc194aa2fa17b813962eef7073d8073</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/diagnostic/get active</title>
  <ns>0</ns>
  <id>377</id>
  <revision>
    <id>659</id>
    <timestamp>2009-01-02T22:17:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/storage/diagnostic/get_active ==== Usage: Get the active vmkernel diagnostic partition information.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="133" xml:space="preserve">==== hostsvc/storage/diagnostic/get_active ====
Usage: Get the active vmkernel diagnostic partition information.

[[Category: Vimsh]]</text>
    <sha1>a7fb0e7e4ba532f5a07daafe46039ed0064fb3ee</sha1>
  </revision>
  <revision>
    <id>663</id>
    <parentid>659</parentid>
    <timestamp>2009-01-02T22:22:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="531" xml:space="preserve">==== hostsvc/storage/diagnostic/get_active ====
Usage: Get the active vmkernel diagnostic partition information.

====Example output====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/storage/diagnostic/get_active
 (vim.host.DiagnosticPartition) {
    dynamicType = &lt;unset&gt;,
    storageType = "directAttached",
    diagnosticType = "singleHost",
    slots = 1,
    id = (vim.host.ScsiDisk.Partition) {
       dynamicType = &lt;unset&gt;,
       diskName = "vmhba2:0:0",
       partition = 9,
    },
 }

[[Category: Vimsh]]</text>
    <sha1>390149c4f25542e604b37c4cb5b0919824042679</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/diagnostic/query available</title>
  <ns>0</ns>
  <id>378</id>
  <revision>
    <id>660</id>
    <timestamp>2009-01-02T22:18:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/diagnostic/query_available ==== Usage: Retrieve the list of available diagnostic partitions.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="140" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/query_available ====
Usage: Retrieve the list of available diagnostic partitions.

[[Category: vimsh]]</text>
    <sha1>9c2d01353ec2c6b1d1358042b2770e2a09632c37</sha1>
  </revision>
  <revision>
    <id>664</id>
    <parentid>660</parentid>
    <timestamp>2009-01-02T22:24:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="614" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/query_available ====
Usage: Retrieve the list of available diagnostic partitions.
==== Example output ==== 
# vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/storage/diagnostic/query_available
 (vim.host.DiagnosticPartition) [
    (vim.host.DiagnosticPartition) {
       dynamicType = &lt;unset&gt;,
       storageType = "directAttached",
       diagnosticType = "singleHost",
       slots = 1,
       id = (vim.host.ScsiDisk.Partition) {
          dynamicType = &lt;unset&gt;,
          diskName = "vmhba2:0:0",
          partition = 9,
       },
    }
 ]

[[Category: vimsh]]</text>
    <sha1>9b116d83a1d67286b608d2a7eb75a01a52d446d8</sha1>
  </revision>
  <revision>
    <id>665</id>
    <parentid>664</parentid>
    <timestamp>2009-01-02T22:24:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="615" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/query_available ====
Usage: Retrieve the list of available diagnostic partitions.
==== Example output ==== 
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/storage/diagnostic/query_available
 (vim.host.DiagnosticPartition) [
    (vim.host.DiagnosticPartition) {
       dynamicType = &lt;unset&gt;,
       storageType = "directAttached",
       diagnosticType = "singleHost",
       slots = 1,
       id = (vim.host.ScsiDisk.Partition) {
          dynamicType = &lt;unset&gt;,
          diskName = "vmhba2:0:0",
          partition = 9,
       },
    }
 ]

[[Category: vimsh]]</text>
    <sha1>5b5e3bc4cf51226db7722f30c320ad600fa0fdb3</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/diagnostic/query create desc</title>
  <ns>0</ns>
  <id>379</id>
  <revision>
    <id>661</id>
    <timestamp>2009-01-02T22:19:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/diagnostic/query_create_desc ==== Usage: query_create_desc diskName diagnostic-type  Query for the diagnostic creation description for a disk.  [[Category: Vimsh...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="190" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/query_create_desc ====
Usage: query_create_desc diskName diagnostic-type

Query for the diagnostic creation description for a disk.

[[Category: Vimsh]]</text>
    <sha1>dc1fa4dac202019a700721863cbc260d3ff51290</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/diagnostic/query create option</title>
  <ns>0</ns>
  <id>380</id>
  <revision>
    <id>662</id>
    <timestamp>2009-01-02T22:19:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/diagnostic/query_create_option ==== Usage: query_create_option storage-type diagnostic-type  Retrieve the list of disks that can be used to contain a diagnostic ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="219" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/query_create_option ====
Usage: query_create_option storage-type diagnostic-type

Retrieve the list of disks that can be used to contain a diagnostic partition.

[[Category: Vimsh]]</text>
    <sha1>e1e08c9fb51999ad8cd16a23c3552f21a3937dd2</sha1>
  </revision>
  <revision>
    <id>666</id>
    <parentid>662</parentid>
    <timestamp>2009-01-02T22:30:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="422" xml:space="preserve">==== vimsh hostsvc/storage/diagnostic/query_create_option ====
Usage: query_create_option storage-type diagnostic-type

Retrieve the list of disks that can be used to contain a diagnostic partition.

==== Example output ====

 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/storage/diagnostic/query_create_option directAttached singleHost
 (vim.host.DiagnosticPartition.CreateOption) []


[[Category: Vimsh]]</text>
    <sha1>567bac6ec6ec3511d0e9dfd153be2386e0232929</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/</title>
  <ns>0</ns>
  <id>381</id>
  <revision>
    <id>667</id>
    <timestamp>2009-01-02T22:34:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/ ====   [[hostsvc/storage/mockup/clear]]  [[hostsvc/storage/mockup/hostbusadapter_add]]  [[hostsvc/storage/mockup/hostbusadapter_remove]]  [[hostsvc/stora...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="497" xml:space="preserve">==== vimsh hostsvc/storage/mockup/ ====

 [[hostsvc/storage/mockup/clear]]
 [[hostsvc/storage/mockup/hostbusadapter_add]]
 [[hostsvc/storage/mockup/hostbusadapter_remove]]
 [[hostsvc/storage/mockup/multipath_path_activate]]
 [[hostsvc/storage/mockup/scsidisk_add]]
 [[hostsvc/storage/mockup/scsidisk_remove]]
 [[hostsvc/storage/mockup/scsilun_add]]
 [[hostsvc/storage/mockup/scsilun_remove]]
 [[hostsvc/storage/mockup/topology_add]]
 [[hostsvc/storage/mockup/topology_remove]]

[[Category: Vimsh]]</text>
    <sha1>4537781b7c6de2a4563e593554a2cf8dfda26d37</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/clear</title>
  <ns>0</ns>
  <id>382</id>
  <revision>
    <id>668</id>
    <timestamp>2009-01-02T22:35:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/clear ==== Usage: clear  Clears the mockup implementation for host storage configuration.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">==== vimsh hostsvc/storage/mockup/clear ====
Usage: clear

Clears the mockup implementation for host storage configuration.

[[Category: vimsh]]</text>
    <sha1>839dc2df8dd395a6c2a735c8eada698b0a1499f4</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/hostbusadapter add</title>
  <ns>0</ns>
  <id>383</id>
  <revision>
    <id>669</id>
    <timestamp>2009-01-02T22:36:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/hostbusadapter_add ==== Usage: hostbusadapter_add [OPTIONS] id transportType pci_id  Adds a host bus adapter.   Options:    --bus=int        Bus number of...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="416" xml:space="preserve">==== vimsh hostsvc/storage/mockup/hostbusadapter_add ====
Usage: hostbusadapter_add [OPTIONS] id transportType pci_id

Adds a host bus adapter.

 Options:
   --bus=int
       Bus number of the host bus adapter.
 
   --status=string
       Operational status of host bus adapter.
 
   --model=string
       Model of host bus adapter.
 
   --driver=string
       Device driver of host bus adapter.

[[Category: Vimsh]]</text>
    <sha1>cac9dabe1f49a29b9b67c3d4fe392905fcfb9958</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/hostbusadapter remove</title>
  <ns>0</ns>
  <id>384</id>
  <revision>
    <id>670</id>
    <timestamp>2009-01-02T22:37:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/hostbusadapter_remove ==== Usage: hostbusadapter_remove id  Removes a SCSI protocol controller.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="150" xml:space="preserve">==== vimsh hostsvc/storage/mockup/hostbusadapter_remove ====
Usage: hostbusadapter_remove id

Removes a SCSI protocol controller.

[[Category: vimsh]]</text>
    <sha1>deec12fac24a81faf9a123757ab1df907f97774f</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/multipath path activate</title>
  <ns>0</ns>
  <id>385</id>
  <revision>
    <id>671</id>
    <timestamp>2009-01-02T22:38:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/multipath_path_activate ==== Usage: multipath_path_activate path  Activate an enabled path for a lun.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="156" xml:space="preserve">==== vimsh hostsvc/storage/mockup/multipath_path_activate ====
Usage: multipath_path_activate path

Activate an enabled path for a lun.

[[Category: vimsh]]</text>
    <sha1>b10443eb2509b64ce87ba58e92d95f2677a995d6</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/scsidisk add</title>
  <ns>0</ns>
  <id>386</id>
  <revision>
    <id>672</id>
    <timestamp>2009-01-02T22:40:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/scsidisk_add ==== Usage: scsidisk_add [OPTIONS] lunId vmDeviceName blocks blocksize  Adds a physical SCSI disk.   Options:    --canonicalName=scsi_lun_vmh...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="556" xml:space="preserve">==== vimsh hostsvc/storage/mockup/scsidisk_add ====
Usage: scsidisk_add [OPTIONS] lunId vmDeviceName blocks blocksize

Adds a physical SCSI disk.

 Options:
   --canonicalName=scsi_lun_vmhba
       Canonical vmhba name of the SCSI device.
 
   --vendor=string
       Vendor.
 
   --model=string
       Model.
 
   --revision=string
       SCSI device revision.
 
   --level=int
       SCSI level.
 
   --status=string
       Operational status.
 
   --serialNumber=string
       Serial number.
 
   --queueDepth=int
       Queue depth.

[[Category: vimsh]]</text>
    <sha1>c9f21e7084286fc60bcbb16b0dd8c2dffe3362c4</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/scsidisk remove</title>
  <ns>0</ns>
  <id>387</id>
  <revision>
    <id>673</id>
    <timestamp>2009-01-02T22:41:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/scsidisk_remove ==== Usage: scsidisk_remove devname  Removes a physical disk.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">==== vimsh hostsvc/storage/mockup/scsidisk_remove ====
Usage: scsidisk_remove devname

Removes a physical disk.

[[Category: Vimsh]]</text>
    <sha1>3fb1f34a4714db745f2b698e18fe82200450c579</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/scsilun add</title>
  <ns>0</ns>
  <id>388</id>
  <revision>
    <id>674</id>
    <timestamp>2009-01-02T22:42:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/scsilun_add ==== Usage: scsilun_add [OPTIONS] lunId scsiType vmScsiType vmDeviceName  Adds a physical SCSI LUN.  LUN must not be a disk.   Options:    --c...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="581" xml:space="preserve">==== vimsh hostsvc/storage/mockup/scsilun_add ====
Usage: scsilun_add [OPTIONS] lunId scsiType vmScsiType vmDeviceName

Adds a physical SCSI LUN.  LUN must not be a disk.

 Options:
   --canonicalName=scsi_lun_vmhba
       Canonical vmhba name of the SCSI device.
 
   --vendor=string
       Vendor.
 
   --model=string
       Model.
 
   --revision=string
       SCSI device revision.
 
   --level=int
       SCSI level.
 
   --status=string
       Operational status.
 
   --serialNumber=string
       Serial number.
 
   --queueDepth=int
       Queue depth.

[[Category: Vimsh]]</text>
    <sha1>d5d095b3a30d3c784e258a186b64b19bf9c1e0bc</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/scsilun remove</title>
  <ns>0</ns>
  <id>389</id>
  <revision>
    <id>675</id>
    <timestamp>2009-01-02T22:43:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/scsilun_remove ==== Usage: scsilun_remove lunId  Removes a physical SCSI LUN.  LUN must not be a disk.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="157" xml:space="preserve">==== vimsh hostsvc/storage/mockup/scsilun_remove ====
Usage: scsilun_remove lunId

Removes a physical SCSI LUN.  LUN must not be a disk.

[[Category: vimsh]]</text>
    <sha1>4b7be87f30866e03de5ebd37eeeb1e0f35414244</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/topology add</title>
  <ns>0</ns>
  <id>390</id>
  <revision>
    <id>676</id>
    <timestamp>2009-01-02T22:44:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/storage/mockup/topology_add ==== Usage: topology_add hba target lun lunId  Adds topology entry from HBA through target to a LUN  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="161" xml:space="preserve">==== hostsvc/storage/mockup/topology_add ====
Usage: topology_add hba target lun lunId

Adds topology entry from HBA through target to a LUN

[[Category: vimsh]]</text>
    <sha1>189839d16ddf289d25225e6c7dd03b736ec88e53</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/mockup/topology remove</title>
  <ns>0</ns>
  <id>391</id>
  <revision>
    <id>677</id>
    <timestamp>2009-01-02T22:44:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/mockup/topology_remove ==== Usage: topology_remove hba target lun lunId  Removes topology entry.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">==== vimsh hostsvc/storage/mockup/topology_remove ====
Usage: topology_remove hba target lun lunId

Removes topology entry.

[[Category: Vimsh]]</text>
    <sha1>ae6458f5ee9b0613930866126e719bfc7e3f4f72</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/provider/</title>
  <ns>0</ns>
  <id>392</id>
  <revision>
    <id>678</id>
    <timestamp>2009-01-02T22:46:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/provider/ ====   [[hostsvc/storage/provider/device_info]]  [[hostsvc/storage/provider/enable_stack_trace]]  [[hostsvc/storage/provider/fs_info]]  [[Category: Vim...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="192" xml:space="preserve">==== vimsh hostsvc/storage/provider/ ====

 [[hostsvc/storage/provider/device_info]]
 [[hostsvc/storage/provider/enable_stack_trace]]
 [[hostsvc/storage/provider/fs_info]]

[[Category: Vimsh]]</text>
    <sha1>380ea7710867823bec46bc0cfc9c34c59904d45a</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/provider/device info</title>
  <ns>0</ns>
  <id>393</id>
  <revision>
    <id>679</id>
    <timestamp>2009-01-02T22:47:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/provider/device_info ==== Usage: device_info  Get storage device information through provider.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="142" xml:space="preserve">==== vimsh hostsvc/storage/provider/device_info ====
Usage: device_info

Get storage device information through provider.

[[Category: Vimsh]]</text>
    <sha1>e4820c3e237062b1c8892cf13079d5774635cc0b</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/provider/enable stack trace</title>
  <ns>0</ns>
  <id>394</id>
  <revision>
    <id>680</id>
    <timestamp>2009-01-02T22:48:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>New page: ==== vimsh hostsvc/storage/provider/enable_stack_trace ==== Usage: enable_stack_trace  Get storage device information through provider.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="156" xml:space="preserve">==== vimsh hostsvc/storage/provider/enable_stack_trace ====
Usage: enable_stack_trace

Get storage device information through provider.

[[Category: Vimsh]]</text>
    <sha1>82c7893356178ca3c6b88e9b92ea1d3ba18e2a60</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/provider/fs info</title>
  <ns>0</ns>
  <id>395</id>
  <revision>
    <id>681</id>
    <timestamp>2009-01-02T22:48:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/storage/provider/fs_info ==== Usage: fs_info  Get storage device information through provider.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== vimsh hostsvc/storage/provider/fs_info ====
Usage: fs_info

Get storage device information through provider.

[[Category: vimsh]]</text>
    <sha1>3702a1b5fe29718fae53bdd4aafe3688f4a28686</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/vmotion/</title>
  <ns>0</ns>
  <id>396</id>
  <revision>
    <id>682</id>
    <timestamp>2009-01-02T22:53:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/vmotion/ ====   [[hostsvc/vmotion/ipconfig_get]]  [[hostsvc/vmotion/ipconfig_set]]  [[hostsvc/vmotion/netconfig_get]]    [[hostsvc/vmotion/vnic_set]]  [[hostsvc/vmotion/...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="221" xml:space="preserve">==== vimsh hostsvc/vmotion/ ====

 [[hostsvc/vmotion/ipconfig_get]]
 [[hostsvc/vmotion/ipconfig_set]]
 [[hostsvc/vmotion/netconfig_get]]  
 [[hostsvc/vmotion/vnic_set]]
 [[hostsvc/vmotion/vnic_unset]]

[[Category: Vimsh]]</text>
    <sha1>e1698f5ca862da1790efe865ce3a950bd578b784</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/vmotion/ipconfig get</title>
  <ns>0</ns>
  <id>397</id>
  <revision>
    <id>683</id>
    <timestamp>2009-01-02T22:54:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/vmotion/ipconfig_get ==== Usage: Get the current IP configuration of the VMotion NIC.  [[Category: Vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">==== vimsh hostsvc/vmotion/ipconfig_get ====
Usage: Get the current IP configuration of the VMotion NIC.

[[Category: Vimsh]]</text>
    <sha1>7db1aeb0b1ee611be20af62e6dcf314a71a2f180</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/vmotion/ipconfig set</title>
  <ns>0</ns>
  <id>398</id>
  <revision>
    <id>684</id>
    <timestamp>2009-01-02T22:55:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== hostsvc/vmotion/ipconfig_set ==== Usage: ipconfig_set [OPTIONS]  Set the current IP configuration of the VMotion NIC.   Options:    --ip-dhcp=bool        Enables or disables DHCP conf...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="315" xml:space="preserve">==== hostsvc/vmotion/ipconfig_set ====
Usage: ipconfig_set [OPTIONS]

Set the current IP configuration of the VMotion NIC.

 Options:
   --ip-dhcp=bool
       Enables or disables DHCP configuration.
 
   --ip-address=ip_address
       IP address.
 
   --ip-subnet=ip_address
       Subnet mask.

[[Category: vimsh]]</text>
    <sha1>3005a049369ad100345be772e66bf15030dfa1db</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/vmotion/netconfig get</title>
  <ns>0</ns>
  <id>399</id>
  <revision>
    <id>685</id>
    <timestamp>2009-01-02T22:56:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/vmotion/netconfig_get ==== Usage: Get the VMotion network configuration.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="112" xml:space="preserve">==== vimsh hostsvc/vmotion/netconfig_get ====
Usage: Get the VMotion network configuration.

[[Category: vimsh]]</text>
    <sha1>5f0406edf4e35500a6c5cf6a92af58e0fc48dd3a</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/vmotion/vnic set</title>
  <ns>0</ns>
  <id>400</id>
  <revision>
    <id>686</id>
    <timestamp>2009-01-02T22:56:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/vmotion/vnic_set ==== Usage: vnic_set vnic  Select a VirtualNic to be used as the VMotion NIC.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">==== vimsh hostsvc/vmotion/vnic_set ====
Usage: vnic_set vnic

Select a VirtualNic to be used as the VMotion NIC.

[[Category: vimsh]]</text>
    <sha1>503ec13164cf3e72c73450f70a071ed54a1abffa</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/vmotion/vnic unset</title>
  <ns>0</ns>
  <id>401</id>
  <revision>
    <id>687</id>
    <timestamp>2009-01-02T22:57:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vimsh hostsvc/vmotion/vnic_unset ==== Usage: vnic_unset  Unconfigure a VirtualNic to be used as the VMotion NIC.  [[Category: vimsh]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="138" xml:space="preserve">==== vimsh hostsvc/vmotion/vnic_unset ====
Usage: vnic_unset

Unconfigure a VirtualNic to be used as the VMotion NIC.

[[Category: vimsh]]</text>
    <sha1>119555b0667f026a2e9a947d127d576f03f11edb</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/storage/info</title>
  <ns>0</ns>
  <id>341</id>
  <revision>
    <id>688</id>
    <parentid>620</parentid>
    <timestamp>2009-01-02T23:53:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="26802" xml:space="preserve">==== vimsh hostsvc/storage/info ====
Usage: info

Get the storage system information.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/storage/info
 (vim.host.StorageDeviceInfo) {
   dynamicType = &lt;unset&gt;,
   hostBusAdapter = (vim.host.HostBusAdapter) [
      (vim.host.InternetScsiHba) {
         dynamicType = &lt;unset&gt;,
         key = "key-vim.host.InternetScsiHba-vmhba32",
         device = "vmhba32",
         bus = -1,
         status = "unknown",
         model = "iSCSI Software Adapter",
         driver = "iscsi_mod",
         pci = "UNKNOWN - NULL PCI DEV IN VMKCTL",
         isSoftwareBased = true,
         discoveryCapabilities = (vim.host.InternetScsiHba.DiscoveryCapabilities) {
            dynamicType = &lt;unset&gt;,
            iSnsDiscoverySettable = false,
            slpDiscoverySettable = false,
            staticTargetDiscoverySettable = false,
            sendTargetsDiscoverySettable = false,
         },
         discoveryProperties = (vim.host.InternetScsiHba.DiscoveryProperties) {
            dynamicType = &lt;unset&gt;,
            iSnsDiscoveryEnabled = false,
            iSnsDiscoveryMethod = &lt;unset&gt;,
            iSnsHost = &lt;unset&gt;,
            slpDiscoveryEnabled = false,
            slpDiscoveryMethod = &lt;unset&gt;,
            slpHost = &lt;unset&gt;,
            staticTargetDiscoveryEnabled = false,
            sendTargetsDiscoveryEnabled = true,
         },
         authenticationCapabilities = (vim.host.InternetScsiHba.AuthenticationCapabilities) {
            dynamicType = &lt;unset&gt;,
            chapAuthSettable = true,
            krb5AuthSettable = false,
            srpAuthSettable = false,
            spkmAuthSettable = false,
         },
         authenticationProperties = (vim.host.InternetScsiHba.AuthenticationProperties) {
            dynamicType = &lt;unset&gt;,
            chapAuthEnabled = false,
            chapName = &lt;unset&gt;,
            chapSecret = &lt;unset&gt;,
         },
         ipCapabilities = (vim.host.InternetScsiHba.IPCapabilities) {
            dynamicType = &lt;unset&gt;,
            addressSettable = false,
            ipConfigurationMethodSettable = false,
            subnetMaskSettable = false,
            defaultGatewaySettable = false,
            primaryDnsServerAddressSettable = false,
            alternateDnsServerAddressSettable = false,
         },
         ipProperties = (vim.host.InternetScsiHba.IPProperties) {
            dynamicType = &lt;unset&gt;,
            mac = &lt;unset&gt;,
            address = &lt;unset&gt;,
            dhcpConfigurationEnabled = false,
            subnetMask = &lt;unset&gt;,
            defaultGateway = &lt;unset&gt;,
            primaryDnsServerAddress = &lt;unset&gt;,
            alternateDnsServerAddress = &lt;unset&gt;,
         },
         iScsiName = "iqn.2009-01.com.vmware:localhost-15682e24",
         iScsiAlias = "localhost.example.com",
         configuredSendTarget = (vim.host.InternetScsiHba.SendTarget) [
            (vim.host.InternetScsiHba.SendTarget) {
               dynamicType = &lt;unset&gt;,
               address = "10.10.0.10",
               port = 3260,
            }
         ],
         maxSpeedMb = &lt;unset&gt;,
         currentSpeedMb = &lt;unset&gt;,
      },
      (vim.host.BlockHba) {
         dynamicType = &lt;unset&gt;,
         key = "key-vim.host.BlockHba-vmhba0",
         device = "vmhba0",
         bus = 0,
         status = "unknown",
         model = "82371AB/EB/MB PIIX4 IDE",
         driver = "ide",
         pci = "00:07.1",
      },
      (vim.host.ParallelScsiHba) {
         dynamicType = &lt;unset&gt;,
         key = "key-vim.host.ParallelScsiHba-vmhba1",
         device = "vmhba1",
         bus = 0,
         status = "unknown",
         model = "53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI",
         driver = "mptscsi_2xx",
         pci = "00:10.0",
      }
   ],
   scsiLun = (vim.host.ScsiLun) [
      (vim.host.ScsiLun) {
         dynamicType = &lt;unset&gt;,
         deviceName = "/vmfs/devices/genide/vmhba0:0:0",
         deviceType = "cdrom",
         key = "key-vim.host.ScsiLun-vmhba0:0:0",
         uuid = "000a000200654e56261303a12343a54303a4c30",
         canonicalName = "vmhba0:0:0",
         lunType = "cdrom",
         vendor = "VMware  ",
         model = "Block device    ",
         revision = "1.0 ",
         scsiLevel = 3,
         serialNumber = "unavailable",
         durableName = (vim.host.ScsiLun.DurableName) null,
         standardInquiry = (byte) [
            10,
            0,
            2,
            0,
            32,
            0,
            0,
            115,
            86,
            77,
            119,
            97,
            114,
            101,
            32,
            32,
            66,
            108,
            111,
            99,
            107,
            32,
            100,
            101,
            118,
            105,
            99,
            101,
            32,
            32,
            32,
            32,
            49,
            46,
            48,
            32,
            0,
            57,
            0,
            63,
            -4,
            124,
            -57,
            3,
            -105,
            70,
            104,
            0,
            0,
            66,
            2,
            63,
            -128,
            -120,
            1,
            63,
            0,
            0,
            0,
            0,
            120,
            125,
            -57,
            3,
            -40,
            65,
            125,
            0,
            0,
            66,
            2,
            63,
            -128,
            -120,
            1,
            63,
            0,
            0,
            0,
            0,
            -2,
            15,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            -128,
            70,
            2,
            63,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            -99,
            4,
            0,
            0,
            8,
            8,
            0,
            0,
            0,
            0,
            0,
            0,
            8,
            8,
            0,
            0,
            -52,
            125,
            -57,
            3,
            51,
            67,
            125,
            0,
            31,
            0,
            -83,
            11,
            -72,
            125,
            -57,
            3,
            -68,
            125,
            -57,
            3,
            24,
            57,
            0,
            63,
            12,
            0,
            0,
            0,
            8,
            14,
            0,
            63,
            8,
            8,
            0,
            0,
            -128,
            70,
            2,
            63,
            118,
            109,
            104,
            98,
            0,
            57,
            0,
            63,
            31,
            0,
            -83,
            11,
            79,
            39,
            1,
            0,
            31,
            0,
            -83,
            11,
            0,
            0,
            0,
            0,
            -128,
            70,
            2
         ],
         queueDepth = &lt;unset&gt;,
         operationalState = (string) [
            "unknown"
         ],
      },
      (vim.host.ScsiDisk) {
         dynamicType = &lt;unset&gt;,
         deviceName = "/vmfs/devices/disks/vmhba1:0:0:0",
         deviceType = "disk",
         key = "key-vim.host.ScsiDisk-vmhba1:0:0",
         uuid = "0000000000856de88242312a41243a14303a4c30",
         canonicalName = "vmhba1:0:0",
         lunType = "disk",
         vendor = "VMware, ",
         model = "VMware Virtual S",
         revision = "1.0 ",
         scsiLevel = 3,
         serialNumber = "unavailable",
         durableName = (vim.host.ScsiLun.DurableName) null,
         standardInquiry = (byte) [
            0,
            0,
            2,
            2,
            31,
            0,
            0,
            115,
            86,
            77,
            119,
            97,
            114,
            101,
            44,
            32,
            86,
            77,
            119,
            97,
            114,
            101,
            32,
            86,
            105,
            114,
            116,
            117,
            97,
            108,
            32,
            83,
            49,
            46,
            48,
            32,
            0,
            57,
            0,
            63,
            -4,
            124,
            -56,
            3,
            -105,
            70,
            104,
            0,
            0,
            66,
            2,
            63,
            -128,
            -120,
            1,
            63,
            0,
            0,
            0,
            0,
            120,
            125,
            -56,
            3,
            -40,
            65,
            125,
            0,
            0,
            66,
            2,
            63,
            -128,
            -120,
            1,
            63,
            0,
            0,
            0,
            0,
            -2,
            15,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            95,
            2,
            63,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            -95,
            4,
            0,
            0,
            8,
            8,
            0,
            0,
            0,
            0,
            0,
            0,
            8,
            8,
            0,
            0,
            -52,
            125,
            -56,
            3,
            51,
            67,
            125,
            0,
            31,
            0,
            -83,
            11,
            -72,
            125,
            -56,
            3,
            -68,
            125,
            -56,
            3,
            24,
            57,
            0,
            63,
            12,
            0,
            0,
            0,
            8,
            14,
            0,
            63,
            8,
            8,
            0,
            0,
            -52,
            125,
            -56,
            3,
            -39,
            -35,
            -120,
            0,
            0,
            57,
            0,
            63,
            31,
            0,
            -83,
            11,
            -27,
            41,
            1,
            0,
            31,
            0,
            -83,
            11,
            0,
            0,
            0,
            0,
            0,
            95,
            2
         ],
         queueDepth = &lt;unset&gt;,
         operationalState = (string) [
            "unknown"
         ],
         capacity = (vim.host.DiskDimensions.Lba) {
            dynamicType = &lt;unset&gt;,
            blockSize = 512,
            block = 16777216,
         },
         devicePath = "/vmfs/devices/disks/vmhba1:0:0:0",
      },
      (vim.host.ScsiDisk) {
         dynamicType = &lt;unset&gt;,
         deviceName = "/vmfs/devices/disks/vml.010000000011223344556677445542",
         deviceType = "disk",
         key = "key-vim.host.ScsiDisk-vmhba32:0:0",
         uuid = "010000000011223344556677445542",
         canonicalName = "vmhba32:0:0",
         lunType = "disk",
         vendor = "IET     ",
         model = "VIRTUAL-DISK    ",
         revision = "0   ",
         scsiLevel = 5,
         serialNumber = "unavailable",
         durableName = (vim.host.ScsiLun.DurableName) {
            dynamicType = &lt;unset&gt;,
            namespace = "SERIALNUM",
            namespaceId = 4,
            data = (byte) [
               32,
               32,
               32,
               32
            ],
         },
         alternateName = (vim.host.ScsiLun.DurableName) [
            (vim.host.ScsiLun.DurableName) {
               dynamicType = &lt;unset&gt;,
               namespace = "SERIALNUM",
               namespaceId = 4,
               data = (byte) [
                  32,
                  32,
                  32,
                  32
               ],
            },
            (vim.host.ScsiLun.DurableName) {
               dynamicType = &lt;unset&gt;,
               namespace = "UNKNOWN",
               namespaceId = 5,
               data = (byte) [
                  1,
                  1,
                  0,
                  24,
                  73,
                  69,
                  84,
                  0,
                  0,
                  0,
                  0,
                  0,
                  0,
                  0,
                  0,
                  0,
                  1,
                  0,
                  0,
                  0,
                  8,
                  8,
                  0,
                  0,
                  13,
                  0,
                  0,
                  0
               ],
            }
         ],
         standardInquiry = (byte) [
            0,
            0,
            4,
            66,
            59,
            0,
            0,
            2,
            73,
            69,
            84,
            32,
            32,
            32,
            32,
            32,
            86,
            73,
            82,
            84,
            85,
            65,
            76,
            45,
            68,
            73,
            83,
            75,
            32,
            32,
            32,
            32,
            48,
            32,
            32,
            32,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            3,
            32,
            9,
            96,
            3,
            0,
            -40,
            65,
            125,
            0,
            0,
            66,
            2,
            63,
            -128,
            -120,
            1,
            63,
            0,
            0,
            0,
            0,
            -2,
            15,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            -128,
            121,
            2,
            63,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            1,
            0,
            0,
            0,
            0,
            0,
            15,
            5,
            0,
            0,
            8,
            8,
            0,
            0,
            8,
            -112,
            2,
            63,
            0,
            57,
            0,
            63,
            -48,
            -3,
            -29,
            3,
            -38,
            66,
            125,
            0,
            8,
            -112,
            2,
            63,
            8,
            8,
            0,
            0,
            -48,
            -3,
            -29,
            3,
            31,
            -71,
            103,
            0,
            0,
            57,
            0,
            63,
            8,
            14,
            0,
            63,
            8,
            8,
            0,
            0,
            -48,
            -3,
            -29,
            3,
            -39,
            -35,
            -120,
            0,
            0,
            57,
            0,
            63,
            0,
            0,
            0,
            0,
            -34,
            -119,
            1,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            -128,
            121,
            2
         ],
         queueDepth = &lt;unset&gt;,
         operationalState = (string) [
            "ok"
         ],
         capacity = (vim.host.DiskDimensions.Lba) {
            dynamicType = &lt;unset&gt;,
            blockSize = 512,
            block = 1249475712,
         },
         devicePath = "/vmfs/devices/disks/vml.010000000011223344556677445542",
      }
   ],
   scsiTopology = (vim.host.ScsiTopology) {
      dynamicType = &lt;unset&gt;,
      adapter = (vim.host.ScsiTopology.Interface) [
         (vim.host.ScsiTopology.Interface) {
            dynamicType = &lt;unset&gt;,
            key = "key-vim.host.ScsiTopology.Interface-vmhba32",
            adapter = &lt;vim.host.InternetScsiHba:key-vim.host.InternetScsiHba-vmhba32&gt;,
            target = (vim.host.ScsiTopology.Target) [
               (vim.host.ScsiTopology.Target) {
                  dynamicType = &lt;unset&gt;,
                  key = "key-vim.host.ScsiTopology.Target-vmhba32:0",
                  target = 0,
                  lun = (vim.host.ScsiTopology.Lun) [
                     (vim.host.ScsiTopology.Lun) {
                        dynamicType = &lt;unset&gt;,
                        key = "010000000011223344556677445542",
                        lun = 0,
                        scsiLun = &lt;vim.host.ScsiDisk:key-vim.host.ScsiDisk-vmhba32:0:0&gt;,
                     }
                  ],
                  transport = (vim.host.InternetScsiTargetTransport) {
                     dynamicType = &lt;unset&gt;,
                     iScsiName = "iqn.2009-01.com.example:storage.disk2.sys1.xyz",
                     iScsiAlias = "",
                     address = (string) [
                        "10.10.0.10:3260"
                     ],
                  },
               }
            ],
         },
         (vim.host.ScsiTopology.Interface) {
            dynamicType = &lt;unset&gt;,
            key = "key-vim.host.ScsiTopology.Interface-vmhba0",
            adapter = &lt;vim.host.BlockHba:key-vim.host.BlockHba-vmhba0&gt;,
            target = (vim.host.ScsiTopology.Target) [
               (vim.host.ScsiTopology.Target) {
                  dynamicType = &lt;unset&gt;,
                  key = "key-vim.host.ScsiTopology.Target-vmhba0:0",
                  target = 0,
                  lun = (vim.host.ScsiTopology.Lun) [
                     (vim.host.ScsiTopology.Lun) {
                        dynamicType = &lt;unset&gt;,
                        key = "000c000000855e393121202b62581a12118b2d21",
                        lun = 0,
                        scsiLun = &lt;vim.host.ScsiLun:key-vim.host.ScsiLun-vmhba0:0:0&gt;,
                     }
                  ],
                  transport = (vim.host.BlockAdapterTargetTransport) {
                     dynamicType = &lt;unset&gt;,
                  },
               }
            ],
         },
         (vim.host.ScsiTopology.Interface) {
            dynamicType = &lt;unset&gt;,
            key = "key-vim.host.ScsiTopology.Interface-vmhba1",
            adapter = &lt;vim.host.ParallelScsiHba:key-vim.host.ParallelScsiHba-vmhba1&gt;,
            target = (vim.host.ScsiTopology.Target) [
               (vim.host.ScsiTopology.Target) {
                  dynamicType = &lt;unset&gt;,
                  key = "key-vim.host.ScsiTopology.Target-vmhba1:0",
                  target = 0,
                  lun = (vim.host.ScsiTopology.Lun) [
                     (vim.host.ScsiTopology.Lun) {
                        dynamicType = &lt;unset&gt;,
                        key = "000c000000855e393121202b62581a12118b2d21",
                        lun = 0,
                        scsiLun = &lt;vim.host.ScsiDisk:key-vim.host.ScsiDisk-vmhba1:0:0&gt;,
                     }
                  ],
                  transport = (vim.host.ParallelScsiTargetTransport) {
                     dynamicType = &lt;unset&gt;,
                  },
               }
            ],
         }
      ],
   },
   multipathInfo = (vim.host.MultipathInfo) {
      dynamicType = &lt;unset&gt;,
      lun = (vim.host.MultipathInfo.LogicalUnit) [
         (vim.host.MultipathInfo.LogicalUnit) {
            dynamicType = &lt;unset&gt;,
            key = "key-vim.host.MultipathInfo.LogicalUnit-vmhba32:0:0",
            id = "vmhba32:0:0",
            lun = &lt;vim.host.ScsiDisk:key-vim.host.ScsiDisk-vmhba32:0:0&gt;,
            path = (vim.host.MultipathInfo.Path) [
               (vim.host.MultipathInfo.Path) {
                  dynamicType = &lt;unset&gt;,
                  key = "key-vim.host.MultipathInfo.Path-vmhba32:0:0",
                  name = "vmhba32:0:0",
                  pathState = "active",
                  adapter = &lt;vim.host.InternetScsiHba:key-vim.host.InternetScsiHba-vmhba32&gt;,
                  lun = &lt;vim.host.MultipathInfo.LogicalUnit:key-vim.host.MultipathInfo.LogicalUnit-vmhba32:0:0&gt;,
                  transport = (vim.host.InternetScsiTargetTransport) {
                     dynamicType = &lt;unset&gt;,
                     iScsiName = "iqn.2009-01.com.example:storage.disk2.sys1.xyz",
                     iScsiAlias = "",
                     address = (string) [
                        "10.10.0.10:3260"
                     ],
                  },
               }
            ],
            policy = (vim.host.MultipathInfo.FixedLogicalUnitPolicy) {
               dynamicType = &lt;unset&gt;,
               policy = "fixed",
               prefer = "vmhba32:0:0",
            },
         },
         (vim.host.MultipathInfo.LogicalUnit) {
            dynamicType = &lt;unset&gt;,
            key = "key-vim.host.MultipathInfo.LogicalUnit-vmhba0:0:0",
            id = "vmhba0:0:0",
            lun = &lt;vim.host.ScsiLun:key-vim.host.ScsiLun-vmhba0:0:0&gt;,
            path = (vim.host.MultipathInfo.Path) [
               (vim.host.MultipathInfo.Path) {
                  dynamicType = &lt;unset&gt;,
                  key = "key-vim.host.MultipathInfo.Path-vmhba0:0:0",
                  name = "vmhba0:0:0",
                  pathState = "active",
                  adapter = &lt;vim.host.BlockHba:key-vim.host.BlockHba-vmhba0&gt;,
                  lun = &lt;vim.host.MultipathInfo.LogicalUnit:key-vim.host.MultipathInfo.LogicalUnit-vmhba0:0:0&gt;,
                  transport = (vim.host.BlockAdapterTargetTransport) {
                     dynamicType = &lt;unset&gt;,
                  },
               }
            ],
            policy = (vim.host.MultipathInfo.FixedLogicalUnitPolicy) {
               dynamicType = &lt;unset&gt;,
               policy = "fixed",
               prefer = "vmhba0:0:0",
            },
         },
         (vim.host.MultipathInfo.LogicalUnit) {
            dynamicType = &lt;unset&gt;,
            key = "key-vim.host.MultipathInfo.LogicalUnit-vmhba1:0:0",
            id = "vmhba1:0:0",
            lun = &lt;vim.host.ScsiDisk:key-vim.host.ScsiDisk-vmhba1:0:0&gt;,
            path = (vim.host.MultipathInfo.Path) [
               (vim.host.MultipathInfo.Path) {
                  dynamicType = &lt;unset&gt;,
                  key = "key-vim.host.MultipathInfo.Path-vmhba1:0:0",
                  name = "vmhba1:0:0",
                  pathState = "active",
                  adapter = &lt;vim.host.ParallelScsiHba:key-vim.host.ParallelScsiHba-vmhba1&gt;,
                  lun = &lt;vim.host.MultipathInfo.LogicalUnit:key-vim.host.MultipathInfo.LogicalUnit-vmhba1:0:0&gt;,
                  transport = (vim.host.ParallelScsiTargetTransport) {
                     dynamicType = &lt;unset&gt;,
                  },
               }
            ],
            policy = (vim.host.MultipathInfo.FixedLogicalUnitPolicy) {
               dynamicType = &lt;unset&gt;,
               policy = "fixed",
               prefer = "vmhba1:0:0",
            },
         }
      ],
   },
   softwareInternetScsiEnabled = true,
 }


[[Category: Vimsh]]</text>
    <sha1>79385017a827e3baa255e88fda9dc6158c982d44</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/net/vnic info</title>
  <ns>0</ns>
  <id>126</id>
  <revision>
    <id>689</id>
    <parentid>275</parentid>
    <timestamp>2009-01-02T23:58:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="815" xml:space="preserve">==== vimsh hostsvc/net/vnic_info ====
Usage: vnic_info [vnic]

Gets information about virtual NICs.

==== example output ==== 
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/net/vnic_info
 (vim.host.VirtualNic) [
   (vim.host.VirtualNic) {
      dynamicType = &lt;unset&gt;,
      device = "vmk0",
      key = "key-vim.host.VirtualNic-vmk0",
      portgroup = "Management Network",
      spec = (vim.host.VirtualNic.Specification) {
         dynamicType = &lt;unset&gt;,
         ip = (vim.host.IpConfig) {
            dynamicType = &lt;unset&gt;,
            dhcp = true,
            ipAddress = "10.10.10.10",
            subnetMask = "255.255.255.0",
         },
         mac = "00:0c:58:1d:ee:18",
      },
      port = &lt;vim.host.PortGroup.Port:key-vim.host.PortGroup.Port-25554131&gt;,
   }
 ]


[[Category: Vimsh]]</text>
    <sha1>5b18c0836c7b9536767938e0b11df2d39c7cbab4</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Vmsvc/getallvms</title>
  <ns>0</ns>
  <id>147</id>
  <revision>
    <id>690</id>
    <parentid>298</parentid>
    <timestamp>2009-01-03T00:02:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="443" xml:space="preserve">==== vimsh vmsvc/getallvms ====
Usage: getallvms

Get the list of virtual machines on the host.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /vmsvc/getallvms
 Vmid    Name               File                 Guest OS       Version   Annotation
 64     bartPE    [store] BartPE/BartPE.vmx     winXPProGuest     vmx-04
 96     trustix   [store] Trustix/Trustix.vmx   otherLinuxGuest   vmx-04

[[Category: Vimsh]]</text>
    <sha1>02b33efe0a5fb69095fe1765e960575a6e4fe688</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/net/provider/</title>
  <ns>0</ns>
  <id>144</id>
  <revision>
    <id>691</id>
    <parentid>294</parentid>
    <timestamp>2009-01-03T00:05:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="129" xml:space="preserve">==== vimsh hostsvc/net/provider/ ====
This plugin only has one option:

 [[hostsvc/net/provider/test_abort]]

[[Category: Vimsh]]</text>
    <sha1>013ebbc559b125f437ec5c42cc60de4797b83d4f</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/net/portgroup set</title>
  <ns>0</ns>
  <id>119</id>
  <revision>
    <id>692</id>
    <parentid>266</parentid>
    <timestamp>2009-01-03T00:07:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>formatted text</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2041" xml:space="preserve">==== vimsh hostsvc/net/portgroup_set ====
Usage: portgroup_set [OPTIONS] vswitch portgroup

Sets the properties on a portgroup.

 Options:
   --securepolicy-promisc=bool
       Allow promiscuous mode.
 
   --securepolicy-macchange=bool
       Allow MAC address to be changed.
 
   --securepolicy-forgedxmit=bool
       Allow forged transmits.
 
   --shapingpolicy-enabled=bool
       Enabled shaper.
 
   --shapingpolicy-average-bandwidth=int
       Average bandwidth.
 
   --shapingpolicy-peak-bandwidth=int
       Peak bandwidth.
 
   --shapingpolicy-burst-size=int
       Burst size.
 
   --nicorderpolicy-active=vmnic_list
       List of active NICs.
 
   --nicorderpolicy-standby=vmnic_list
       Order in which failover should occur.
 
   --failurecriteria-check-speed=failurecriteria-check-speed
       Detecting failover using link speed check
 
   --failurecriteria-speed=int
       The speed for link speed check method
 
   --failurecriteria-check-duplex=bool
       Detecting failover using link duplex check
 
   --failurecriteria-duplex=bool
       The duplexity for link duplex check method
 
   --failurecriteria-check-error=bool
       Detecting failover using link error percentage
 
   --failurecriteria-error=int
       The error percentage for link error percentage check method
 
   --failurecriteria-check-beacon=bool
       Detecting failover using the beacon
 
   --nicteaming-policy=nicteaming-policy
       Nic-Teaming policy.
 
   --nicteaming-reverse-policy=bool
       Apply the teaming policy to inbound frames as well.
 
   --nicteaming-notify-switch=bool
       Notify switches when detects a link failure.
 
   --nicteaming-rollingorder=bool
       Whether or not to use rolling failover.
 
   --offloadcaps-csum-offload=bool
       Checksum offload
 
   --offloadcaps-tcp-segment=bool
       TCP segment offload
 
   --offloadcaps-zerocopy-xmit=bool
       Scatter gather
 
   --portgroup-vlanid=int
       VLAN identifier.
 
   --portgroup-name=string
       New portgroup identifier.
[[Category: Vimsh]]</text>
    <sha1>0c9257379b18ec6a605a96280017af378a537ab5</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/querydisabledmethods</title>
  <ns>0</ns>
  <id>89</id>
  <revision>
    <id>693</id>
    <parentid>235</parentid>
    <timestamp>2009-01-03T00:09:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="463" xml:space="preserve">==== Vimsh hostsvc/querydisabledmethods====
Usage: querydisabled

Query for disabled methods on the host.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/querydisabledmethods
 Disabled methods:
 
 (vmodl.MethodName) [
    "vim.HostSystem.disconnect",
    "vim.HostSystem.reconnect",
    "vim.HostSystem.reconfigureDAS",
    "vim.HostSystem.exitStandbyMode",
    "vim.HostSystem.exitMaintenanceMode"
 ]


[[Category: Vimsh]]</text>
    <sha1>71aea774b2ab607586eb5b437cba7054bd1fd5cd</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/queryconnectioninfo</title>
  <ns>0</ns>
  <id>88</id>
  <revision>
    <id>694</id>
    <parentid>234</parentid>
    <timestamp>2009-01-03T00:11:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="345" xml:space="preserve">==== Vimsh hostsvc/queryconnectioninfo====
Usage: queryconn

Query for connection information from the host.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/queryconnectioninfo
 (vim.fault.RestrictedVersion) {
    dynamicType = &lt;unset&gt;,
    msg = "fault.RestrictedVersion.summary"
 }


[[Category: Vimsh]]</text>
    <sha1>57dde34a81b836fece3098b9b0d01e8244504cc0</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/autostartmanager/autostart</title>
  <ns>0</ns>
  <id>294</id>
  <revision>
    <id>695</id>
    <parentid>565</parentid>
    <timestamp>2009-01-03T11:15:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="394" xml:space="preserve">==== vimsh hostsvc/autostartmanager/autostart ====

Usage: autostart

Starts up VMs in the AutoStart sequence

==== example output ====
Example output when no autostart is set:
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/autostartmanager/autostart
 (vim.fault.RestrictedVersion) {
    dynamicType = &lt;unset&gt;,
    msg = "fault.RestrictedVersion.summary"
 }


[[Category: Vimsh]]</text>
    <sha1>2e2d6e600ac37eee874b741e1db450174f09f102</sha1>
  </revision>
  <revision>
    <id>698</id>
    <parentid>695</parentid>
    <timestamp>2009-01-03T11:35:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="429" xml:space="preserve">==== vimsh hostsvc/autostartmanager/autostart ====

Usage: autostart

Starts up VMs in the AutoStart sequence

==== example output ====
Example output on the restricted version of ES3.5iU3 (not allowed output) :
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/autostartmanager/autostart
 (vim.fault.RestrictedVersion) {
    dynamicType = &lt;unset&gt;,
    msg = "fault.RestrictedVersion.summary"
 }


[[Category: Vimsh]]</text>
    <sha1>d3615217cb426fd931e325dceccb98e1c338bc21</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/autostartmanager/get autostartseq</title>
  <ns>0</ns>
  <id>297</id>
  <revision>
    <id>696</id>
    <parentid>568</parentid>
    <timestamp>2009-01-03T11:30:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="653" xml:space="preserve">==== vimsh hostsvc/autostartmanager/get_autostartseq ====
Usage: Get the current VM Autostart sequence.

==== example output ====
Example output with one virtual machine set to autostart
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/autostartmanager/get_autostart
 (vim.host.AutoStartManager.AutoPowerInfo) [
    (vim.host.AutoStartManager.AutoPowerInfo) {
       dynamicType = &lt;unset&gt;,
       key = 'vim.VirtualMachine:96',
       startOrder = 1,
       startDelay = -1,
       waitForHeartbeat = "systemDefault",
       startAction = "PowerOn",
       stopDelay = -1,
       stopAction = "SystemDefault",
    }
 ]


[[Category: Vimsh]]</text>
    <sha1>f50915e7c114f8beaf332089ead1a8c41c4bf4b9</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/autostartmanager/get defaults</title>
  <ns>0</ns>
  <id>298</id>
  <revision>
    <id>697</id>
    <parentid>569</parentid>
    <timestamp>2009-01-03T11:33:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="837" xml:space="preserve">==== hostsvc/autostartmanager/get_defaults ====
Usage: Get the AutoStart system defaults.
==== example output ====
Default output on a ESX3.5i  machine when autostart is disabled:
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/autostartmanager/get_defaults
 (vim.host.AutoStartManager.SystemDefaults) {
    dynamicType = &lt;unset&gt;,
    enabled = false,
    startDelay = 120,
    stopDelay = 120,
    waitForHeartbeat = false,
    stopAction = "PowerOff",
 }
The output after enabling the autostart functionality:
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/autostartmanager/get_defaults
 (vim.host.AutoStartManager.SystemDefaults) {
    dynamicType = &lt;unset&gt;,
    enabled = true,
    startDelay = 120,
    stopDelay = 120,
    waitForHeartbeat = false,
    stopAction = "PowerOff",
 }


[[Category: Vimsh]]</text>
    <sha1>f04338787546d326d0a475b590e3ab5dd5cdc41b</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/autostartmanager/enable autostart</title>
  <ns>0</ns>
  <id>296</id>
  <revision>
    <id>699</id>
    <parentid>567</parentid>
    <timestamp>2009-01-03T11:41:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="389" xml:space="preserve">==== vimsh hostsvc/autostartmanager/enable_autostart ====
Usage: enable_autostart EnableAutoStart

Enable or disable AutoStart.

==== example output ====
Here's some output from a ESX3.5 host from within the vimsh shell:
 [/]$ hostsvc/autostartmanager/enable_autostart true
 Enabled AutoStart
 [/]$ hostsvc/autostartmanager/enable_autostart false 
 Disabled AutoStart


[[Category: Vimsh]]</text>
    <sha1>837db6f602043c662a066f7151fa20cc5ccc42ae</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Vmsvc/get.filelayout</title>
  <ns>0</ns>
  <id>173</id>
  <revision>
    <id>700</id>
    <parentid>329</parentid>
    <timestamp>2009-01-04T12:19:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1040" xml:space="preserve">==== vimsh vmsvc/get.filelayout ====
Usage: get.filelayout vmid

Show the list of files for this virtual machine.

See also [[vmsvc/getallvms]] to get a lits of all VMs
==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /vmsvc/get.filelayout 96
 (vim.vm.FileInfo) {
    dynamicType = &lt;unset&gt;,
    vmPathName = "[store] Trustix/Trustix.vmx",
    snapshotDirectory = "[store] Trustix",
    suspendDirectory = "[store] Trustix",
    logDirectory = "[store] Trustix",
 }
 (vim.vm.FileLayout) {
    dynamicType = &lt;unset&gt;,
    configFile = (string) [
       "Trustix.vmsd",
       "Trustix.vmxf",
       "Trustix.nvram"
    ],
    logFile = (string) [
       "vmware-1.log",
       "vmware-2.log",
       "vmware.log"
    ],
    disk = (vim.vm.FileLayout.DiskLayout) [
       (vim.vm.FileLayout.DiskLayout) {
          dynamicType = &lt;unset&gt;,
          key = 2000,
          diskFile = (string) [
             "[store] Trustix/Trustix.vmdk"
           ],
       }
    ],
    swapFile = &lt;unset&gt;,
  }


[[Category: Vimsh]]</text>
    <sha1>b48a286640d883cbd091e8a8f66169bb2b7f94d7</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Hostsvc/net/dns info</title>
  <ns>0</ns>
  <id>110</id>
  <revision>
    <id>701</id>
    <parentid>257</parentid>
    <timestamp>2009-01-04T12:27:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="510" xml:space="preserve">==== vimsh hostsvc/net/dns_info ====
Usage: dns_info

Get the DNS configuration.
==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/net/dns_info
 (vim.host.DnsConfig) {
    dynamicType = &lt;unset&gt;,
    dhcp = true,
    virtualNicDevice = "Management Network",
    hostName = "localhost",
    domainName = "example.com",
    address = (string) [
       "10.10.10.1",
       "10.10.10.177"
    ],
    searchDomain = (string) [
       "example.com"
    ],
 }

[[Category: Vimsh]]</text>
    <sha1>e88e2f98c8557f3fcd4fffe3517400e325be6954</sha1>
  </revision>
</page>
<page arvcontinue="20090102055011|653">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>702</id>
    <parentid>437</parentid>
    <timestamp>2009-01-04T13:18:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Updated with status on the vimsh documentation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1552" xml:space="preserve">== VI Toolkit ==
'' December 11, 2008 ''
==== Welcome ====
Welcome at our new site which will contain information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since Januari 3rd, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

==== Contribute / help out ====
This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you.

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>4a4ece7e8bdcc241ac6532d36c4a464ee3db79d7</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>703</id>
    <parentid>542</parentid>
    <timestamp>2009-01-04T14:28:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>update what's done</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1577" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages. Partly done
* Add "what's new" to the main page
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* Do email notifications work? (I think not)

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?

[[Category: website]]</text>
    <sha1>c5ac4a5626909d00005154a749889f84847e5136</sha1>
  </revision>
  <revision>
    <id>704</id>
    <parentid>703</parentid>
    <timestamp>2009-01-05T01:46:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>fixed email notifications</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1584" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages. Partly done
* Add "what's new" to the main page
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* Find a better way to present what's available on the site, improve ways to restructure the data
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?

[[Category: website]]</text>
    <sha1>e4629bb1b6c2b39fab22111527528db2eb48b5f8</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/net/portgroup add</title>
  <ns>0</ns>
  <id>117</id>
  <revision>
    <id>705</id>
    <parentid>264</parentid>
    <timestamp>2009-01-05T01:48:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>formatted text</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1936" xml:space="preserve">==== vimsh hostsvc/net/portgroup_add ====
Usage: portgroup_add [OPTIONS] vswitch portgroup [vlan]

Adds a portgroup to a virtual switch.

 Options:
   --securepolicy-promisc=bool
       Allow promiscuous mode.
 
   --securepolicy-macchange=bool
       Allow MAC address to be changed.
 
   --securepolicy-forgedxmit=bool
       Allow forged transmits.
 
   --shapingpolicy-enabled=bool
       Enabled shaper.
 
   --shapingpolicy-average-bandwidth=int
       Average bandwidth.
 
   --shapingpolicy-peak-bandwidth=int
       Peak bandwidth.
 
   --shapingpolicy-burst-size=int
       Burst size.
 
   --nicorderpolicy-active=vmnic_list
       List of active NICs.
 
   --nicorderpolicy-standby=vmnic_list
       Order in which failover should occur.
 
   --failurecriteria-check-speed=failurecriteria-check-speed
       Detecting failover using link speed check
 
   --failurecriteria-speed=int
       The speed for link speed check method
 
   --failurecriteria-check-duplex=bool
       Detecting failover using link duplex check
 
   --failurecriteria-duplex=bool
       The duplexity for link duplex check method
 
   --failurecriteria-check-error=bool
       Detecting failover using link error percentage
 
   --failurecriteria-error=int
       The error percentage for link error percentage check method
 
   --failurecriteria-check-beacon=bool
       Detecting failover using the beacon
 
   --nicteaming-policy=nicteaming-policy
       Nic-Teaming policy.
 
   --nicteaming-reverse-policy=bool
       Apply the teaming policy to inbound frames as well.
 
   --nicteaming-notify-switch=bool
       Notify switches when detects a link failure.
 
   --nicteaming-rollingorder=bool
       Whether or not to use rolling failover.
 
   --offloadcaps-csum-offload=bool
       Checksum offload
 
   --offloadcaps-tcp-segment=bool
       TCP segment offload
 
   --offloadcaps-zerocopy-xmit=bool
       Scatter gather
[[Category: Vimsh]]</text>
    <sha1>06e57b9c4274664f4da760bf9213dc73e5ccb7ea</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/datastore/listsummary</title>
  <ns>0</ns>
  <id>305</id>
  <revision>
    <id>706</id>
    <parentid>577</parentid>
    <timestamp>2009-01-05T01:55:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1013" xml:space="preserve">==== vimsh hostsvc/datastore/listsummary ====
Usage: List a summary of all datastores available.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/datastore/listsummary
 (vim.Datastore.Summary) [
    (vim.Datastore.Summary) {
       dynamicType = &lt;unset&gt;,
       datastore = 'vim.Datastore:24b85cd6-123d5101-7b21-0016c8c08128',
       name = "store",
       url = "/vmfs/volumes/24b85cd6-123d5101-7b21-0016c8c08128",
       capacity = 639681691648,
       freeSpace = 62658707456,
       accessible = true,
       multipleHostAccess = &lt;unset&gt;,
       type = "VMFS",
    },
    (vim.Datastore.Summary) {
       dynamicType = &lt;unset&gt;,
        datastore = 'vim.Datastore:271a2c8b-1f21810d-c28d-000d172bcef8',
       name = "datastore2",
       url = "/vmfs/volumes/271a2c8b-1f21810d-c28d-000d172bcef8",
       capacity = 3489660928,
       freeSpace = 3178233856,
       accessible = true,
       multipleHostAccess = &lt;unset&gt;,
       type = "VMFS",
    }
 ]

[[Category: Vimsh]]</text>
    <sha1>674209f24a19cb572ff9a177e3f375e87f201271</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/datastore/info</title>
  <ns>0</ns>
  <id>304</id>
  <revision>
    <id>707</id>
    <parentid>575</parentid>
    <timestamp>2009-01-05T01:58:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1346" xml:space="preserve">==== hostsvc/datastore/info ====
Usage: info name

Retrieve the information of a datastore by name.

==== example output ==== 
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/datastore/info store
 (vim.host.VmfsDatastoreInfo) {
    dynamicType = &lt;unset&gt;,
    name = "store",
    url = "/vmfs/volumes/24b85cd6-123d5101-7b21-0016c8c08128",
    freeSpace = 62658707456,
    maxFileSize = 549755813888,
    vmfs = (vim.host.VmfsVolume) {
       dynamicType = &lt;unset&gt;,
       type = "VMFS",
       name = "isc",
       capacity = 639681691648,
       blockSizeMb = 2,
       maxBlocks = 262144,
       majorVersion = 3,
       version = "3.21",
       uuid = "24b85cd6-123d5101-7b21-0016c8c08128",
       extent = (vim.host.ScsiDisk.Partition) [
          (vim.host.ScsiDisk.Partition) {
             dynamicType = &lt;unset&gt;,
             diskName = "vmhba32:0:0",
             partition = 1,
          }
       ],
       vmfsUpgradable = false,
    },
 }
 (vim.Datastore.HostMount) [
    (vim.Datastore.HostMount) {
       dynamicType = &lt;unset&gt;,
       key = 'vim.HostSystem:ha-host',
       mountInfo = (vim.host.MountInfo) {
          dynamicType = &lt;unset&gt;,
          path = "/vmfs/volumes/24b85cd6-123d5101-7b21-0016c8c08128",
          accessMode = "readWrite",
          accessible = &lt;unset&gt;,
       },
    }
 ]


[[Category: Vimsh]]</text>
    <sha1>d1d16b52e56d0fb0c699a8d56b215a55f0e43de7</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/datastore/capabilities</title>
  <ns>0</ns>
  <id>302</id>
  <revision>
    <id>708</id>
    <parentid>573</parentid>
    <timestamp>2009-01-05T02:00:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="422" xml:space="preserve">==== hostsvc/datastore/capabilities ====
Usage: List the capabilities supported by the datastore system.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/datastore/capabilities
 (vim.host.DatastoreSystem.Capabilities) {
    dynamicType = &lt;unset&gt;,
    nfsMountCreationRequired = true,
    nfsMountCreationSupported = true,
    localDatastoreSupported = false,
 }


[[category: Vimsh]]</text>
    <sha1>583411c70c5d3b20cf1aa5b54677af8f1ee131c9</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/storage/multipath info</title>
  <ns>0</ns>
  <id>353</id>
  <revision>
    <id>709</id>
    <parentid>632</parentid>
    <timestamp>2009-01-05T02:06:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3798" xml:space="preserve">==== vimsh hostsvc/storage/multipath_info ====
Usage: multipath_info

Get storage multipath information.

==== example output ==== 
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/storage/multipath_info
 (vim.host.MultipathInfo) {
    dynamicType = &lt;unset&gt;,
    lun = (vim.host.MultipathInfo.LogicalUnit) [
       (vim.host.MultipathInfo.LogicalUnit) {
          dynamicType = &lt;unset&gt;,
          key = "key-vim.host.MultipathInfo.LogicalUnit-vmhba32:0:0",
          id = "vmhba32:0:0",
          lun = &lt;vim.host.ScsiDisk:key-vim.host.ScsiDisk-vmhba32:0:0&gt;,
          path = (vim.host.MultipathInfo.Path) [
             (vim.host.MultipathInfo.Path) {
                dynamicType = &lt;unset&gt;,
                key = "key-vim.host.MultipathInfo.Path-vmhba32:0:0",
                 name = "vmhba32:0:0",
                pathState = "active",
                adapter = &lt;vim.host.InternetScsiHba:key-vim.host.InternetScsiHba-vmhba32&gt;,
                lun = &lt;vim.host.MultipathInfo.LogicalUnit:key-vim.host.MultipathInfo.LogicalUnit-vmhba32:0:0&gt;,
                transport = (vim.host.InternetScsiTargetTransport) {
                   dynamicType = &lt;unset&gt;,
                    iScsiName = "iqn.2009-01.com.example:storage.disk2.sys1.xyz",
                   iScsiAlias = "",
                   address = (string) [
                       "10.10.0.10:3260"
                   ],
                },
             }
          ],
          policy = (vim.host.MultipathInfo.FixedLogicalUnitPolicy) {
              dynamicType = &lt;unset&gt;,
             policy = "fixed",
             prefer = "vmhba32:0:0",
          },
       },
       (vim.host.MultipathInfo.LogicalUnit) {
          dynamicType = &lt;unset&gt;,
          key = "key-vim.host.MultipathInfo.LogicalUnit-vmhba0:0:0",
          id = "vmhba0:0:0",
          lun = &lt;vim.host.ScsiLun:key-vim.host.ScsiLun-vmhba0:0:0&gt;,
          path = (vim.host.MultipathInfo.Path) [
             (vim.host.MultipathInfo.Path) {
                dynamicType = &lt;unset&gt;,
                key = "key-vim.host.MultipathInfo.Path-vmhba0:0:0",
                name = "vmhba0:0:0",
                pathState = "active",
                adapter = &lt;vim.host.BlockHba:key-vim.host.BlockHba-vmhba0&gt;,
                 lun = &lt;vim.host.MultipathInfo.LogicalUnit:key-vim.host.MultipathInfo.LogicalUnit-vmhba0:0:0&gt;,
                transport = (vim.host.BlockAdapterTargetTransport) {
                   dynamicType = &lt;unset&gt;,
                },
             }
          ],
           policy = (vim.host.MultipathInfo.FixedLogicalUnitPolicy) {
             dynamicType = &lt;unset&gt;,
             policy = "fixed",
             prefer = "vmhba0:0:0",
          },
       },
       (vim.host.MultipathInfo.LogicalUnit) {
          dynamicType = &lt;unset&gt;,
          key = "key-vim.host.MultipathInfo.LogicalUnit-vmhba1:0:0",
          id = "vmhba1:0:0",
          lun = &lt;vim.host.ScsiDisk:key-vim.host.ScsiDisk-vmhba1:0:0&gt;,
          path = (vim.host.MultipathInfo.Path) [
             (vim.host.MultipathInfo.Path) {
                 dynamicType = &lt;unset&gt;,
                key = "key-vim.host.MultipathInfo.Path-vmhba1:0:0",
                name = "vmhba1:0:0",
                pathState = "active",
                adapter = &lt;vim.host.ParallelScsiHba:key-vim.host.ParallelScsiHba-vmhba1&gt;,
                lun = &lt;vim.host.MultipathInfo.LogicalUnit:key-vim.host.MultipathInfo.LogicalUnit-vmhba1:0:0&gt;,
                transport = (vim.host.ParallelScsiTargetTransport) {
                    dynamicType = &lt;unset&gt;,
                },
             }
          ],
          policy = (vim.host.MultipathInfo.FixedLogicalUnitPolicy) {
             dynamicType = &lt;unset&gt;,
             policy = "fixed",
             prefer = "vmhba1:0:0",
          },
       }
    ],
 }


[[Category: Vimsh]]</text>
    <sha1>97b98ce502ad5b1b07a75ddf9483064bd1477936</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/vmotion/vnic set</title>
  <ns>0</ns>
  <id>400</id>
  <revision>
    <id>710</id>
    <parentid>686</parentid>
    <timestamp>2009-01-05T12:30:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="569" xml:space="preserve">==== vimsh hostsvc/vmotion/vnic_set ====
Usage: vnic_set vnic

Select a VirtualNic to be used as the VMotion NIC.

==== example ====

Taken from http://www.yellow-bricks.com/2008/12/08/enable-vmotion-from-the-command-line/

As of ESX 3.5 the way to enable VMotion via the command-line changed. 

So for anyone looking for this particular command:

 /usr/bin/vmware-vim-cmd "hostsvc/vmotion/vnic_set vmk0"

In this example “vmk0″ is the first vmkernel nic. This is one of the things that changed, so no portgroup id’s anymore. 

thanks Duncan!

[[Category: vimsh]]</text>
    <sha1>e2e80df03b386e243718b2bc72beb49e3ddd3a96</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/net/config</title>
  <ns>0</ns>
  <id>99</id>
  <revision>
    <id>711</id>
    <parentid>246</parentid>
    <timestamp>2009-01-05T15:24:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example output</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8673" xml:space="preserve">==== vimsh hostsvc/net/config ====
Usage: config

Get the network configuration.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /hostsvc/net/config
 (vim.host.NetworkConfig) {
   dynamicType = &lt;unset&gt;,
   vswitch = (vim.host.VirtualSwitch.Config) [
      (vim.host.VirtualSwitch.Config) {
         dynamicType = &lt;unset&gt;,
         changeOperation = &lt;unset&gt;,
         name = "vSwitch0",
         spec = (vim.host.VirtualSwitch.Specification) {
            dynamicType = &lt;unset&gt;,
            numPorts = 64,
            bridge = (vim.host.VirtualSwitch.BondBridge) {
               dynamicType = &lt;unset&gt;,
               nicDevice = (string) [
                  "vmnic0"
               ],
               beacon = (vim.host.VirtualSwitch.BeaconConfig) {
                  dynamicType = &lt;unset&gt;,
                  interval = 1,
               },
            },
            policy = (vim.host.NetworkPolicy) {
               dynamicType = &lt;unset&gt;,
               security = (vim.host.NetworkPolicy.SecurityPolicy) {
                  dynamicType = &lt;unset&gt;,
                  allowPromiscuous = false,
                  macChanges = true,
                  forgedTransmits = true,
               },
               nicTeaming = (vim.host.NetworkPolicy.NicTeamingPolicy) {
                  dynamicType = &lt;unset&gt;,
                  policy = "loadbalance_srcid",
                  reversePolicy = true,
                  notifySwitches = true,
                  rollingOrder = false,
                  failureCriteria = (vim.host.NetworkPolicy.NicFailureCriteria) {
                     dynamicType = &lt;unset&gt;,
                     checkSpeed = "minimum",
                     speed = 10,
                     checkDuplex = false,
                     fullDuplex = false,
                     checkErrorPercent = false,
                     percentage = 0,
                     checkBeacon = false,
                  },
                  nicOrder = (vim.host.NetworkPolicy.NicOrderPolicy) {
                     dynamicType = &lt;unset&gt;,
                     activeNic = (string) [
                        "vmnic0"
                     ],
                  },
               },
               offloadPolicy = (vim.host.NetOffloadCapabilities) {
                  dynamicType = &lt;unset&gt;,
                  csumOffload = true,
                  tcpSegmentation = true,
                  zeroCopyXmit = true,
               },
               shapingPolicy = (vim.host.NetworkPolicy.TrafficShapingPolicy) {
                  dynamicType = &lt;unset&gt;,
                  enabled = false,
                  averageBandwidth = &lt;unset&gt;,
                  peakBandwidth = &lt;unset&gt;,
                  burstSize = &lt;unset&gt;,
               },
            },
            mtu = &lt;unset&gt;,
         },
      }
   ],
   portgroup = (vim.host.PortGroup.Config) [
      (vim.host.PortGroup.Config) {
         dynamicType = &lt;unset&gt;,
         changeOperation = &lt;unset&gt;,
         spec = (vim.host.PortGroup.Specification) {
            dynamicType = &lt;unset&gt;,
            name = "VM Network",
            vlanId = 0,
            vswitchName = "vSwitch0",
            policy = (vim.host.NetworkPolicy) {
               dynamicType = &lt;unset&gt;,
               security = (vim.host.NetworkPolicy.SecurityPolicy) {
                  dynamicType = &lt;unset&gt;,
                  allowPromiscuous = &lt;unset&gt;,
                  macChanges = &lt;unset&gt;,
                  forgedTransmits = &lt;unset&gt;,
               },
               nicTeaming = (vim.host.NetworkPolicy.NicTeamingPolicy) {
                  dynamicType = &lt;unset&gt;,
                  policy = &lt;unset&gt;,
                  reversePolicy = &lt;unset&gt;,
                  notifySwitches = &lt;unset&gt;,
                  rollingOrder = &lt;unset&gt;,
                  failureCriteria = (vim.host.NetworkPolicy.NicFailureCriteria) {
                     dynamicType = &lt;unset&gt;,
                     checkSpeed = &lt;unset&gt;,
                     speed = &lt;unset&gt;,
                     checkDuplex = &lt;unset&gt;,
                     fullDuplex = &lt;unset&gt;,
                     checkErrorPercent = &lt;unset&gt;,
                     percentage = &lt;unset&gt;,
                     checkBeacon = &lt;unset&gt;,
                  },
                  nicOrder = (vim.host.NetworkPolicy.NicOrderPolicy) null,
               },
               offloadPolicy = (vim.host.NetOffloadCapabilities) {
                  dynamicType = &lt;unset&gt;,
                  csumOffload = &lt;unset&gt;,
                  tcpSegmentation = &lt;unset&gt;,
                  zeroCopyXmit = &lt;unset&gt;,
               },
               shapingPolicy = (vim.host.NetworkPolicy.TrafficShapingPolicy) {
                  dynamicType = &lt;unset&gt;,
                  enabled = &lt;unset&gt;,
                  averageBandwidth = &lt;unset&gt;,
                  peakBandwidth = &lt;unset&gt;,
                  burstSize = &lt;unset&gt;,
               },
            },
         },
      },
      (vim.host.PortGroup.Config) {
         dynamicType = &lt;unset&gt;,
         changeOperation = &lt;unset&gt;,
         spec = (vim.host.PortGroup.Specification) {
            dynamicType = &lt;unset&gt;,
            name = "Management Network",
            vlanId = 0,
            vswitchName = "vSwitch0",
            policy = (vim.host.NetworkPolicy) {
               dynamicType = &lt;unset&gt;,
               security = (vim.host.NetworkPolicy.SecurityPolicy) {
                  dynamicType = &lt;unset&gt;,
                  allowPromiscuous = &lt;unset&gt;,
                  macChanges = &lt;unset&gt;,
                  forgedTransmits = &lt;unset&gt;,
               },
               nicTeaming = (vim.host.NetworkPolicy.NicTeamingPolicy) {
                  dynamicType = &lt;unset&gt;,
                  policy = "loadbalance_srcid",
                  reversePolicy = true,
                  notifySwitches = true,
                  rollingOrder = false,
                  failureCriteria = (vim.host.NetworkPolicy.NicFailureCriteria) {
                     dynamicType = &lt;unset&gt;,
                     checkSpeed = "minimum",
                     speed = 10,
                     checkDuplex = false,
                     fullDuplex = false,
                     checkErrorPercent = false,
                     percentage = 0,
                     checkBeacon = false,
                  },
                  nicOrder = (vim.host.NetworkPolicy.NicOrderPolicy) {
                     dynamicType = &lt;unset&gt;,
                     activeNic = (string) [
                        "vmnic0"
                     ],
                  },
               },
               offloadPolicy = (vim.host.NetOffloadCapabilities) {
                  dynamicType = &lt;unset&gt;,
                  csumOffload = &lt;unset&gt;,
                  tcpSegmentation = &lt;unset&gt;,
                  zeroCopyXmit = &lt;unset&gt;,
               },
               shapingPolicy = (vim.host.NetworkPolicy.TrafficShapingPolicy) {
                  dynamicType = &lt;unset&gt;,
                  enabled = &lt;unset&gt;,
                  averageBandwidth = &lt;unset&gt;,
                  peakBandwidth = &lt;unset&gt;,
                  burstSize = &lt;unset&gt;,
               },
            },
         },
      }
   ],
   pnic = (vim.host.PhysicalNic.Config) [
      (vim.host.PhysicalNic.Config) {
         dynamicType = &lt;unset&gt;,
         device = "vmnic0",
         spec = (vim.host.PhysicalNic.Specification) {
            dynamicType = &lt;unset&gt;,
            ip = (vim.host.IpConfig) {
               dynamicType = &lt;unset&gt;,
               dhcp = false,
               ipAddress = "",
               subnetMask = "",
            },
            linkSpeed = (vim.host.PhysicalNic.LinkSpeedDuplex) null,
         },
      }
   ],
   vnic = (vim.host.VirtualNic.Config) [
      (vim.host.VirtualNic.Config) {
         dynamicType = &lt;unset&gt;,
         changeOperation = &lt;unset&gt;,
         device = "vmk0",
         portgroup = "Management Network",
         spec = (vim.host.VirtualNic.Specification) {
            dynamicType = &lt;unset&gt;,
            ip = (vim.host.IpConfig) {
               dynamicType = &lt;unset&gt;,
               dhcp = true,
               ipAddress = "10.10.10.10",
               subnetMask = "255.255.255.0",
            },
            mac = "00:0c:58:1d:ee:18",
         },
      }
   ],
   dnsConfig = (vim.host.DnsConfig) {
      dynamicType = &lt;unset&gt;,
      dhcp = true,
      virtualNicDevice = "Management Network",
      hostName = "localhost",
      domainName = "example.com",
      address = (string) [
         "10.10.10.1",
         "10.10.0.177"
      ],
      searchDomain = (string) [
         "example.com"
      ],
   },
   ipRouteConfig = (vim.host.IpRouteConfig) null,
   consoleIpRouteConfig = (vim.host.IpRouteConfig) null,
 }

[[Category: Vimsh]]</text>
    <sha1>9763754276f4d219c64dbe82c83ca165047d3535</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/datastore/nas create</title>
  <ns>0</ns>
  <id>308</id>
  <revision>
    <id>712</id>
    <parentid>580</parentid>
    <timestamp>2009-01-05T20:18:15Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="655" xml:space="preserve">==== vimsh hostsvc/datastore/nas_create ====
Usage: nas_create name remoteHost remotePath readonly

Add a NAS datastore.
readonly is a boolean value, 0 for readonly and 1 for rw access.

==== Example ====

NFS SERVER IP: 172.30.0.254&lt;br&gt;
NFS EXPORTED PATH: /nfs/mount/path&lt;br&gt;
RW: 1&lt;br&gt;
DATASTORE NAME : MY_NFS_DATASTORE&lt;br&gt;

ESX 3.5+
  vmware-vim-cmd hostsvc/datastore/nas_create MY_NFS_DATASTORE 172.30.0.254 /nfs/mount/point 1

ESXi 3.5+
  vim-cmd hostsvc/datastore/nas_create MY_NFS_DATASTORE 172.30.0.254 /nfs/mount/point 1

ESX 3.0.x+
  vimsh -n -e "hostsvc/datastore/nas_create MY_NFS_DATASTORE 172.30.0.254 /nfs/mount/point 1"

[[Category: Vimsh]]</text>
    <sha1>8b4e6938cb81364966dd67fc7b3aacf3ee9752ae</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>713</id>
    <parentid>118</parentid>
    <timestamp>2009-01-05T20:40:03Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1114" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x]]

[[Linked Clones for ESXi]]

[[Customer my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]</text>
    <sha1>f66b5cf538e73213fd45323ebf4f9cc398c22888</sha1>
  </revision>
  <revision>
    <id>714</id>
    <parentid>713</parentid>
    <timestamp>2009-01-05T20:40:14Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1112" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]</text>
    <sha1>6ed8b9fe288547269344b8b9f9b5e79651ac3d1d</sha1>
  </revision>
  <revision>
    <id>727</id>
    <parentid>714</parentid>
    <timestamp>2009-01-05T21:01:23Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1113" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]</text>
    <sha1>b686a42ed14157ad79d2b069e2469623d698b419</sha1>
  </revision>
  <revision>
    <id>728</id>
    <parentid>727</parentid>
    <timestamp>2009-01-05T21:02:12Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1112" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]</text>
    <sha1>6ed8b9fe288547269344b8b9f9b5e79651ac3d1d</sha1>
  </revision>
  <revision>
    <id>731</id>
    <parentid>728</parentid>
    <timestamp>2009-01-05T21:03:08Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1113" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]</text>
    <sha1>b686a42ed14157ad79d2b069e2469623d698b419</sha1>
  </revision>
  <revision>
    <id>732</id>
    <parentid>731</parentid>
    <timestamp>2009-01-05T21:03:35Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1112" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]</text>
    <sha1>6ed8b9fe288547269344b8b9f9b5e79651ac3d1d</sha1>
  </revision>
  <revision>
    <id>733</id>
    <parentid>732</parentid>
    <timestamp>2009-01-05T21:03:55Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1113" xml:space="preserve">==== documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[ESX3i Remote CLI documentation]]

===== vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]</text>
    <sha1>b686a42ed14157ad79d2b069e2469623d698b419</sha1>
  </revision>
  <revision>
    <id>743</id>
    <parentid>733</parentid>
    <timestamp>2009-01-05T22:40:37Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1222" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== RCLI =====

[[ESX3i Remote CLI documentation]]

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI scripts ====

COMING SOON</text>
    <sha1>165f2c0ac65085a82281adef8abb4af683694887</sha1>
  </revision>
  <revision>
    <id>744</id>
    <parentid>743</parentid>
    <timestamp>2009-01-05T22:52:14Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1981" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== RCLI =====

What is VMware RCLI?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0


What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? [http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun API guide] but see also the [[VIX]] page for more details.


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI scripts ====

COMING SOON</text>
    <sha1>16d36840443e40ec52be7d9ed8f5409d0d25968a</sha1>
  </revision>
  <revision>
    <id>750</id>
    <parentid>744</parentid>
    <timestamp>2009-01-05T23:05:07Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2018" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== RCLI =====

What is VMware RCLI?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI scripts ====

COMING SOON</text>
    <sha1>e57cd0db45cb0fa7a700f06cbc900a0b3d60a390</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Linked Clones for ESX 3.+</title>
  <ns>0</ns>
  <id>402</id>
  <revision>
    <id>715</id>
    <timestamp>2009-01-05T20:43:18Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Compatiable with''': ESX 3.x+  Please find more details located at: http://communities.vmware.com/docs/DOC-9020  This script allows users to create linked cloned virtual machine(s) from...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1759" xml:space="preserve">'''Compatiable with''': ESX 3.x+

Please find more details located at: http://communities.vmware.com/docs/DOC-9020

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine. Clones may be stored on any type of datastore (LOCAL, SAN, NFS) that is presented to the ESX host. The script is very capable in deploying a large VDI environment in a relatively short amount of time.

There are currently 3 supported use cases:

1) '''Default'''&lt;br&gt;
--Description: Generate linked clones located in the same datastore that houses the master (golden) virtual machine. Writes will be directed to their respective linked virtual machine delta file with reads originating from the master virtual machine. 

2) '''Distributed Write(s) I/O'''&lt;br&gt;
--Description: Generate linked clones evenly across available datastores of choice. Reads will originate from the specified master virtual machine while writes are directed towards their respective virtual machine delta files that have been dispersed across the specified datastores. 

3) '''Distributed Read(s) &amp; Write(s) I/O'''&lt;br&gt;
--Description: Duplicate the master virtual machine on available datastores of choice and evenly generate linked clones off of each duplicated master virtual machine. Reads and writes will be isolated onto the datastore of the linked clone(s) in question. This process is similar to running multiple instances of the default behavior of the script. 

'''Note''': This linked clones script is virtual machine OS independent (i.e. it is not restricted to just Windows OS's for VDI environment). For example, one can utilize this script to their advantage in development environments where new VMs need to be (mass) cloned quickly for testing.</text>
    <sha1>56fa56b8bc210d041102dca4a631536432010db2</sha1>
  </revision>
  <revision>
    <id>722</id>
    <parentid>715</parentid>
    <timestamp>2009-01-05T20:56:17Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1882" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghetto-esx-linked-clones.sh ghetto-esx-linked-clones.sh]

'''Compatiable with''': ESX 3.x+

Please find more details located at: http://communities.vmware.com/docs/DOC-9020

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine. Clones may be stored on any type of datastore (LOCAL, SAN, NFS) that is presented to the ESX host. The script is very capable in deploying a large VDI environment in a relatively short amount of time.

There are currently 3 supported use cases:

1) '''Default'''&lt;br&gt;
--Description: Generate linked clones located in the same datastore that houses the master (golden) virtual machine. Writes will be directed to their respective linked virtual machine delta file with reads originating from the master virtual machine. 

2) '''Distributed Write(s) I/O'''&lt;br&gt;
--Description: Generate linked clones evenly across available datastores of choice. Reads will originate from the specified master virtual machine while writes are directed towards their respective virtual machine delta files that have been dispersed across the specified datastores. 

3) '''Distributed Read(s) &amp; Write(s) I/O'''&lt;br&gt;
--Description: Duplicate the master virtual machine on available datastores of choice and evenly generate linked clones off of each duplicated master virtual machine. Reads and writes will be isolated onto the datastore of the linked clone(s) in question. This process is similar to running multiple instances of the default behavior of the script. 

'''Note''': This linked clones script is virtual machine OS independent (i.e. it is not restricted to just Windows OS's for VDI environment). For example, one can utilize this script to their advantage in development environments where new VMs need to be (mass) cloned quickly for testing.</text>
    <sha1>0454ffbf1f45c50e7cc52bc508a156100d265f9c</sha1>
  </revision>
  <revision>
    <id>729</id>
    <parentid>722</parentid>
    <timestamp>2009-01-05T21:02:41Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>[[Linked Clones for ESX 3.x]] moved to [[Linked Clones for ESX 3.+]]: Supports ESX 3.0.0 up to latest ESX 3.5.0 Update 3</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1882" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghetto-esx-linked-clones.sh ghetto-esx-linked-clones.sh]

'''Compatiable with''': ESX 3.x+

Please find more details located at: http://communities.vmware.com/docs/DOC-9020

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine. Clones may be stored on any type of datastore (LOCAL, SAN, NFS) that is presented to the ESX host. The script is very capable in deploying a large VDI environment in a relatively short amount of time.

There are currently 3 supported use cases:

1) '''Default'''&lt;br&gt;
--Description: Generate linked clones located in the same datastore that houses the master (golden) virtual machine. Writes will be directed to their respective linked virtual machine delta file with reads originating from the master virtual machine. 

2) '''Distributed Write(s) I/O'''&lt;br&gt;
--Description: Generate linked clones evenly across available datastores of choice. Reads will originate from the specified master virtual machine while writes are directed towards their respective virtual machine delta files that have been dispersed across the specified datastores. 

3) '''Distributed Read(s) &amp; Write(s) I/O'''&lt;br&gt;
--Description: Duplicate the master virtual machine on available datastores of choice and evenly generate linked clones off of each duplicated master virtual machine. Reads and writes will be isolated onto the datastore of the linked clone(s) in question. This process is similar to running multiple instances of the default behavior of the script. 

'''Note''': This linked clones script is virtual machine OS independent (i.e. it is not restricted to just Windows OS's for VDI environment). For example, one can utilize this script to their advantage in development environments where new VMs need to be (mass) cloned quickly for testing.</text>
    <sha1>0454ffbf1f45c50e7cc52bc508a156100d265f9c</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Linked Clones for ESXi</title>
  <ns>0</ns>
  <id>403</id>
  <revision>
    <id>716</id>
    <timestamp>2009-01-05T20:43:55Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Compatiable with''': ESXi  Please find more details located at: http://communities.vmware.com/docs/DOC-9202  This script allows users to create linked cloned virtual machine(s) from a m...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="428" xml:space="preserve">'''Compatiable with''': ESXi

Please find more details located at: http://communities.vmware.com/docs/DOC-9202

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine on ESXi. The only supported use case is that of the default behavior of the "ghetto-esx-linked-clones.sh" script which is due to some of the limitations in the ESXi Busybox Service Console like environment.</text>
    <sha1>d12bc63b7258868fcd3c79984b4907ea2a832ce1</sha1>
  </revision>
  <revision>
    <id>721</id>
    <parentid>716</parentid>
    <timestamp>2009-01-05T20:55:45Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="553" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghetto-esxi-linked-clones.sh ghetto-esxi-linked-clones.sh]

'''Compatiable with''': ESXi

Please find more details located at: http://communities.vmware.com/docs/DOC-9202

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine on ESXi. The only supported use case is that of the default behavior of the "ghetto-esx-linked-clones.sh" script which is due to some of the limitations in the ESXi Busybox Service Console like environment.</text>
    <sha1>62bf7b79fc3022400e52eb749715ea9b971a160a</sha1>
  </revision>
  <revision>
    <id>737</id>
    <parentid>721</parentid>
    <timestamp>2009-01-05T22:32:06Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="621" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghetto-esxi-linked-clones.sh ghetto-esxi-linked-clones.sh]

'''Compatiable with''': ESXi

Please find more details located at: http://communities.vmware.com/docs/DOC-9202

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine on ESXi. The only supported use case is that of the default behavior of the "ghetto-esx-linked-clones.sh" script which is due to some of the limitations in the ESXi Busybox Service Console like environment.

[[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Automation]]</text>
    <sha1>97923206065ff0c058ef7f2e41724e174e2b34bd</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Custom my-vmware-cmd management script</title>
  <ns>0</ns>
  <id>404</id>
  <revision>
    <id>717</id>
    <timestamp>2009-01-05T20:51:10Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Supported On''': ESX 3.5+ and ESXi  Please find more details located at: http://communities.vmware.com/docs/DOC-9061  This is a custom management script to help administer large virtual...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2643" xml:space="preserve">'''Supported On''': ESX 3.5+ and ESXi

Please find more details located at: http://communities.vmware.com/docs/DOC-9061

This is a custom management script to help administer large virtual machine environments. This script is used to run administrative commands across a large set of virtual machines specified in a file. In particular, this tool complements the developed linked clones. scripts. For example, to save unique attributes (Active Directory personalities, etc.) for each linked VM, a final snapshot is executed on all linked VMs after joining each to the domain. After a specified duration, this script is then used to revert each VM back to a clean state. The same may be applied on other (non-linked) virtual machines currently residing on the ESX(i) server(s). 

'''To get list of options, just execute the script''':
  [root@himalaya scripts]# ./my-vmware-cmd.sh

'''Operations available''':
  Usage:
        Local execution-
            my-vmware-cmd.sh [operation] [vm_input_file] &lt;optional_arguments&gt;
        Remote execution-
            my-vmware-cmd.sh remote [ESX_ESXI_IP_ADDRESS] [operation] [vm_input_file] &lt;optional_arguments&gt;
   Operations:
        start [vm_input_file]
           -- Start all VMs in the input file
        stop [vm_input_file]
           -- Stop all VMs in the input file
        suspend [vm_input_file]
           -- Suspend all VMs in the input file
        resume [vm_input_file]
           -- Resume all suspended VMs in the input file
        reset [vm_input_file]
           -- Hard reset all VMs in the input file
        shutdown [vm_input_file]
           -- Shutdown all VMs in the input file (VMware Tools required)
        reboot [vm_input_file]
           -- Reboot all VMs in the input file (VMware Tools required)
        snap [vm_input_file]
           -- Create administrative pristine snapshot of all VMs in the input file
        revert [vm_input_file]
           -- Revert all VMs in the input file back to pristine state
        purge [vm_input_file]
           -- Removes from local inventory and purges all VMs in the input file
        mac [vm_input_file] [generic|nixdhcp] [NETWORK (172.30.0)] [HOST_COUNT_START (200)] &lt;NIC_#&gt; default=0
           -- Extracts MAC addresses and generates either a generic file or one compatible with *nix dhcpd
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] generic )
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] nixdhcp 172.30.0 200 )
        vnic [vm_input_file] &lt;NIC_#&gt; default=0
           -- Change vNic portgroup for all VMs in the input file
               ( e.g. my-vmware-cmd.sh vnic [vm_input_file] 3 )</text>
    <sha1>961acc40dae1932869d7fe7a160e7d8bb45a3381</sha1>
  </revision>
  <revision>
    <id>720</id>
    <parentid>717</parentid>
    <timestamp>2009-01-05T20:55:09Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2744" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmware-cmd.sh my-vmware-cmd.sh]

'''Supported On''': ESX 3.5+ and ESXi

Please find more details located at: http://communities.vmware.com/docs/DOC-9061

This is a custom management script to help administer large virtual machine environments. This script is used to run administrative commands across a large set of virtual machines specified in a file. In particular, this tool complements the developed linked clones. scripts. For example, to save unique attributes (Active Directory personalities, etc.) for each linked VM, a final snapshot is executed on all linked VMs after joining each to the domain. After a specified duration, this script is then used to revert each VM back to a clean state. The same may be applied on other (non-linked) virtual machines currently residing on the ESX(i) server(s). 

'''To get list of options, just execute the script''':
  [root@himalaya scripts]# ./my-vmware-cmd.sh

'''Operations available''':
  Usage:
        Local execution-
            my-vmware-cmd.sh [operation] [vm_input_file] &lt;optional_arguments&gt;
        Remote execution-
            my-vmware-cmd.sh remote [ESX_ESXI_IP_ADDRESS] [operation] [vm_input_file] &lt;optional_arguments&gt;
   Operations:
        start [vm_input_file]
           -- Start all VMs in the input file
        stop [vm_input_file]
           -- Stop all VMs in the input file
        suspend [vm_input_file]
           -- Suspend all VMs in the input file
        resume [vm_input_file]
           -- Resume all suspended VMs in the input file
        reset [vm_input_file]
           -- Hard reset all VMs in the input file
        shutdown [vm_input_file]
           -- Shutdown all VMs in the input file (VMware Tools required)
        reboot [vm_input_file]
           -- Reboot all VMs in the input file (VMware Tools required)
        snap [vm_input_file]
           -- Create administrative pristine snapshot of all VMs in the input file
        revert [vm_input_file]
           -- Revert all VMs in the input file back to pristine state
        purge [vm_input_file]
           -- Removes from local inventory and purges all VMs in the input file
        mac [vm_input_file] [generic|nixdhcp] [NETWORK (172.30.0)] [HOST_COUNT_START (200)] &lt;NIC_#&gt; default=0
           -- Extracts MAC addresses and generates either a generic file or one compatible with *nix dhcpd
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] generic )
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] nixdhcp 172.30.0 200 )
        vnic [vm_input_file] &lt;NIC_#&gt; default=0
           -- Change vNic portgroup for all VMs in the input file
               ( e.g. my-vmware-cmd.sh vnic [vm_input_file] 3 )</text>
    <sha1>bda8fa655363b5cc1b2e93ffda796d7e280164c6</sha1>
  </revision>
  <revision>
    <id>738</id>
    <parentid>720</parentid>
    <timestamp>2009-01-05T22:32:25Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2830" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmware-cmd.sh my-vmware-cmd.sh]

'''Supported On''': ESX 3.5+ and ESXi

Please find more details located at: http://communities.vmware.com/docs/DOC-9061

This is a custom management script to help administer large virtual machine environments. This script is used to run administrative commands across a large set of virtual machines specified in a file. In particular, this tool complements the developed linked clones. scripts. For example, to save unique attributes (Active Directory personalities, etc.) for each linked VM, a final snapshot is executed on all linked VMs after joining each to the domain. After a specified duration, this script is then used to revert each VM back to a clean state. The same may be applied on other (non-linked) virtual machines currently residing on the ESX(i) server(s). 

'''To get list of options, just execute the script''':
  [root@himalaya scripts]# ./my-vmware-cmd.sh

'''Operations available''':
  Usage:
        Local execution-
            my-vmware-cmd.sh [operation] [vm_input_file] &lt;optional_arguments&gt;
        Remote execution-
            my-vmware-cmd.sh remote [ESX_ESXI_IP_ADDRESS] [operation] [vm_input_file] &lt;optional_arguments&gt;
   Operations:
        start [vm_input_file]
           -- Start all VMs in the input file
        stop [vm_input_file]
           -- Stop all VMs in the input file
        suspend [vm_input_file]
           -- Suspend all VMs in the input file
        resume [vm_input_file]
           -- Resume all suspended VMs in the input file
        reset [vm_input_file]
           -- Hard reset all VMs in the input file
        shutdown [vm_input_file]
           -- Shutdown all VMs in the input file (VMware Tools required)
        reboot [vm_input_file]
           -- Reboot all VMs in the input file (VMware Tools required)
        snap [vm_input_file]
           -- Create administrative pristine snapshot of all VMs in the input file
        revert [vm_input_file]
           -- Revert all VMs in the input file back to pristine state
        purge [vm_input_file]
           -- Removes from local inventory and purges all VMs in the input file
        mac [vm_input_file] [generic|nixdhcp] [NETWORK (172.30.0)] [HOST_COUNT_START (200)] &lt;NIC_#&gt; default=0
           -- Extracts MAC addresses and generates either a generic file or one compatible with *nix dhcpd
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] generic )
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] nixdhcp 172.30.0 200 )
        vnic [vm_input_file] &lt;NIC_#&gt; default=0
           -- Change vNic portgroup for all VMs in the input file
               ( e.g. my-vmware-cmd.sh vnic [vm_input_file] 3 )

[[Category: ESX]] [[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Automation]]</text>
    <sha1>f4dd017b2a47f3149d546df8f325577425c81b8f</sha1>
  </revision>
  <revision>
    <id>745</id>
    <parentid>738</parentid>
    <timestamp>2009-01-05T23:00:27Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2857" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmware-cmd.sh my-vmware-cmd.sh]

'''Supported On''': ESX 3.5+ and ESXi

Please find more details located at: http://communities.vmware.com/docs/DOC-9061

This is a custom management script to help administer large virtual machine environments. This script is used to run administrative commands across a large set of virtual machines specified in a file. In particular, this tool complements the developed linked clones. scripts. For example, to save unique attributes (Active Directory personalities, etc.) for each linked VM, a final snapshot is executed on all linked VMs after joining each to the domain. After a specified duration, this script is then used to revert each VM back to a clean state. The same may be applied on other (non-linked) virtual machines currently residing on the ESX(i) server(s). 

'''To get list of options, just execute the script''':
  [root@himalaya scripts]# ./my-vmware-cmd.sh

'''Operations available''':
  Usage:
        Local execution-
            my-vmware-cmd.sh [operation] [vm_input_file] &lt;optional_arguments&gt;
        Remote execution-
            my-vmware-cmd.sh remote [ESX_ESXI_IP_ADDRESS] [operation] [vm_input_file] &lt;optional_arguments&gt;
   Operations:
        start [vm_input_file]
           -- Start all VMs in the input file
        stop [vm_input_file]
           -- Stop all VMs in the input file
        suspend [vm_input_file]
           -- Suspend all VMs in the input file
        resume [vm_input_file]
           -- Resume all suspended VMs in the input file
        reset [vm_input_file]
           -- Hard reset all VMs in the input file
        shutdown [vm_input_file]
           -- Shutdown all VMs in the input file (VMware Tools required)
        reboot [vm_input_file]
           -- Reboot all VMs in the input file (VMware Tools required)
        snap [vm_input_file]
           -- Create administrative pristine snapshot of all VMs in the input file
        revert [vm_input_file]
           -- Revert all VMs in the input file back to pristine state
        purge [vm_input_file]
           -- Removes from local inventory and purges all VMs in the input file
        mac [vm_input_file] [generic|nixdhcp] [NETWORK (172.30.0)] [HOST_COUNT_START (200)] &lt;NIC_#&gt; default=0
           -- Extracts MAC addresses and generates either a generic file or one compatible with *nix dhcpd
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] generic )
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] nixdhcp 172.30.0 200 )
        vnic [vm_input_file] &lt;NIC_#&gt; default=0
           -- Change vNic portgroup for all VMs in the input file
               ( e.g. my-vmware-cmd.sh vnic [vm_input_file] 3 )

[[Category: ESX]] [[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Automation]] [[Category: VM Managment]]</text>
    <sha1>2b6c4a2a5db620e7f587b9ac2b6115cab489e390</sha1>
  </revision>
  <revision>
    <id>746</id>
    <parentid>745</parentid>
    <timestamp>2009-01-05T23:01:02Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2858" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmware-cmd.sh my-vmware-cmd.sh]

'''Supported On''': ESX 3.5+ and ESXi

Please find more details located at: http://communities.vmware.com/docs/DOC-9061

This is a custom management script to help administer large virtual machine environments. This script is used to run administrative commands across a large set of virtual machines specified in a file. In particular, this tool complements the developed linked clones. scripts. For example, to save unique attributes (Active Directory personalities, etc.) for each linked VM, a final snapshot is executed on all linked VMs after joining each to the domain. After a specified duration, this script is then used to revert each VM back to a clean state. The same may be applied on other (non-linked) virtual machines currently residing on the ESX(i) server(s). 

'''To get list of options, just execute the script''':
  [root@himalaya scripts]# ./my-vmware-cmd.sh

'''Operations available''':
  Usage:
        Local execution-
            my-vmware-cmd.sh [operation] [vm_input_file] &lt;optional_arguments&gt;
        Remote execution-
            my-vmware-cmd.sh remote [ESX_ESXI_IP_ADDRESS] [operation] [vm_input_file] &lt;optional_arguments&gt;
   Operations:
        start [vm_input_file]
           -- Start all VMs in the input file
        stop [vm_input_file]
           -- Stop all VMs in the input file
        suspend [vm_input_file]
           -- Suspend all VMs in the input file
        resume [vm_input_file]
           -- Resume all suspended VMs in the input file
        reset [vm_input_file]
           -- Hard reset all VMs in the input file
        shutdown [vm_input_file]
           -- Shutdown all VMs in the input file (VMware Tools required)
        reboot [vm_input_file]
           -- Reboot all VMs in the input file (VMware Tools required)
        snap [vm_input_file]
           -- Create administrative pristine snapshot of all VMs in the input file
        revert [vm_input_file]
           -- Revert all VMs in the input file back to pristine state
        purge [vm_input_file]
           -- Removes from local inventory and purges all VMs in the input file
        mac [vm_input_file] [generic|nixdhcp] [NETWORK (172.30.0)] [HOST_COUNT_START (200)] &lt;NIC_#&gt; default=0
           -- Extracts MAC addresses and generates either a generic file or one compatible with *nix dhcpd
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] generic )
               ( e.g. my-vmware-cmd.sh mac [vm_input_file] nixdhcp 172.30.0 200 )
        vnic [vm_input_file] &lt;NIC_#&gt; default=0
           -- Change vNic portgroup for all VMs in the input file
               ( e.g. my-vmware-cmd.sh vnic [vm_input_file] 3 )

[[Category: ESX]] [[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Automation]] [[Category: VM Management]]</text>
    <sha1>c515036d76aa5c38352d49ad1a9cf76c6917e238</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Locate all VMs with NPIV WWN for ESX</title>
  <ns>0</ns>
  <id>405</id>
  <revision>
    <id>718</id>
    <timestamp>2009-01-05T20:53:58Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: Download script: [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esx.sh npiv_wwn_discovery-esx.sh]  This script is used to locate all virtual machines that have the NPIV optio...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="420" xml:space="preserve">Download script: [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esx.sh npiv_wwn_discovery-esx.sh]

This script is used to locate all virtual machines that have the NPIV option enabled and provide the VMs Name, Port WWN, Node WWN and the WWN TYPE on an ESX host. This can possibly list virtual machines with the NPIV option in a cluster if the ESX host is connected to all datastores present to the cluster.</text>
    <sha1>8501786734f06e713441ac33b06ab6853542b2bf</sha1>
  </revision>
  <revision>
    <id>719</id>
    <parentid>718</parentid>
    <timestamp>2009-01-05T20:54:10Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="426" xml:space="preserve">'''Download script:''' [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esx.sh npiv_wwn_discovery-esx.sh]

This script is used to locate all virtual machines that have the NPIV option enabled and provide the VMs Name, Port WWN, Node WWN and the WWN TYPE on an ESX host. This can possibly list virtual machines with the NPIV option in a cluster if the ESX host is connected to all datastores present to the cluster.</text>
    <sha1>4640e9ed77329b6cb9fb96914559f8cfea0927ef</sha1>
  </revision>
  <revision>
    <id>723</id>
    <parentid>719</parentid>
    <timestamp>2009-01-05T20:57:03Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="460" xml:space="preserve">'''Download script:''' [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esx.sh npiv_wwn_discovery-esx.sh]

'''Compatiable with''': ESX 3.5+

This script is used to locate all virtual machines that have the NPIV option enabled and provide the VMs Name, Port WWN, Node WWN and the WWN TYPE on an ESX host. This can possibly list virtual machines with the NPIV option in a cluster if the ESX host is connected to all datastores present to the cluster.</text>
    <sha1>839fa56870003beb4b40ece9c7b398e9eb1cb320</sha1>
  </revision>
  <revision>
    <id>739</id>
    <parentid>723</parentid>
    <timestamp>2009-01-05T22:32:55Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="527" xml:space="preserve">'''Download script:''' [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esx.sh npiv_wwn_discovery-esx.sh]

'''Compatiable with''': ESX 3.5+

This script is used to locate all virtual machines that have the NPIV option enabled and provide the VMs Name, Port WWN, Node WWN and the WWN TYPE on an ESX host. This can possibly list virtual machines with the NPIV option in a cluster if the ESX host is connected to all datastores present to the cluster.

[[Category: ESX]] [[Category: Vimsh]] [[Category: VM Automation]]</text>
    <sha1>0fbdc1b806efd81ca7a66add4886d43a7841ed99</sha1>
  </revision>
  <revision>
    <id>747</id>
    <parentid>739</parentid>
    <timestamp>2009-01-05T23:02:10Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="527" xml:space="preserve">'''Download script:''' [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esx.sh npiv_wwn_discovery-esx.sh]

'''Compatiable with''': ESX 3.5+

This script is used to locate all virtual machines that have the NPIV option enabled and provide the VMs Name, Port WWN, Node WWN and the WWN TYPE on an ESX host. This can possibly list virtual machines with the NPIV option in a cluster if the ESX host is connected to all datastores present to the cluster.

[[Category: ESX]] [[Category: Vimsh]] [[Category: VM Management]]</text>
    <sha1>1f7574bb65b5a5990199d36481e07454fc373b1f</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Locate all VMs with NPIV WWN for ESXi</title>
  <ns>0</ns>
  <id>406</id>
  <revision>
    <id>724</id>
    <timestamp>2009-01-05T20:58:00Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esxi.sh npiv_wwn_discovery-esxi.sh]  '''Compatiable with''': ESXi 3.5+  This script is used to locate al...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="315" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esxi.sh npiv_wwn_discovery-esxi.sh]

'''Compatiable with''': ESXi 3.5+

This script is used to locate all virtual machines that have NPIV option enabled and provide the VMs Name, Port WWN, Node WWN and the WWN TYPE on an ESXi host.</text>
    <sha1>da0103ad7183fe7faf970f5325550fe0a04a3137</sha1>
  </revision>
  <revision>
    <id>740</id>
    <parentid>724</parentid>
    <timestamp>2009-01-05T22:33:09Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="383" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esxi.sh npiv_wwn_discovery-esxi.sh]

'''Compatiable with''': ESXi 3.5+

This script is used to locate all virtual machines that have NPIV option enabled and provide the VMs Name, Port WWN, Node WWN and the WWN TYPE on an ESXi host.

[[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Automation]]</text>
    <sha1>3f6d63d5c02d9e263a30bda249ed8964b9b5fcde</sha1>
  </revision>
  <revision>
    <id>748</id>
    <parentid>740</parentid>
    <timestamp>2009-01-05T23:02:17Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="383" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/npiv_wwn_discovery-esxi.sh npiv_wwn_discovery-esxi.sh]

'''Compatiable with''': ESXi 3.5+

This script is used to locate all virtual machines that have NPIV option enabled and provide the VMs Name, Port WWN, Node WWN and the WWN TYPE on an ESXi host.

[[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Management]]</text>
    <sha1>73050b9a8fac96934adf1cf414848c32bd60f25e</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Locate all VMs with RDMs for ESX and ESXi</title>
  <ns>0</ns>
  <id>407</id>
  <revision>
    <id>725</id>
    <timestamp>2009-01-05T20:58:38Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/rdm.sh rdm.sh]  '''Compatiable with''': ESX 3.5+ and ESXi  This script is used to locate all virtual machines that have an ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="348" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/rdm.sh rdm.sh]

'''Compatiable with''': ESX 3.5+ and ESXi

This script is used to locate all virtual machines that have an RDM mapping and provides the VMs Name, Hard Disk label shown on the VIC/VC, Datastore, LUN UUID, HBA/LUN, Compatibility Mode (Phys/Virt), DiskMode and Capacity.</text>
    <sha1>03e3a277a10754baf7ec11e68edfe2f2b2cb8d28</sha1>
  </revision>
  <revision>
    <id>741</id>
    <parentid>725</parentid>
    <timestamp>2009-01-05T22:33:26Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="434" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/rdm.sh rdm.sh]

'''Compatiable with''': ESX 3.5+ and ESXi

This script is used to locate all virtual machines that have an RDM mapping and provides the VMs Name, Hard Disk label shown on the VIC/VC, Datastore, LUN UUID, HBA/LUN, Compatibility Mode (Phys/Virt), DiskMode and Capacity.

[[Category: ESX]] [[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Automation]]</text>
    <sha1>055dae383f910abbfb9c7feb64e2a3023b180904</sha1>
  </revision>
  <revision>
    <id>749</id>
    <parentid>741</parentid>
    <timestamp>2009-01-05T23:02:24Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="434" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/rdm.sh rdm.sh]

'''Compatiable with''': ESX 3.5+ and ESXi

This script is used to locate all virtual machines that have an RDM mapping and provides the VMs Name, Hard Disk label shown on the VIC/VC, Datastore, LUN UUID, HBA/LUN, Compatibility Mode (Phys/Virt), DiskMode and Capacity.

[[Category: ESX]] [[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Management]]</text>
    <sha1>8c7ee7e9e9cc01005163ee7ddef7330a8c6917a9</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Free VM backup solution for ESX and ESXi</title>
  <ns>0</ns>
  <id>408</id>
  <revision>
    <id>726</id>
    <timestamp>2009-01-05T20:59:23Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: Please find more details located at: http://communities.vmware.com/docs/DOC-8760  '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoVCB.sh ghettoVCB.sh]  '''Compatiabl...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="626" xml:space="preserve">Please find more details located at: http://communities.vmware.com/docs/DOC-8760

'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoVCB.sh ghettoVCB.sh]

'''Compatiable with''': ESX 3.5+ and ESXi

This is a non-interactive script that backs up a specified list of VMs to a chosen datastore. Supported datastores are: local storage, SAN and NFS. The nature of the script allows backups to be scheduled via crontab. The script also provides an option to backup virtual machines to a non-persistent NFS share. The NFS connection is created on the ESX(i) server and is disconnected upon completion of backups.</text>
    <sha1>2006bff9ef42e622a6a3aed1d0d80210ac18c599</sha1>
  </revision>
  <revision>
    <id>742</id>
    <parentid>726</parentid>
    <timestamp>2009-01-05T22:34:01Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="755" xml:space="preserve">Please find more details located at: http://communities.vmware.com/docs/DOC-8760

'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoVCB.sh ghettoVCB.sh]

'''Compatiable with''': ESX 3.5+ and ESXi

This is a non-interactive script that backs up a specified list of VMs to a chosen datastore. Supported datastores are: local storage, SAN and NFS. The nature of the script allows backups to be scheduled via crontab. The script also provides an option to backup virtual machines to a non-persistent NFS share. The NFS connection is created on the ESX(i) server and is disconnected upon completion of backups.

[[Category: ESX]] [[Category: ESXi]] [[Category: ESXi]] [[Category: Vimsh]] [[Category: VM Automation]] [[Category: VM Backup]]</text>
    <sha1>c480ece1eab3b0d0d2f5963e0159772bd6e3484c</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Linked Clones for ESX 3.x</title>
  <ns>0</ns>
  <id>409</id>
  <revision>
    <id>730</id>
    <timestamp>2009-01-05T21:02:41Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>[[Linked Clones for ESX 3.x]] moved to [[Linked Clones for ESX 3.+]]: Supports ESX 3.0.0 up to latest ESX 3.5.0 Update 3</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39" xml:space="preserve">#REDIRECT [[Linked Clones for ESX 3.+]]</text>
    <sha1>64703ec5304f3a053a3acec655c41ee15e2eff41</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Linked Clones for ESX 3.x+</title>
  <ns>0</ns>
  <id>410</id>
  <revision>
    <id>734</id>
    <timestamp>2009-01-05T21:04:02Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghetto-esx-linked-clones.sh ghetto-esx-linked-clones.sh]  '''Compatiable with''': ESX 3.x+  Please find more details locate...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1882" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghetto-esx-linked-clones.sh ghetto-esx-linked-clones.sh]

'''Compatiable with''': ESX 3.x+

Please find more details located at: http://communities.vmware.com/docs/DOC-9020

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine. Clones may be stored on any type of datastore (LOCAL, SAN, NFS) that is presented to the ESX host. The script is very capable in deploying a large VDI environment in a relatively short amount of time.

There are currently 3 supported use cases:

1) '''Default'''&lt;br&gt;
--Description: Generate linked clones located in the same datastore that houses the master (golden) virtual machine. Writes will be directed to their respective linked virtual machine delta file with reads originating from the master virtual machine. 

2) '''Distributed Write(s) I/O'''&lt;br&gt;
--Description: Generate linked clones evenly across available datastores of choice. Reads will originate from the specified master virtual machine while writes are directed towards their respective virtual machine delta files that have been dispersed across the specified datastores. 

3) '''Distributed Read(s) &amp; Write(s) I/O'''&lt;br&gt;
--Description: Duplicate the master virtual machine on available datastores of choice and evenly generate linked clones off of each duplicated master virtual machine. Reads and writes will be isolated onto the datastore of the linked clone(s) in question. This process is similar to running multiple instances of the default behavior of the script. 

'''Note''': This linked clones script is virtual machine OS independent (i.e. it is not restricted to just Windows OS's for VDI environment). For example, one can utilize this script to their advantage in development environments where new VMs need to be (mass) cloned quickly for testing.</text>
    <sha1>0454ffbf1f45c50e7cc52bc508a156100d265f9c</sha1>
  </revision>
  <revision>
    <id>736</id>
    <parentid>734</parentid>
    <timestamp>2009-01-05T22:31:37Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1949" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghetto-esx-linked-clones.sh ghetto-esx-linked-clones.sh]

'''Compatiable with''': ESX 3.x+

Please find more details located at: http://communities.vmware.com/docs/DOC-9020

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine. Clones may be stored on any type of datastore (LOCAL, SAN, NFS) that is presented to the ESX host. The script is very capable in deploying a large VDI environment in a relatively short amount of time.

There are currently 3 supported use cases:

1) '''Default'''&lt;br&gt;
--Description: Generate linked clones located in the same datastore that houses the master (golden) virtual machine. Writes will be directed to their respective linked virtual machine delta file with reads originating from the master virtual machine. 

2) '''Distributed Write(s) I/O'''&lt;br&gt;
--Description: Generate linked clones evenly across available datastores of choice. Reads will originate from the specified master virtual machine while writes are directed towards their respective virtual machine delta files that have been dispersed across the specified datastores. 

3) '''Distributed Read(s) &amp; Write(s) I/O'''&lt;br&gt;
--Description: Duplicate the master virtual machine on available datastores of choice and evenly generate linked clones off of each duplicated master virtual machine. Reads and writes will be isolated onto the datastore of the linked clone(s) in question. This process is similar to running multiple instances of the default behavior of the script. 

'''Note''': This linked clones script is virtual machine OS independent (i.e. it is not restricted to just Windows OS's for VDI environment). For example, one can utilize this script to their advantage in development environments where new VMs need to be (mass) cloned quickly for testing.

[[Category: ESX]] [[Category: Vimsh]] [[Category: VM Automation]]</text>
    <sha1>c60b9cc003ea701f23376979393ab0237a9fd406</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>User:Lamw</title>
  <ns>2</ns>
  <id>411</id>
  <revision>
    <id>735</id>
    <timestamp>2009-01-05T21:39:00Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: William lam  [http://www.linkedin.com/in/lamwilliam William's LinkedIn Profile]  http://engineering.ucsb.edu/~duonglt/vmware/</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">William lam

[http://www.linkedin.com/in/lamwilliam William's LinkedIn Profile]

http://engineering.ucsb.edu/~duonglt/vmware/</text>
    <sha1>13cf734fc22970427e4c64e4ecb7132ee0b97e59</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/datastore/listvm</title>
  <ns>0</ns>
  <id>306</id>
  <revision>
    <id>751</id>
    <parentid>578</parentid>
    <timestamp>2009-01-05T23:12:04Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1039" xml:space="preserve">==== vimsh hostsvc/datastore/listvm ====
Usage: listvm name

Retrieve the virtual machines stored on the datastore.

==== Example output ====
 [root@himalaya scripts]# vmware-vim-cmd hostsvc/datastore/listvm "himalaya-local-SAS.VMStorage"
 (ManagedObjectReference) [
   'vim.VirtualMachine:1040',
   'vim.VirtualMachine:1072',
   'vim.VirtualMachine:16',
   'vim.VirtualMachine:1680',
   'vim.VirtualMachine:176',
   'vim.VirtualMachine:21168',
   'vim.VirtualMachine:31168',
   'vim.VirtualMachine:31248',
   'vim.VirtualMachine:31968',
   'vim.VirtualMachine:32',
   'vim.VirtualMachine:59216',
   'vim.VirtualMachine:59312',
   'vim.VirtualMachine:59392',
   'vim.VirtualMachine:59408',
   'vim.VirtualMachine:59424',
   'vim.VirtualMachine:59712',
   'vim.VirtualMachine:59792',
   'vim.VirtualMachine:60064',
   'vim.VirtualMachine:64',
   'vim.VirtualMachine:784',
   'vim.VirtualMachine:80',
   'vim.VirtualMachine:880',
   'vim.VirtualMachine:928',
   'vim.VirtualMachine:96',
   'vim.VirtualMachine:976'
 ]


[[Category: Vimsh]]</text>
    <sha1>fb8e73bcfadd41f4ad7f9eace59571dc124d91fa</sha1>
  </revision>
</page>
<page arvcontinue="20090104142801|703">
  <title>Hostsvc/net/capabilities</title>
  <ns>0</ns>
  <id>100</id>
  <revision>
    <id>752</id>
    <parentid>247</parentid>
    <timestamp>2009-01-05T23:16:27Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="764" xml:space="preserve">==== vimsh hostsvc/net/capabilities ====
Usage: capabilities

Get the network capabilities.

==== Example output ====
 [root@himalaya scripts]# vmware-vim-cmd hostsvc/net/capabilities
 (vim.host.NetCapabilities) {
   dynamicType = &lt;unset&gt;,
   canSetPhysicalNicLinkSpeed = true,
   supportsNicTeaming = true,
   nicTeamingPolicy = (string) [
      "loadbalance_ip",
      "loadbalance_srcmac",
      "loadbalance_srcid",
      "failover_explicit"
   ],
   supportsVlan = true,
   usesServiceConsoleNic = true,
   supportsNetworkHints = true,
   maxPortGroupsPerVswitch = &lt;unset&gt;,
   vswitchConfigSupported = true,
   vnicConfigSupported = true,
   ipRouteConfigSupported = true,
   dnsConfigSupported = true,
   dhcpOnVnicSupported = false,
 }


[[Category: Vimsh]]</text>
    <sha1>70b0df852b67decdbe93c4ac6a7f415f15f03547</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Hostsvc/rsrc/pools get</title>
  <ns>0</ns>
  <id>331</id>
  <revision>
    <id>753</id>
    <parentid>608</parentid>
    <timestamp>2009-01-05T23:20:42Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="507" xml:space="preserve">==== vimsh hostsvc/rsrc/pools_get ====
Usage: pools_get poolId

Get the list of pools nested within the specified pool.

==== Example ====

To extract the poolId, you actually have to look in the following file:

  /etc/vmware/hostd/pools.xml

Here is a quick snippet of code to extract the poolId based on a VM Name:

  cat /etc/vmware/hostd/pools.xml | grep "RESOURCE_POOL_NAME" -A1 | grep "&lt;objID&gt;" | sed 's/&lt;objID&gt;//;s/&lt;\/objID&gt;//g' | sed -e 's/^[[:blank:]]*//;s/[[:blank:]]*$//'  


[[Category: Vimsh]]</text>
    <sha1>020da7b53021c5b1419654b575dd75bbf8bbc3cd</sha1>
  </revision>
  <revision>
    <id>754</id>
    <parentid>753</parentid>
    <timestamp>2009-01-05T23:22:03Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="946" xml:space="preserve">==== vimsh hostsvc/rsrc/pools_get ====
Usage: pools_get poolId

Get the list of pools nested within the specified pool.

==== Example ====

To extract the poolId, you actually have to look in the following file:

  /etc/vmware/hostd/pools.xml

Here is a quick snippet of code to extract the poolId based on a VM Name:

  cat /etc/vmware/hostd/pools.xml | grep "RESOURCE_POOL_NAME" -A1 | grep "&lt;objID&gt;" | sed 's/&lt;objID&gt;//;s/&lt;\/objID&gt;//g' | sed -e 's/^[[:blank:]]*//;s/[[:blank:]]*$//'  

To register a VM and assign it to a given resource pool, you can do the following (Assuming you have a VM named *UCSB-GAUCHOS* and Resource Pool named *UCSB-DEV-RP*:

  vmware-vim-cmd solo/registervm /vmfs/volumes/olga-local-SAS.Storage/UCSB-GAUCHOS/UCSB-GAUCHOS.vmx UCSB-GAUCHOS `cat /etc/vmware/hostd/pools.xml | grep "UCSB-DEV-RP" -A1 | grep "&lt;objID&gt;" | sed 's/&lt;objID&gt;//;s/&lt;\/objID&gt;//g' | sed -e 's/^[[:blank:]]*//;s/[[:blank:]]*$//'`


[[Category: Vimsh]]</text>
    <sha1>f1870819188d3401a04a08d3c4f36b15a2343015</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Solo/registervm</title>
  <ns>0</ns>
  <id>187</id>
  <revision>
    <id>755</id>
    <parentid>357</parentid>
    <timestamp>2009-01-05T23:22:56Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="641" xml:space="preserve">==== vimsh solo/registervm ====
Usage: registervm vm path [name] [resourcepool]

registervm [cfg path] [name(optional)] [resourcepool(optional)]

Register the vm

==== Example ==== 

To register a VM and assign it to a given resource pool, you can do the following (Assuming you have a VM named *UCSB-GAUCHOS* and Resource Pool named *UCSB-DEV-RP*:

  vmware-vim-cmd solo/registervm /vmfs/volumes/olga-local-SAS.Storage/UCSB-GAUCHOS/UCSB-GAUCHOS.vmx UCSB-GAUCHOS `cat /etc/vmware/hostd/pools.xml | grep "UCSB-DEV-RP" -A1 | grep "&lt;objID&gt;" | sed 's/&lt;objID&gt;//;s/&lt;\/objID&gt;//g' | sed -e 's/^[[:blank:]]*//;s/[[:blank:]]*$//'`

[[Category: Vimsh]]</text>
    <sha1>568386e2f3331d56131d431f43eac9719cf788dc</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Hostsvc/memoryinfo</title>
  <ns>0</ns>
  <id>85</id>
  <revision>
    <id>756</id>
    <parentid>229</parentid>
    <timestamp>2009-01-05T23:26:41Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="457" xml:space="preserve">==== Vimsh hostsvc/memoryinfo ====
Usage: memoryinfo [memoryCfg]

Get the memory information.  If memoryCfg is specified, sets configured memory.

==== Example output ====

 [root@himalaya scripts]# vmware-vim-cmd hostsvc/memoryinfo
 (vim.host.MemoryManagerSystem.ServiceConsoleReservationInfo) {
   dynamicType = &lt;unset&gt;,
   serviceConsoleReservedCfg = 838860800,
   serviceConsoleReserved = 838860800,
   unreserved = 12045254656,
 }


[[Category: Vimsh]]</text>
    <sha1>8ef0adda3112f4d3e33847dbd5bee074ee850aeb</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Proxysvc/service list</title>
  <ns>0</ns>
  <id>250</id>
  <revision>
    <id>757</id>
    <parentid>464</parentid>
    <timestamp>2009-01-05T23:30:00Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1584" xml:space="preserve">==== vimsh proxysvc/service_list ====
Usage: service_list

Get the list of services being proxied.

==== Example output ====

 [root@himalaya scripts]# vmware-vim-cmd proxysvc/service_list
 (vim.ProxyService.EndpointSpec) [
   (vim.ProxyService.NamedPipeServiceSpec) {
      dynamicType = &lt;unset&gt;,
      serverNamespace = "/",
      accessMode = "httpsWithRedirect",
      pipeName = "/var/run/vmware/proxy-webserver",
   },
   (vim.ProxyService.NamedPipeServiceSpec) {
      dynamicType = &lt;unset&gt;,
      serverNamespace = "/client/clients.xml",
      accessMode = "httpAndHttps",
      pipeName = "/var/run/vmware/proxy-webserver",
   },
   (vim.ProxyService.NamedPipeServiceSpec) {
      dynamicType = &lt;unset&gt;,
      serverNamespace = "/mob",
      accessMode = "httpsWithRedirect",
      pipeName = "/var/run/vmware/proxy-mob",
   },
   (vim.ProxyService.NamedPipeServiceSpec) {
      dynamicType = &lt;unset&gt;,
      serverNamespace = "/sdk",
      accessMode = "httpsWithRedirect",
      pipeName = "/var/run/vmware/proxy-sdk",
   },
   (vim.ProxyService.LocalServiceSpec) {
      dynamicType = &lt;unset&gt;,
      serverNamespace = "/ui",
      accessMode = "httpsWithRedirect",
      port = 8080,
   },
   (vim.ProxyService.NamedPipeServiceSpec) {
      dynamicType = &lt;unset&gt;,
      serverNamespace = "/vpxa",
      accessMode = "httpsOnly",
      pipeName = "/var/run/vmware/proxy-vpxa",
   },
   (vim.ProxyService.LocalServiceSpec) {
      dynamicType = &lt;unset&gt;,
      serverNamespace = "/wsman",
      accessMode = "httpsWithRedirect",
      port = 8889,
   }
 ]

[[Category: Vimsh]]</text>
    <sha1>3173ba218b62fb60efa0320a05b8feca35560e46</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vimsvc/task list</title>
  <ns>0</ns>
  <id>226</id>
  <revision>
    <id>758</id>
    <parentid>410</parentid>
    <timestamp>2009-01-05T23:31:17Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="497" xml:space="preserve">==== vimsh vimsvc/task_list ====
Usage: task_list

Get list of recent tasks.

==== Example output ====

 [root@himalaya scripts]# vmware-vim-cmd vimsvc/task_list
 (ManagedObjectReference) [
   'vim.Task:haTask-ha-root-pool-vim.ResourcePool.updateConfig-51467',
   'vim.Task:haTask-ha-root-pool-vim.ResourcePool.updateConfig-51468',
   'vim.Task:haTask-ha-root-pool-vim.ResourcePool.updateConfig-51491',
   'vim.Task:haTask-ha-root-pool-vim.ResourcePool.updateConfig-51492'
 ]


[[Category: Vimsh]]</text>
    <sha1>45644e575d143d804aa9cf137079ad8da4e7440b</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vmsvc/get.config</title>
  <ns>0</ns>
  <id>167</id>
  <revision>
    <id>759</id>
    <parentid>323</parentid>
    <timestamp>2009-01-05T23:34:02Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6771" xml:space="preserve">==== vimsh vmsvc/get.config ====
Usage: get.config vmid

Retrieves and displays the configuration object for the vm.

==== Example output ====

 [root@himalaya scripts]# vmware-vim-cmd vmsvc/get.config 31168
 Configuration:
 (vim.vm.ConfigInfo) {
   dynamicType = &lt;unset&gt;,
   changeVersion = "2009-01-01T01:13:08.765224Z",
   modified = "1970-01-01T00:00:00Z",
   name = "VIMA",
   guestFullName = "Red Hat Enterprise Linux 3 (64-bit)",
   version = "vmx-04",
   uuid = "5034d5e6-3add-6386-7d1e-01449596f169",
   npivWorldWideNameType = "",
   locationId = "564ded5c-9488-f275-fbd5-cecb5e9a482f",
   template = false,
   guestId = "rhel3_64Guest",
   alternateGuestName = "Red Hat Enterprise Linux 3 (64-bit)",
   annotation = "This OVF file contains the VMware Infrastructure Management Assistant (VIMA) virtual machine.",
   files = (vim.vm.FileInfo) {
      dynamicType = &lt;unset&gt;,
      vmPathName = "[himalaya-local-SAS.VMStorage] VIMA/VIMA.vmx",
      snapshotDirectory = "[himalaya-local-SAS.VMStorage] VIMA",
      suspendDirectory = "[himalaya-local-SAS.VMStorage] VIMA",
      logDirectory = "[himalaya-local-SAS.VMStorage] VIMA",
   },
   tools = (vim.vm.ToolsConfigInfo) {
      dynamicType = &lt;unset&gt;,
      toolsVersion = 119584,
      afterPowerOn = true,
      afterResume = true,
      beforeGuestStandby = true,
      beforeGuestShutdown = true,
      beforeGuestReboot = &lt;unset&gt;,
      toolsUpgradePolicy = "manual",
      pendingCustomization = &lt;unset&gt;,
      syncTimeWithHost = false,
   },
   flags = (vim.vm.FlagInfo) {
      dynamicType = &lt;unset&gt;,
      disableAcceleration = false,
      enableLogging = true,
      useToe = false,
      runWithDebugInfo = false,
      monitorType = "release",
      htSharing = "any",
      snapshotDisabled = &lt;unset&gt;,
      snapshotLocked = &lt;unset&gt;,
      diskUuidEnabled = false,
      virtualMmuUsage = "automatic",
      snapshotPowerOffBehavior = "powerOff",
   },
   consolePreferences = (vim.vm.ConsolePreferences) null,
   defaultPowerOps = (vim.vm.DefaultPowerOpInfo) {
      dynamicType = &lt;unset&gt;,
      powerOffType = "preset",
      suspendType = "preset",
      resetType = "preset",
      defaultPowerOffType = "hard",
      defaultSuspendType = "hard",
      defaultResetType = "hard",
      standbyAction = "checkpoint",
   },
   hardware = (vim.vm.VirtualHardware) {
      dynamicType = &lt;unset&gt;,
      numCPU = -1257091211,
      memoryMB = 286660,
   },
   cpuAllocation = (vim.ResourceAllocationInfo) {
      dynamicType = &lt;unset&gt;,
      reservation = 0,
      expandableReservation = false,
      limit = 18080,
      shares = (vim.SharesInfo) {
         dynamicType = &lt;unset&gt;,
         shares = 1000,
         level = "normal",
      },
      overheadLimit = &lt;unset&gt;,
   },
   memoryAllocation = (vim.ResourceAllocationInfo) {
      dynamicType = &lt;unset&gt;,
      reservation = 0,
      expandableReservation = false,
      limit = -1,
      shares = (vim.SharesInfo) {
         dynamicType = &lt;unset&gt;,
         shares = 5120,
         level = "normal",
      },
      overheadLimit = &lt;unset&gt;,
   },
   cpuAffinity = (vim.vm.AffinityInfo) null,
   memoryAffinity = (vim.vm.AffinityInfo) null,
   networkShaper = (vim.vm.NetworkShaperInfo) null,
   extraConfig = (vim.option.OptionValue) [
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "deploymentPlatform",
         value = "windows",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "ethernet1.features",
         value = "15",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "evcCompatibilityMode",
         value = "false",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "guestCPUID.0",
         value = "0000000a756e65476c65746e49656e69",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "guestCPUID.1",
         value = "0001067800010800000822010febfbff",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "guestCPUID.80000001",
         value = "00000000000000000000000120100000",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "hostCPUID.0",
         value = "0000000a756e65476c65746e49656e69",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "hostCPUID.1",
         value = "0001067600040800000ce3bdbfebfbff",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "hostCPUID.80000001",
         value = "00000000000000000000000120100000",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "nvram",
         value = "VIMA.nvram",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "sched.swap.derivedName",
         value = "/vmfs/volumes/48c3a8cb-92b015b9-de33-003048670886/VIMA/VIMA-6561511b.vswp",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "scsi0:0.redo",
         value = "",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "userCPUID.0",
         value = "0000000a756e65476c65746e49656e69",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "userCPUID.1",
         value = "0001067600040800000822010febfbff",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "userCPUID.80000001",
         value = "00000000000000000000000120100000",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "virtualHW.productCompatibility",
         value = "hosted",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "vmware.tools.internalversion",
         value = "7302",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "vmware.tools.requiredversion",
         value = "7302",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "vmware.tools.installstate",
         value = "none",
      },
      (vim.option.OptionValue) {
         dynamicType = &lt;unset&gt;,
         key = "vmware.tools.lastInstallStatus.result",
         value = "unknown",
      }
   ],
   datastoreUrl = (vim.vm.ConfigInfo.DatastoreUrlPair) [
      (vim.vm.ConfigInfo.DatastoreUrlPair) {
         dynamicType = &lt;unset&gt;,
         name = "himalaya-local-SAS.VMStorage",
         url = "/vmfs/volumes/48c3a8cb-92b015b9-de33-003048670886/",
      }
   ],
   swapPlacement = "inherit",
   bootOptions = (vim.vm.BootOptions) {
      dynamicType = &lt;unset&gt;,
      bootDelay = 0,
      enterBIOSSetup = false,
   },
 }


[[Category: Vimsh]]</text>
    <sha1>b848b3e56652cb7631220b9773c5edfec64e0798</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vmsvc/get.config.cpuidmask</title>
  <ns>0</ns>
  <id>168</id>
  <revision>
    <id>760</id>
    <parentid>324</parentid>
    <timestamp>2009-01-05T23:35:28Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2200" xml:space="preserve">==== vimsh vmsvc/get.config.cpuidmask ====
Usage: get.config.cpuidmask vmid

Retrieves and displays the cpu id masks for this virtual machine

==== Example output ====

 [root@himalaya scripts]# vmware-vim-cmd vmsvc/get.config.cpuidmask 31168
 (vim.host.CpuIdInfo) [
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = 0,
      vendor = &lt;unset&gt;,
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = 0,
      vendor = "amd",
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = 1,
      vendor = &lt;unset&gt;,
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = 1,
      vendor = "amd",
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = -2147483648,
      vendor = &lt;unset&gt;,
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = -2147483648,
      vendor = "amd",
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = -2147483647,
      vendor = &lt;unset&gt;,
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = -2147483647,
      vendor = "amd",
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = -2147483640,
      vendor = &lt;unset&gt;,
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   },
   (vim.host.CpuIdInfo) {
      dynamicType = &lt;unset&gt;,
      level = -2147483640,
      vendor = "amd",
      eax = &lt;unset&gt;,
      ebx = &lt;unset&gt;,
      ecx = &lt;unset&gt;,
      edx = &lt;unset&gt;,
   }
 ]


[[Category: Vimsh]]</text>
    <sha1>2f609a5153ac3c787fa9ead890b21f779e9986b9</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vmsvc/get.datastores</title>
  <ns>0</ns>
  <id>170</id>
  <revision>
    <id>761</id>
    <parentid>326</parentid>
    <timestamp>2009-01-05T23:37:18Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="507" xml:space="preserve">==== vimsh vmsvc/get.datastore ====
Usage: get.datastores vmid

Show the list of datastores for this virtual machine.

==== Example output ====

 [root@himalaya scripts]# vmware-vim-cmd vmsvc/get.datastore 31168
 name                 himalaya-local-SAS.VMStorage
 url                  /vmfs/volumes/48c3a8cb-92b015b9-de33-003048670886
 capacity             293131517952
 freeSpace            60166242304
 accessible           1
 type                 VMFS 
 multipleHostAccess   &lt;unset&gt;


[[Category: Vimsh]]</text>
    <sha1>546f6e9b5a83d38a35b6e3b4cafa30fc3e5bb3e8</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vmsvc/get.disabledmethods</title>
  <ns>0</ns>
  <id>171</id>
  <revision>
    <id>762</id>
    <parentid>327</parentid>
    <timestamp>2009-01-05T23:38:41Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1108" xml:space="preserve">==== vimsh vmsvc/get.disabledmethods ====
Usage: get.disabledmethods vmid

Show the list of disabled methods on the virtual machine.

==== Example output ====

 [root@himalaya scripts]# vmware-vim-cmd vmsvc/get.disabledmethods 31168
 Disabled methods:
 (vmodl.MethodName) [
   "vim.ExtensibleManagedObject.setCustomValue",
   "vim.ManagedEntity.destroy",
   "vim.VirtualMachine.revertToCurrentSnapshot",
   "vim.VirtualMachine.removeAllSnapshots",
   "vim.VirtualMachine.upgradeVirtualHardware",
   "vim.VirtualMachine.powerOn",
   "vim.VirtualMachine.answer",
   "vim.VirtualMachine.customize",
   "vim.VirtualMachine.checkCustomizationSpec",
   "vim.VirtualMachine.migrate",
   "vim.VirtualMachine.relocate",
   "vim.VirtualMachine.clone",
   "vim.VirtualMachine.markAsTemplate",
   "vim.VirtualMachine.markAsVirtualMachine",
   "vim.VirtualMachine.unregister",
   "vim.VirtualMachine.resetGuestInformation",
   "vim.VirtualMachine.unmountToolsInstaller",
   "vim.VirtualMachine.upgradeTools",
   "vim.VirtualMachine.setScreenResolution",
   "vim.VirtualMachine.defragmentAllDisks"
 ]


[[Category: Vimsh]]</text>
    <sha1>9591905f50102eba2bab0025a52c0e460f104f13</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vmsvc/get.snapshotinfo</title>
  <ns>0</ns>
  <id>178</id>
  <revision>
    <id>763</id>
    <parentid>334</parentid>
    <timestamp>2009-01-05T23:41:48Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="941" xml:space="preserve">==== vimsh vmsvc/get.snapshotinfo ====
Usage: get.snapshotinfo vmid

Show the snapshot information for this virtual machine.

==== Example output =====

 [root@himalaya scripts]# vmware-vim-cmd vmsvc/get.snapshotinfo 60064
 (vim.vm.SnapshotInfo) {
   dynamicType = &lt;unset&gt;,
   currentSnapshot = 'vim.vm.Snapshot:/vmfs/volumes/48c3a8cb-92b015b9-de33-003048670886/WILLIAM-LC-18/WILLIAM-LC-18.vmx-snapshot-1',
   rootSnapshotList = (vim.vm.SnapshotTree) [
      (vim.vm.SnapshotTree) {
         dynamicType = &lt;unset&gt;,
         snapshot = 'vim.vm.Snapshot:/vmfs/volumes/48c3a8cb-92b015b9-de33-003048670886/WILLIAM-LC-18/WILLIAM-LC-18.vmx-snapshot-1',
         vm = 'vim.VirtualMachine:60064',
         name = "Linked_Cloned",
         description = "WILLIAM-LC-18_Cloned_from_UCSB-GAUCHOS",
         createTime = "2009-01-03T15:03:44.288377-08:00",
         state = "poweredOff",
         quiesced = false,
      }
   ],
 }


[[Category: Vimsh]]</text>
    <sha1>fe98f00d538df6400ecc7ad8b22737937d91b699</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vimsh: argtype</title>
  <ns>0</ns>
  <id>59</id>
  <revision>
    <id>764</id>
    <parentid>193</parentid>
    <timestamp>2009-01-05T23:44:14Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1959" xml:space="preserve">==== vimsh argtype command ====

Usage: argtype

Lists the registered argument types.

==== Example output ====

 [root@himalaya scripts]# vmware-vimsh -n -e "argtype"
 [2009-01-05 15:43:00.039 'App' 3076460672 info] Current working directory: /usr/lib/vmware/hostd
 [2009-01-05 15:43:00.040 'BaseLibs' 3076460672 info] HOSTINFO: Seeing Intel CPU, numCoresPerCPU 4 numThreadsPerCore 1.
 [2009-01-05 15:43:00.041 'BaseLibs' 3076460672 info] HOSTINFO: hyperthreading disabled, setting number of threads per core to 1.
 [2009-01-05 15:43:00.042 'BaseLibs' 3076460672 info] HOSTINFO: This machine has 2 physical CPUS, 8 total cores, and 8 logical CPUs.
 [2009-01-05 15:43:00.043 'BaseLibs' 3076460672 info] System libcrypto.so.0.9.7 library is older than our library (90701F &lt; 90709F)
 [2009-01-05 15:43:00.044 'App' 3076460672 info] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
 [2009-01-05 15:43:00.065 'BaseLibs' 9333680 warning] [Vmdb_Unset] Unsetting unknown path: /vmomi/
 account_user              host_mode_lock_type       scsi_disk_device
 advanced_option_key       lic_addons                scsi_lun
 argtype                   lic_editions              scsi_lun_type
 auth_privilege_id         lic_source                scsi_lun_vmhba
 auth_role_name            local_file_path           scsi_lun_vmtype
 bool                      managed_entity_moid       task_id
 console_virtual_nic       multipath_lun_policy      virtual_nic
 datastore                 multipath_path            virtual_switch
 debug_exception_variable  pci_device                vm_id
 diagnostic_storage_type   perfcount_query_moid      vm_message_choice_key
 diagnostic_type           perfcount_registry_path   vm_message_id
 fs_volume_label           physical_nic              vmfs_blocksize
 host_bus_adapter          physical_nic_mb           vmfs_majorversion
 host_bus_adapter_type     portgroup                 vmotion_vnic


[[Category: Vimsh]]</text>
    <sha1>5d4ba8f28a590dd73cd0003bc3a1f85bd57f983f</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vimsh</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>765</id>
    <parentid>547</parentid>
    <timestamp>2009-01-05T23:47:01Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3645" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help          puload
 internalsvc/  ?             csls          pinfo         puse
 proxysvc/     argtype       csuimport     pload         quit
 solo/         cls           echo          ploadpath     sleep
 vimsvc/       csimport      exit          pls           source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX (ESX3.5+), there's also a non interactive command line version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative: vimsh -n -e "command"

'''ESX 3.0.x+'''
  /usr/bin/vimsh -n -e "command"

'''ESX 3.5+''' 
 /usr/bin/vimsh -n -e "command"
 /usr/bin/vmware-vimsh "command"
 /usr/bin/vmware-vim-cmd "command"

'''ESXi 3.5+'''
 /bin/vim-cmd "command"


==== List of commands ====

Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki)

Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help and in many cases some example output of the commands.

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that vimsh will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>3116afe9489d3892aeccf9e366a5f211fa103b23</sha1>
  </revision>
  <revision>
    <id>792</id>
    <parentid>765</parentid>
    <timestamp>2009-01-30T10:58:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>correction on vmware-vimsh</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3694" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help          puload
 internalsvc/  ?             csls          pinfo         puse
 proxysvc/     argtype       csuimport     pload         quit
 solo/         cls           echo          ploadpath     sleep
 vimsvc/       csimport      exit          pls           source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX (ESX3.5+), there's also a non interactive command line version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative: vimsh -n -e "command"

'''ESX 3.0.x+'''
  /usr/bin/vimsh -n -e "command"

'''ESX 3.5+''' 
 /usr/bin/vimsh -n -e "command"
 /usr/bin/vmware-vim-cmd "command"

'''ESXi 3.5+'''
 /bin/vim-cmd "command"

/usr/bin/vimsh is a symbolic link to the file [[vmware-vimsh]] in the same folder.

==== List of commands ====

Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki)

Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help and in many cases some example output of the commands.

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that vimsh will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>12554c9342908b33a8df15b7e3a99440a3b0319d</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>766</id>
    <parentid>750</parentid>
    <timestamp>2009-01-06T00:38:46Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2250" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware RCLI?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== VI Perl Toolkit scripts ====

COMING SOON


==== RCLI scripts ====

COMING SOON</text>
    <sha1>375f0abd25d4ee1162ca0aab54b2ef0755241ca4</sha1>
  </revision>
  <revision>
    <id>771</id>
    <parentid>766</parentid>
    <timestamp>2009-01-10T00:22:03Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2219" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware RCLI?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

COMING SOON</text>
    <sha1>3b0cd25dc0be90229d37a343574575d12a1519d4</sha1>
  </revision>
  <revision>
    <id>773</id>
    <parentid>771</parentid>
    <timestamp>2009-01-13T16:51:15Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2250" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware RCLI?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]</text>
    <sha1>a18c309b140904058e032c6a399141284cfd3c0b</sha1>
  </revision>
  <revision>
    <id>778</id>
    <parentid>773</parentid>
    <timestamp>2009-01-21T16:09:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2304" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware RCLI?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

==== Perl scripts ====
[[Recover vmx from log file]]</text>
    <sha1>f18cc760e04590c470c2c40f93ba680fcf9a9690</sha1>
  </revision>
  <revision>
    <id>782</id>
    <parentid>778</parentid>
    <timestamp>2009-01-26T09:54:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2492" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

==== Perl scripts ====
[[Recover vmx from log file]]</text>
    <sha1>badd8eb3188a5ce1d8eaaa22c06b0c28e0dba591</sha1>
  </revision>
  <revision>
    <id>783</id>
    <parentid>782</parentid>
    <timestamp>2009-01-26T16:59:31Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2549" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

==== Perl scripts ====
[[Recover vmx from log file]]</text>
    <sha1>4e2c0e4d3c93f6bf3a572c95294d488c68bf9249</sha1>
  </revision>
  <revision>
    <id>785</id>
    <parentid>783</parentid>
    <timestamp>2009-01-27T23:47:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2571" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

==== Perl scripts ====
[[Recover vmx from log file]]</text>
    <sha1>b9e1c15b6c06192944a55fa80dc6482145b0c634</sha1>
  </revision>
  <revision>
    <id>797</id>
    <parentid>785</parentid>
    <timestamp>2009-02-01T00:41:35Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2603" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

==== Perl scripts ====
[[Recover vmx from log file]]</text>
    <sha1>1a4e6dbb31a145b7131ac69aaf81922960898c2e</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>VI-Toolkit:Community Portal</title>
  <ns>4</ns>
  <id>6</id>
  <revision>
    <id>767</id>
    <parentid>489</parentid>
    <timestamp>2009-01-09T10:47:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="987" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management console, a stripped down linux console which was could be used for automating and managing your virtual machines. As of ESX 3.5i this is no longer available and the future is to move away from the fat hypervisor. In order to manage your virtual machines in a similar way as before, we now have special virtual machines that come with management software pre-installed. VMware delivers 2 appliances for this, the [[VIMA]] and the [[RCLI]].</text>
    <sha1>f061b83dbe0358c6acb4b800a7fb5b74ca079fb8</sha1>
  </revision>
  <revision>
    <id>769</id>
    <parentid>767</parentid>
    <timestamp>2009-01-10T00:21:20Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1091" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and VI Perl Toolkit to aide in managing your VI infrastructure.</text>
    <sha1>652124e6e4a75f69b92dcaa097c361c2ffa2dafd</sha1>
  </revision>
  <revision>
    <id>770</id>
    <parentid>769</parentid>
    <timestamp>2009-01-10T00:21:39Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1095" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and [[VI Perl Toolkit]] to aide in managing your VI infrastructure.</text>
    <sha1>a8ea2aa466942ddd9df992923bfccf6a97eb1e31</sha1>
  </revision>
  <revision>
    <id>772</id>
    <parentid>770</parentid>
    <timestamp>2009-01-10T00:22:41Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1102" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and VMware [[VI Perl Toolkit]] to aide in managing your VI infrastructure.</text>
    <sha1>137ce26b53adcdacc17891fc85487f0bb2c9d84a</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Virtualisation technical articles</title>
  <ns>0</ns>
  <id>412</id>
  <revision>
    <id>768</id>
    <timestamp>2009-01-09T11:11:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>virtual technical hyperlinks</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="858" xml:space="preserve">This page contains links to technical articles about virtualisation technology.
It's a sort of fancy bookmark of what I consider interesting reading as a programmer... this is not likely to be interesting for everyone ;)

* [http://www.codeproject.com/KB/debug/cdbntsd6.aspx Navigating the kernel debugger]
This tutorial covers a few of the basic features of the kernel debugger and has some tips on getting used to using it. 

* [http://www.ddj.com/cpp/184402033 Sharing memory with the virtual machine]
Tricks on sharing data between guest OS instances and the host. 

* [http://www.codeplex.com/visa/Wiki/View.aspx?title=English%20version&amp;referringTitle=Home Virtualisation Instruction Set Architecture]
MIPS R3000 processor model, available at ArchC was extended to offer virtualisation support, adding instructions and structures inspired by Intel VT-x.</text>
    <sha1>8b457950cc0dd4d483c6d8484fb32f0638d29b68</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Free VM Clone utility for ESX and ESXi</title>
  <ns>0</ns>
  <id>413</id>
  <revision>
    <id>774</id>
    <timestamp>2009-01-13T16:54:26Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoClone.sh ghettoClone.sh]  '''Requires''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmregister.pl my-vmregister.pl...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="873" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoClone.sh ghettoClone.sh]

'''Requires''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmregister.pl my-vmregister.pl]

'''Compatible with''': ESX/ESXi 3.5u2+

Please find more details located at: http://communities.vmware.com/docs/DOC-9321

This script provide administrators with a means to automatically clone and deploy a large subset of virtual machines into a virtual environment without requiring tedious Service Console work or Virtual Center. Furthermore, for ease of accessibility, the free VMware VIMA appliance was chosen as the central launch point for the cloning process. ghettoClone.sh is executed from within VIMA and is compatible with both ESX and ESXi 3.5u2+. It accepts a single source virtual machine along with inputted configuration parameters to tailor cloned virtual machines.</text>
    <sha1>ad79cba2a2eb1a89ace9f050cf697e9648540bda</sha1>
  </revision>
  <revision>
    <id>775</id>
    <parentid>774</parentid>
    <timestamp>2009-01-13T16:54:38Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="879" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoClone.sh ghettoClone.sh]

'''Requires''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmregister.pl my-vmregister.pl]

'''Compatible with''': ESX/ESXi 3.5u2+

Please find more details located at: http://communities.vmware.com/docs/DOC-9321

This script provide administrators with a means to automatically clone and deploy a large subset of virtual machines into a virtual environment without requiring tedious Service Console work or Virtual Center. Furthermore, for ease of accessibility, the free VMware VIMA appliance was chosen as the central launch point for the cloning process. '''ghettoClone.sh''' is executed from within VIMA and is compatible with both ESX and ESXi 3.5u2+. It accepts a single source virtual machine along with inputted configuration parameters to tailor cloned virtual machines.</text>
    <sha1>12764d6c58c895634133c4af855d876ad313e9ed</sha1>
  </revision>
  <revision>
    <id>776</id>
    <parentid>775</parentid>
    <timestamp>2009-01-13T16:54:59Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="927" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoClone.sh ghettoClone.sh]

'''Requires''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmregister.pl my-vmregister.pl]

'''Compatible with''': ESX/ESXi 3.5u2+

Please find more details located at: http://communities.vmware.com/docs/DOC-9321

This script provide administrators with a means to automatically clone and deploy a large subset of virtual machines into a virtual environment without requiring tedious Service Console work or Virtual Center. Furthermore, for ease of accessibility, the free [http://www.vmware.com/support/developer/vima/ VMware VIMA] appliance was chosen as the central launch point for the cloning process. '''ghettoClone.sh''' is executed from within VIMA and is compatible with both ESX and ESXi 3.5u2+. It accepts a single source virtual machine along with inputted configuration parameters to tailor cloned virtual machines.</text>
    <sha1>ef0c4769d9c1979a094886b5ae8c8b471a27d094</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Hostsvc/net/vswitch setpolicy</title>
  <ns>0</ns>
  <id>136</id>
  <revision>
    <id>777</id>
    <parentid>285</parentid>
    <timestamp>2009-01-15T10:29:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added example</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2131" xml:space="preserve">==== vimsh hostsvc/net/vswitch_setpolicy ====

Usage: vswitch_setpolicy [OPTIONS] vswitch

Changes the policies of a virtual switch.

Options:
   --securepolicy-promisc=bool
       Allow promiscuous mode.
 
   --securepolicy-macchange=bool
       Allow MAC address to be changed.
 
   --securepolicy-forgedxmit=bool
       Allow forged transmits.
 
   --shapingpolicy-enabled=bool
       Enabled shaper.
 
   --shapingpolicy-average-bandwidth=int
       Average bandwidth.
 
   --shapingpolicy-peak-bandwidth=int
       Peak bandwidth.
 
   --shapingpolicy-burst-size=int
       Burst size.
 
   --nicorderpolicy-active=vmnic_list
       List of active NICs.
 
   --nicorderpolicy-standby=vmnic_list
       Order in which failover should occur.
 
   --failurecriteria-check-speed=failurecriteria-check-speed
       Detecting failover using link speed check
 
   --failurecriteria-speed=int
       The speed for link speed check method
 
   --failurecriteria-check-duplex=bool
       Detecting failover using link duplex check
 
   --failurecriteria-duplex=bool
       The duplexity for link duplex check method
 
   --failurecriteria-check-error=bool
       Detecting failover using link error percentage
 
   --failurecriteria-error=int
       The error percentage for link error percentage check method
 
   --failurecriteria-check-beacon=bool
       Detecting failover using the beacon
 
   --nicteaming-policy=nicteaming-policy
       Nic-Teaming policy.
 
   --nicteaming-reverse-policy=bool
       Apply the teaming policy to inbound frames as well.
 
   --nicteaming-notify-switch=bool
       Notify switches when detects a link failure.
 
   --nicteaming-rollingorder=bool
       Whether or not to use rolling failover.
 
   --offloadcaps-csum-offload=bool
       Checksum offload
 
   --offloadcaps-tcp-segment=bool
       TCP segment offload
 
   --offloadcaps-zerocopy-xmit=bool
       Scatter gather

==== Example ====
This works on ESX 3.5 U3 [http://communities.vmware.com/message/1144345 forum reference]

 vmware-vim-cmd /hostsvc/net/vswitch_setpolicy --failurecriteria-check-beacon 1 vSwitch0


[[Category: Vimsh]]</text>
    <sha1>5e77b2ccf697f2a6876bf57ac3930442ec735ec3</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Recover vmx from log file</title>
  <ns>0</ns>
  <id>414</id>
  <revision>
    <id>779</id>
    <timestamp>2009-01-21T16:46:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: === Recover vmx from log file === On the VMware community forums, [http://communities.vmware.com/people/etung|Eric Tung] has devised a little jewel of code that automates recreating a vmx ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1883" xml:space="preserve">=== Recover vmx from log file ===
On the VMware community forums, [http://communities.vmware.com/people/etung|Eric Tung] has devised a little jewel of code that automates recreating a vmx file from a recent vmware.log file.

This is possible as on every boot of a virtual machine, the vmware.log gets a copy from your virtual hardware settings written out into the vmware.log logfile along with some extra information such as the date and time this VM was run.
The script extracts the relevant part for you and eliminates the risk of making a typo while doing this by hand.
It is written in perl, just a few lines long and shows the true power of what a bit of perl can do for you :)

==== vmxRecover.pl code ====
 #!/usr/bin/perl
 use strict;
 use warnings;  

 if ($#ARGV != 0) {
    print "Recovers .vmx files from .log files. Usage:\n";
    print "$0 logfile &gt; vmxfile\n\n";
    exit;
 }
 
 while (&lt;&gt;) {
    # Scan until we reach the config section
    if (/: vmx\| DICT --- CONFIGURATION/) { last; }
 }
 
 while (&lt;&gt;) {
    if (/: vmx\| DICT --- \S/) { last; } # Keep going until the next section
    s/^.*: vmx\| DICT\s*//;    # Strip off the leading timestamp and other stuff
    s/\r//;                    # Get rid of any \r's that may have somehow snuck in
    s/([^=]*=) (.*)/$1 "$2"/;  # Quote the value
    print;
 }

==== Usage ====
Say you want to recreate a the virtual hardware configuration for a VMware virtual machine "Windows XP.vmx" then you'd call it like this:
 vmxRecover.pl vmware.log &gt; "Windows XP.vmx"


==== External links ====
* The original post [http://communities.vmware.com/message/1029971#1029971 Not a Valid Virtual Machine Configuration...]
* The script [http://communities.vmware.com/servlet/JiveServlet/download/1029971-12847/vmxRecover.pl.zip?tstart=0&amp;start=15 vmxRecover.pl.zip]
* Eric's site http://www.koiproductions.com

[[Category: Perl]]</text>
    <sha1>31132aa441f4bfd440a95afc9055648c6000f718</sha1>
  </revision>
  <revision>
    <id>780</id>
    <parentid>779</parentid>
    <timestamp>2009-01-21T16:46:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1884" xml:space="preserve">=== Recover vmx from log file ===
On the VMware community forums, [http://communities.vmware.com/people/etung|Eric Tung] has devised a little jewel of code that automates recreating a vmx file from a recent vmware.log file.

This is possible as on every boot of a virtual machine, the vmware.log gets a copy from your virtual hardware settings written out into the vmware.log logfile along with some extra information such as the date and time this VM was run.
The script extracts the relevant part for you and eliminates the risk of making a typo while doing this by hand.
It is written in perl, just a few lines long and shows the true power of what a bit of perl can do for you :)

==== vmxRecover.pl code ====
 #!/usr/bin/perl
 use strict;
 use warnings;  
 
 if ($#ARGV != 0) {
    print "Recovers .vmx files from .log files. Usage:\n";
    print "$0 logfile &gt; vmxfile\n\n";
    exit;
 }
 
 while (&lt;&gt;) {
    # Scan until we reach the config section
    if (/: vmx\| DICT --- CONFIGURATION/) { last; }
 }
 
 while (&lt;&gt;) {
    if (/: vmx\| DICT --- \S/) { last; } # Keep going until the next section
    s/^.*: vmx\| DICT\s*//;    # Strip off the leading timestamp and other stuff
    s/\r//;                    # Get rid of any \r's that may have somehow snuck in
    s/([^=]*=) (.*)/$1 "$2"/;  # Quote the value
    print;
 }

==== Usage ====
Say you want to recreate a the virtual hardware configuration for a VMware virtual machine "Windows XP.vmx" then you'd call it like this:
 vmxRecover.pl vmware.log &gt; "Windows XP.vmx"


==== External links ====
* The original post [http://communities.vmware.com/message/1029971#1029971 Not a Valid Virtual Machine Configuration...]
* The script [http://communities.vmware.com/servlet/JiveServlet/download/1029971-12847/vmxRecover.pl.zip?tstart=0&amp;start=15 vmxRecover.pl.zip]
* Eric's site http://www.koiproductions.com

[[Category: Perl]]</text>
    <sha1>1f2c0f0a1413a4cda32dab330e7e997d57f6880f</sha1>
  </revision>
  <revision>
    <id>781</id>
    <parentid>780</parentid>
    <timestamp>2009-01-21T16:52:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1884" xml:space="preserve">=== Recover vmx from log file ===
On the VMware community forums, [http://communities.vmware.com/people/etung Eric Tung] has devised a little jewel of code that automates recreating a vmx file from a recent vmware.log file.

This is possible as on every boot of a virtual machine, the vmware.log gets a copy from your virtual hardware settings written out into the vmware.log logfile along with some extra information such as the date and time this VM was run.
The script extracts the relevant part for you and eliminates the risk of making a typo while doing this by hand.
It is written in perl, just a few lines long and shows the true power of what a bit of perl can do for you :)

==== vmxRecover.pl code ====
 #!/usr/bin/perl
 use strict;
 use warnings;  
 
 if ($#ARGV != 0) {
    print "Recovers .vmx files from .log files. Usage:\n";
    print "$0 logfile &gt; vmxfile\n\n";
    exit;
 }
 
 while (&lt;&gt;) {
    # Scan until we reach the config section
    if (/: vmx\| DICT --- CONFIGURATION/) { last; }
 }
 
 while (&lt;&gt;) {
    if (/: vmx\| DICT --- \S/) { last; } # Keep going until the next section
    s/^.*: vmx\| DICT\s*//;    # Strip off the leading timestamp and other stuff
    s/\r//;                    # Get rid of any \r's that may have somehow snuck in
    s/([^=]*=) (.*)/$1 "$2"/;  # Quote the value
    print;
 }

==== Usage ====
Say you want to recreate a the virtual hardware configuration for a VMware virtual machine "Windows XP.vmx" then you'd call it like this:
 vmxRecover.pl vmware.log &gt; "Windows XP.vmx"


==== External links ====
* The original post [http://communities.vmware.com/message/1029971#1029971 Not a Valid Virtual Machine Configuration...]
* The script [http://communities.vmware.com/servlet/JiveServlet/download/1029971-12847/vmxRecover.pl.zip?tstart=0&amp;start=15 vmxRecover.pl.zip]
* Eric's site http://www.koiproductions.com

[[Category: Perl]]</text>
    <sha1>b606b443c06d8817005da16d80e7d5fd25d4e02d</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>"Quick" migration utility for VM(s) on ESX and ESXi</title>
  <ns>0</ns>
  <id>415</id>
  <revision>
    <id>784</id>
    <timestamp>2009-01-26T17:01:21Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoQuickMigrate.sh ghettoQuickMigrate.sh]  '''Compatible with''': ESX/ESXi 3.5u2+  Please find more details located at: ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1168" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoQuickMigrate.sh ghettoQuickMigrate.sh]

'''Compatible with''': ESX/ESXi 3.5u2+

Please find more details located at: http://communities.vmware.com/docs/DOC-9400

This script provides administrators running the free version of ESXi on several hosts with the capability to perform Hyper-V-like "'''quick'''" migrations of virtual machines residing on shared storage between the hosts. [http://www.vmware.com/support/developer/vima/ VMware's VIMA] virtual appliance was chosen as the central launch point for the quick migration process. '''ghettoQuickMigration.sh''' is executed from within VIMA and is compatible with ESXi 3.5u2+.

This script follows similarly to the Hyper-V Quick Migration process with the exception of replacing the disk resource swap with a virtual machine unregister/register command on the source and target hosts respectively. The state (powered ON/Suspended/OFF) of the virtual machine designated for migration is preserved through the entire process. Online virtual machines undergoing this migration will experience a temporary pause due to the suspend and resume steps.</text>
    <sha1>42a96ba863457e651959ace4f28f8048e8226db6</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>ESX CLI Commands</title>
  <ns>0</ns>
  <id>416</id>
  <revision>
    <id>786</id>
    <timestamp>2009-01-27T23:48:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== ESX CLI Commands ====  Virtual Infrastructure ESX has a service console which can be used to management purposes. This is a light weight linux based (RHEL3) Virtual Machine which has ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1959" xml:space="preserve">==== ESX CLI Commands ====

Virtual Infrastructure ESX has a service console which can be used to management purposes.
This is a light weight linux based (RHEL3) Virtual Machine which has special privileges that can be used in order to manage your host and Virtual Machines.
Down here we will be trying to document the available commands that you can use on this service console from the so called Command Line Interface (CLI).

In ESXi (3.x) the service console has been removed from the host and there's only a remote alternative available, which is called the [[RCLI]].
The chapter here only contains the documentation for the full blown version not the RCLI.

 [[esxcfg-advcfg]]      
 [[esxcfg-auth]]        
 [[esxcfg-boot]]        
 [[esxcfg-configcheck]]
 [[esxcfg-dumppart]]   
 [[esxcfg-firewall]]   
 [[esxcfg-hwiscsi]]    
 [[esxcfg-info]]     
 [[esxcfg-init]]
 [[esxcfg-linuxnet]]
 [[esxcfg-module]]
 [[esxcfg-mpath]]
 [[esxcfg-nas]]
 [[esxcfg-nics]]
 [[esxcfg-pciid]]
 [[esxcfg-rescan]]
 [[esxcfg-resgrp]]
 [[esxcfg-route]]
 [[esxcfg-swiscsi]]
 [[esxcfg-upgrade]]
 [[esxcfg-vmhbadevs]]
 [[esxcfg-vmknic]]
 [[esxcfg-vswif]]
 [[esxcfg-vswitch]]
 [[esxupdate]]
 [[vcbExport]]
 [[vcbMounter]]
 [[vcbResAll]]
 [[vcbRestore]]
 [[vcbSnapAll]]
 [[vcbSnapshot]]
 [[vcbUtil]]
 [[vcbVmName]]
 [[vdf]]
 [[vmfsqhtool]]
 [[vmfsqueuetool]]
 [[vmkchdev]]
 [[vmkdump]]
 [[vmkerrcode]]
 [[vmkfstools]]
 [[vmkiscsid]]
 [[vmkiscsi-device]]
 [[vmkiscsi-ls]]
 [[vmkiscsi-tool]]
 [[vmkiscsi-util]]
 [[vmkloader]]
 [[vmkload_mod]]
 [[vmklogger]]
 [[vmkpcidivy]]
 [[vmkping]]
 [[vmkuptime.pl]]
 [[vmres.pl]]
 [[vmsnap_all]]
 [[vmsnap.pl]]
 [[vmstat]]
 [[vm-support]]
 [[vmware]]
 [[vmware-authd]]
 [[vmware-autopoweron.sh]]
 [[vmware-cmd]]
 [[vmware-configcheck]]
 [[vmware-config.pl]]
 [[vmware-hostd]]
 [[vmware-hostd-support]]
 [[vmware-mkinitrd]]
 [[vmware-vim-cmd]]         
 [[vmware-vimdump]]         
 [[vmware-vimsh]]
 [[vmware-watchdog]]
 [[vmware-webAccess]]</text>
    <sha1>f2b39aaab34bbac7bfa1f2ca110a08bb2aabc03f</sha1>
  </revision>
  <revision>
    <id>788</id>
    <parentid>786</parentid>
    <timestamp>2009-01-27T23:54:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Forgot categories :)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1996" xml:space="preserve">==== ESX CLI Commands ====

Virtual Infrastructure ESX has a service console which can be used to management purposes.
This is a light weight linux based (RHEL3) Virtual Machine which has special privileges that can be used in order to manage your host and Virtual Machines.
Down here we will be trying to document the available commands that you can use on this service console from the so called Command Line Interface (CLI).

In ESXi (3.x) the service console has been removed from the host and there's only a remote alternative available, which is called the [[RCLI]].
The chapter here only contains the documentation for the full blown version not the RCLI.

 [[esxcfg-advcfg]]      
 [[esxcfg-auth]]        
 [[esxcfg-boot]]        
 [[esxcfg-configcheck]]
 [[esxcfg-dumppart]]   
 [[esxcfg-firewall]]   
 [[esxcfg-hwiscsi]]    
 [[esxcfg-info]]     
 [[esxcfg-init]]
 [[esxcfg-linuxnet]]
 [[esxcfg-module]]
 [[esxcfg-mpath]]
 [[esxcfg-nas]]
 [[esxcfg-nics]]
 [[esxcfg-pciid]]
 [[esxcfg-rescan]]
 [[esxcfg-resgrp]]
 [[esxcfg-route]]
 [[esxcfg-swiscsi]]
 [[esxcfg-upgrade]]
 [[esxcfg-vmhbadevs]]
 [[esxcfg-vmknic]]
 [[esxcfg-vswif]]
 [[esxcfg-vswitch]]
 [[esxupdate]]
 [[vcbExport]]
 [[vcbMounter]]
 [[vcbResAll]]
 [[vcbRestore]]
 [[vcbSnapAll]]
 [[vcbSnapshot]]
 [[vcbUtil]]
 [[vcbVmName]]
 [[vdf]]
 [[vmfsqhtool]]
 [[vmfsqueuetool]]
 [[vmkchdev]]
 [[vmkdump]]
 [[vmkerrcode]]
 [[vmkfstools]]
 [[vmkiscsid]]
 [[vmkiscsi-device]]
 [[vmkiscsi-ls]]
 [[vmkiscsi-tool]]
 [[vmkiscsi-util]]
 [[vmkloader]]
 [[vmkload_mod]]
 [[vmklogger]]
 [[vmkpcidivy]]
 [[vmkping]]
 [[vmkuptime.pl]]
 [[vmres.pl]]
 [[vmsnap_all]]
 [[vmsnap.pl]]
 [[vmstat]]
 [[vm-support]]
 [[vmware]]
 [[vmware-authd]]
 [[vmware-autopoweron.sh]]
 [[vmware-cmd]]
 [[vmware-configcheck]]
 [[vmware-config.pl]]
 [[vmware-hostd]]
 [[vmware-hostd-support]]
 [[vmware-mkinitrd]]
 [[vmware-vim-cmd]]         
 [[vmware-vimdump]]         
 [[vmware-vimsh]]
 [[vmware-watchdog]]
 [[vmware-webAccess]]

[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>6eb35765c4d5348871dfcac7663800a0ac56690d</sha1>
  </revision>
  <revision>
    <id>790</id>
    <parentid>788</parentid>
    <timestamp>2009-01-30T10:24:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2324" xml:space="preserve">==== ESX CLI Commands ====

Virtual Infrastructure ESX has a service console which can be used to management purposes.
This is a light weight linux based (RHEL3) Virtual Machine which has special privileges that can be used in order to manage your host and Virtual Machines.
Down here we will be trying to document the available commands that you can use on this service console from the so called Command Line Interface (CLI).

In ESXi (3.x) the service console has been removed from the host and there's only a remote alternative available, which is called the [[RCLI]].
The chapter here only contains the documentation for the full blown version not the RCLI.

Any changes made to the configuration of the host will not be seen by vCenter Server or the host itself until you restart the vmware-hostd daemon. By restarting this daemon, the configuration file /etc/vmware/esx.conf will be re-read.

 service mgmt-vmware restart

will restart this daemon.


==== The available commands ====

 [[esxcfg-advcfg]]      
 [[esxcfg-auth]]        
 [[esxcfg-boot]]        
 [[esxcfg-configcheck]]
 [[esxcfg-dumppart]]   
 [[esxcfg-firewall]]   
 [[esxcfg-hwiscsi]]    
 [[esxcfg-info]]     
 [[esxcfg-init]]
 [[esxcfg-linuxnet]]
 [[esxcfg-module]]
 [[esxcfg-mpath]]
 [[esxcfg-nas]]
 [[esxcfg-nics]]
 [[esxcfg-pciid]]
 [[esxcfg-rescan]]
 [[esxcfg-resgrp]]
 [[esxcfg-route]]
 [[esxcfg-swiscsi]]
 [[esxcfg-upgrade]]
 [[esxcfg-vmhbadevs]]
 [[esxcfg-vmknic]]
 [[esxcfg-vswif]]
 [[esxcfg-vswitch]]
 [[esxupdate]]
 [[vcbExport]]
 [[vcbMounter]]
 [[vcbResAll]]
 [[vcbRestore]]
 [[vcbSnapAll]]
 [[vcbSnapshot]]
 [[vcbUtil]]
 [[vcbVmName]]
 [[vdf]]
 [[vmfsqhtool]]
 [[vmfsqueuetool]]
 [[vmkchdev]]
 [[vmkdump]]
 [[vmkerrcode]]
 [[vmkfstools]]
 [[vmkiscsid]]
 [[vmkiscsi-device]]
 [[vmkiscsi-ls]]
 [[vmkiscsi-tool]]
 [[vmkiscsi-util]]
 [[vmkloader]]
 [[vmkload_mod]]
 [[vmklogger]]
 [[vmkpcidivy]]
 [[vmkping]]
 [[vmkuptime.pl]]
 [[vmres.pl]]
 [[vmsnap_all]]
 [[vmsnap.pl]]
 [[vmstat]]
 [[vm-support]]
 [[vmware]]
 [[vmware-authd]]
 [[vmware-autopoweron.sh]]
 [[vmware-cmd]]
 [[vmware-configcheck]]
 [[vmware-config.pl]]
 [[vmware-hostd]]
 [[vmware-hostd-support]]
 [[vmware-mkinitrd]]
 [[vmware-vim-cmd]]         
 [[vmware-vimdump]]         
 [[vmware-vimsh]]
 [[vmware-watchdog]]
 [[vmware-webAccess]]

[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>911e2b90516e4a9afc618b31738f8fbcae71f1c7</sha1>
  </revision>
  <revision>
    <id>791</id>
    <parentid>790</parentid>
    <timestamp>2009-01-30T10:54:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>do'h forgot vimsh</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2335" xml:space="preserve">==== ESX CLI Commands ====

Virtual Infrastructure ESX has a service console which can be used to management purposes.
This is a light weight linux based (RHEL3) Virtual Machine which has special privileges that can be used in order to manage your host and Virtual Machines.
Down here we will be trying to document the available commands that you can use on this service console from the so called Command Line Interface (CLI).

In ESXi (3.x) the service console has been removed from the host and there's only a remote alternative available, which is called the [[RCLI]].
The chapter here only contains the documentation for the full blown version not the RCLI.

Any changes made to the configuration of the host will not be seen by vCenter Server or the host itself until you restart the vmware-hostd daemon. By restarting this daemon, the configuration file /etc/vmware/esx.conf will be re-read.

 service mgmt-vmware restart

will restart this daemon.


==== The available commands ====

 [[esxcfg-advcfg]]      
 [[esxcfg-auth]]        
 [[esxcfg-boot]]        
 [[esxcfg-configcheck]]
 [[esxcfg-dumppart]]   
 [[esxcfg-firewall]]   
 [[esxcfg-hwiscsi]]    
 [[esxcfg-info]]     
 [[esxcfg-init]]
 [[esxcfg-linuxnet]]
 [[esxcfg-module]]
 [[esxcfg-mpath]]
 [[esxcfg-nas]]
 [[esxcfg-nics]]
 [[esxcfg-pciid]]
 [[esxcfg-rescan]]
 [[esxcfg-resgrp]]
 [[esxcfg-route]]
 [[esxcfg-swiscsi]]
 [[esxcfg-upgrade]]
 [[esxcfg-vmhbadevs]]
 [[esxcfg-vmknic]]
 [[esxcfg-vswif]]
 [[esxcfg-vswitch]]
 [[esxupdate]]
 [[vcbExport]]
 [[vcbMounter]]
 [[vcbResAll]]
 [[vcbRestore]]
 [[vcbSnapAll]]
 [[vcbSnapshot]]
 [[vcbUtil]]
 [[vcbVmName]]
 [[vdf]]
 [[vimsh]]
 [[vmfsqhtool]]
 [[vmfsqueuetool]]
 [[vmkchdev]]
 [[vmkdump]]
 [[vmkerrcode]]
 [[vmkfstools]]
 [[vmkiscsid]]
 [[vmkiscsi-device]]
 [[vmkiscsi-ls]]
 [[vmkiscsi-tool]]
 [[vmkiscsi-util]]
 [[vmkloader]]
 [[vmkload_mod]]
 [[vmklogger]]
 [[vmkpcidivy]]
 [[vmkping]]
 [[vmkuptime.pl]]
 [[vmres.pl]]
 [[vmsnap_all]]
 [[vmsnap.pl]]
 [[vmstat]]
 [[vm-support]]
 [[vmware]]
 [[vmware-authd]]
 [[vmware-autopoweron.sh]]
 [[vmware-cmd]]
 [[vmware-configcheck]]
 [[vmware-config.pl]]
 [[vmware-hostd]]
 [[vmware-hostd-support]]
 [[vmware-mkinitrd]]
 [[vmware-vim-cmd]]         
 [[vmware-vimdump]]         
 [[vmware-vimsh]]
 [[vmware-watchdog]]
 [[vmware-webAccess]]

[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>f5ad443ddf9706b129f63c58f006b588d5062d58</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vmkerrcode</title>
  <ns>0</ns>
  <id>417</id>
  <revision>
    <id>787</id>
    <timestamp>2009-01-27T23:49:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== vmkerrcode ==== Usage:   vmkerrcode [-l] [error code (hex or decimal)]     -l list all error codes  This can be used in order to decode the error  ==== Example output ====  # vmkerrco...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24816" xml:space="preserve">==== vmkerrcode ====
Usage: 
 vmkerrcode [-l] [error code (hex or decimal)]
    -l list all error codes

This can be used in order to decode the error

==== Example output ====
 # vmkerrcode -l
 
 VMK_ReturnStatus table for VMware ESX Server, Build #130756
 Name                             Dec         Hex          errno equiv    Description                                                 
 -------------------------------------------------------------------------------
 VMK_OK                           0           0            OK            Success
 VMK_FAILURE                      195887105   0xbad0001    EINVAL        Failure
 VMK_WOULD_BLOCK                  195887106   0xbad0002    EAGAIN        Would block
 VMK_NOT_FOUND                    195887107   0xbad0003    ENOENT        Not found
 VMK_BUSY                         195887108   0xbad0004    EBUSY         Busy
 VMK_EXISTS                       195887109   0xbad0005    EEXIST        Already exists
 VMK_LIMIT_EXCEEDED               195887110   0xbad0006    EFBIG         Limit exceeded
 VMK_BAD_PARAM                    195887111   0xbad0007    EINVAL        Bad parameter
 VMK_METADATA_READ_ERROR          195887112   0xbad0008    EIO           Metadata read error
 VMK_METADATA_WRITE_ERROR         195887113   0xbad0009    EIO           Metadata write error
 VMK_IO_ERROR                     195887114   0xbad000a    EIO           I/O error
 VMK_READ_ERROR                   195887115   0xbad000b    EIO           Read error
 VMK_WRITE_ERROR                  195887116   0xbad000c    EIO           Write error
 VMK_INVALID_NAME                 195887117   0xbad000d    ENAMETOOLONG  Invalid name
 VMK_INVALID_HANDLE               195887118   0xbad000e    EBADF         Invalid handle
 VMK_INVALID_ADAPTER              195887119   0xbad000f    ENODEV        No such SCSI adapter
 VMK_INVALID_TARGET               195887120   0xbad0010    ENODEV        No such target on adapter
 VMK_INVALID_PARTITION            195887121   0xbad0011    ENXIO         No such partition on target
 VMK_INVALID_FS                   195887122   0xbad0012    ENXIO         No filesystem on the device
 VMK_INVALID_MEMMAP               195887123   0xbad0013    EFAULT        Memory map mismatch
 VMK_NO_MEMORY                    195887124   0xbad0014    ENOMEM        Out of memory
 VMK_NO_MEMORY_RETRY              195887125   0xbad0015    ENOMEM        Out of memory (ok to retry)
 VMK_NO_RESOURCES                 195887126   0xbad0016    ENOMEM        Out of resources
 VMK_NO_FREE_HANDLES              195887127   0xbad0017    EMFILE        No free handles
 VMK_NUM_HANDLES_EXCEEDED         195887128   0xbad0018    ENFILE        Exceeded maximum number of allowed handles
 VMK_DEPRECATED_NO_FREE_PTR_BLOCKS195887129   0xbad0019    ENOSPC        No free pointer blocks (deprecated)
 VMK_DEPRECATED_NO_FREE_DATA_BLOCKS195887130   0xbad001a    ENOSPC        No free data blocks (deprecated)
 VMK_CORRUPT_REDOLOG              195887131   0xbad001b    EBADF         Corrupt RedoLog
 VMK_STATUS_PENDING               195887132   0xbad001c    EAGAIN        Status pending
 VMK_STATUS_FREE                  195887133   0xbad001d    EAGAIN        Status free
 VMK_UNSUPPORTED_CPU              195887134   0xbad001e    ENODEV        Unsupported CPU
 VMK_NOT_SUPPORTED                195887135   0xbad001f    ENOSYS        Not supported
 VMK_TIMEOUT                      195887136   0xbad0020    ETIMEDOUT     Timeout
 VMK_READ_ONLY                    195887137   0xbad0021    EROFS         Read only
 VMK_RESERVATION_CONFLICT         195887138   0xbad0022    EAGAIN        SCSI reservation conflict
 VMK_FS_LOCKED                    195887139   0xbad0023    EADDRINUSE    File system locked
 VMK_NOT_ENOUGH_SLOTS             195887140   0xbad0024    ENFILE        Out of slots
 VMK_INVALID_ADDRESS              195887141   0xbad0025    EFAULT        Invalid address
 VMK_NOT_SHARED                   195887142   0xbad0026    ENOMEM        Not shared
 VMK_SHARED                       195887143   0xbad0027    ENOMEM        Page is shared
 VMK_KSEG_PAIR_FLUSHED            195887144   0xbad0028    ENOMEM        Kseg pair flushed
 VMK_MAX_ASYNCIO_PENDING          195887145   0xbad0029    ENOMEM        Max async I/O requests pending
 VMK_VERSION_MISMATCH_MINOR       195887146   0xbad002a    ENOSYS        Minor version mismatch
 VMK_VERSION_MISMATCH_MAJOR       195887147   0xbad002b    ENOSYS        Major version mismatch
 VMK_IS_CONNECTED                 195887148   0xbad002c    EINVAL        Already connected
 VMK_IS_DISCONNECTED              195887149   0xbad002d    ENOTCONN      Already disconnected
 VMK_IS_ENABLED                   195887150   0xbad002e    EINVAL        Already enabled
 VMK_IS_DISABLED                  195887151   0xbad002f    EINVAL        Already disabled
 VMK_NOT_INITIALIZED              195887152   0xbad0030    EINVAL        Not initialized
 VMK_WAIT_INTERRUPTED             195887153   0xbad0031    EINTR         Wait interrupted
 VMK_NAME_TOO_LONG                195887154   0xbad0032    ENAMETOOLONG  Name too long
 VMK_MISSING_FS_PES               195887155   0xbad0033    ENOTDIR       VMFS volume missing physical extents
 VMK_NICTEAMING_VALID_MASTER      195887156   0xbad0034    EINVAL        NIC teaming master valid
 VMK_NICTEAMING_SLAVE             195887157   0xbad0035    EEXIST        NIC teaming slave
 VMK_NICTEAMING_REGULAR_VMNIC     195887158   0xbad0036    EINVAL        NIC teaming regular VMNIC
 VMK_ABORT_NOT_RUNNING            195887159   0xbad0037    ECANCELED     Abort not running
 VMK_NOT_READY                    195887160   0xbad0038    EIO           Not ready
 VMK_CHECKSUM_MISMATCH            195887161   0xbad0039    EIO           Checksum mismatch
 VMK_VLAN_NO_HW_ACCEL             195887162   0xbad003a    EINVAL        VLan HW Acceleration not supported
 VMK_NO_VLAN_SUPPORT              195887163   0xbad003b    EOPNOTSUPP    VLan is not supported in vmkernel
 VMK_NOT_VLAN_HANDLE              195887164   0xbad003c    EINVAL        Not a VLan handle
 VMK_BAD_VLANID                   195887165   0xbad003d    EBADF         Couldn't retrieve VLan id
 VMK_MIG_PROTO_ERROR              195887166   0xbad003e    EINVAL        Migration protocol error
 VMK_NO_CONNECT                   195887167   0xbad003f    EIO           No connection
 VMK_SEGMENT_OVERLAP              195887168   0xbad0040    EINVAL        Segment overlap
 VMK_BAD_MPS                      195887169   0xbad0041    EIO           Error parsing MPS Table
 VMK_BAD_ACPI                     195887170   0xbad0042    EIO           Error parsing ACPI Table
 VMK_RESUME_ERROR                 195887171   0xbad0043    EIO           Failed to resume VM
 VMK_NO_ADDRESS_SPACE             195887172   0xbad0044    ENOMEM        Insufficient address space for operation
 VMK_BAD_ADDR_RANGE               195887173   0xbad0045    EINVAL        Bad address range
 VMK_ENETDOWN                     195887174   0xbad0046    ENETDOWN      Network is down
 VMK_ENETUNREACH                  195887175   0xbad0047    ENETUNREACH   Network unreachable
 VMK_ENETRESET                    195887176   0xbad0048    ENETRESET     Network dropped connection on reset
 VMK_ECONNABORTED                 195887177   0xbad0049    ECONNABORTED  Software caused connection abort
 VMK_ECONNRESET                   195887178   0xbad004a    ECONNRESET    Connection reset by peer
 VMK_ENOTCONN                     195887179   0xbad004b    ENOTCONN      Socket is not connected
 VMK_ESHUTDOWN                    195887180   0xbad004c    ESHUTDOWN     Can't send after socket shutdown
 VMK_ETOOMANYREFS                 195887181   0xbad004d    ETOOMANYREFS  Too many references: can't splice
 VMK_ECONNREFUSED                 195887182   0xbad004e    ECONNREFUSED  Connection refused
 VMK_EHOSTDOWN                    195887183   0xbad004f    EHOSTDOWN     Host is down
 VMK_EHOSTUNREACH                 195887184   0xbad0050    EHOSTUNREACH  No route to host
 VMK_EADDRINUSE                   195887185   0xbad0051    EADDRINUSE    Address already in use
 VMK_BROKEN_PIPE                  195887186   0xbad0052    EPIPE         Broken pipe
 VMK_NOT_A_DIRECTORY              195887187   0xbad0053    ENOTDIR       Not a directory
 VMK_IS_A_DIRECTORY               195887188   0xbad0054    EISDIR        Is a directory
 VMK_NOT_EMPTY                    195887189   0xbad0055    ENOTEMPTY     Directory not empty
 VMK_NOT_IMPLEMENTED              195887190   0xbad0056    ENOSYS        Not implemented
 VMK_NO_SIGNAL_HANDLER            195887191   0xbad0057    EINVAL        No signal handler
 VMK_FATAL_SIGNAL_BLOCKED         195887192   0xbad0058    EINVAL        Fatal signal blocked
 VMK_NO_ACCESS                    195887193   0xbad0059    EACCES        Permission denied
 VMK_NO_PERMISSION                195887194   0xbad005a    EPERM         Operation not permitted
 VMK_UNDEFINED_SYSCALL            195887195   0xbad005b    ENOSYS        Undefined syscall
 VMK_RESULT_TOO_LARGE             195887196   0xbad005c    ERANGE        Result too large
 VMK_VLAN_FILTERED                195887197   0xbad005d    ERANGE        Pkts dropped because of VLAN (support)  mismatch
 VMK_BAD_EXCFRAME                 195887198   0xbad005e    EFAULT        Unsafe exception frame
 VMK_MODULE_NOT_LOADED            195887199   0xbad005f    ENODEV        Necessary module isn't loaded
 VMK_NO_SUCH_ZOMBIE               195887200   0xbad0060    ECHILD        No dead world by that name
 VMK_NO_SUCH_CARTEL               195887201   0xbad0061    ESRCH         No cartel by that name
 VMK_IS_A_SYMLINK                 195887202   0xbad0062    ELOOP         Is a symbolic link
 VMK_CROSS_DEVICE_LINK            195887203   0xbad0063    EXDEV         Cross-device link
 VMK_NOT_A_SOCKET                 195887204   0xbad0064    ENOTSOCK      Not a socket
 VMK_ILLEGAL_SEEK                 195887205   0xbad0065    ESPIPE        Illegal seek
 VMK_ADDRFAM_UNSUPP               195887206   0xbad0066    EAFNOSUPPORT  Unsupported address family
 VMK_ALREADY_CONNECTED            195887207   0xbad0067    EISCONN       Already connected
 VMK_DEATH_PENDING                195887208   0xbad0068    ENOENT        World is marked for death
 VMK_NO_CELL_ASSIGNMENT           195887209   0xbad0069    EINVAL        No valid scheduler cell assignment
 VMK_CPU_MIN_INVALID              195887210   0xbad006a    EINVAL        Invalid cpu min
 VMK_CPU_MINLIMIT_INVALID         195887211   0xbad006b    EINVAL        Invalid cpu minLimit
 VMK_CPU_MAX_INVALID              195887212   0xbad006c    EINVAL        Invalid cpu max
 VMK_CPU_SHARES_INVALID           195887213   0xbad006d    EINVAL        Invalid cpu shares
 VMK_CPU_MIN_OVERFLOW             195887214   0xbad006e    EINVAL        Cpu min outside valid range
 VMK_CPU_MINLIMIT_OVERFLOW        195887215   0xbad006f    EINVAL        Cpu minLimit outside valid range
 VMK_CPU_MAX_OVERFLOW             195887216   0xbad0070    EINVAL        Cpu max outside valid range
 VMK_CPU_MIN_GT_MINLIMIT          195887217   0xbad0071    EINVAL        Cpu min exceeds minLimit
 VMK_CPU_MIN_GT_MAX               195887218   0xbad0072    EINVAL        Cpu min exceeds max
 VMK_CPU_MINLIMIT_LT_RESERVED     195887219   0xbad0073    ENOSPC        Cpu minLimit less than cpu already  reserved by children
 VMK_CPU_MAX_LT_RESERVED          195887220   0xbad0074    ENOSPC        Cpu max less than cpu already reserved by children
 VMK_CPU_ADMIT_FAILED             195887221   0xbad0075    ENOSPC        Admission check failed for cpu resource
 VMK_MEM_MIN_INVALID              195887222   0xbad0076    EINVAL        Invalid memory min
 VMK_MEM_MINLIMIT_INVALID         195887223   0xbad0077    EINVAL        Invalid memory minLimit
 VMK_MEM_MAX_INVALID              195887224   0xbad0078    EINVAL        Invalid memory max
 VMK_MEM_MIN_OVERFLOW             195887225   0xbad0079    EINVAL        Memory min outside valid range
 VMK_MEM_MINLIMIT_OVERFLOW        195887226   0xbad007a    EINVAL        Memory minLimit outside valid range
 VMK_MEM_MAX_OVERFLOW             195887227   0xbad007b    EINVAL        Memory max outside valid range
 VMK_MEM_MIN_GT_MINLIMIT          195887228   0xbad007c    EINVAL        Memory min exceeds minLimit
 VMK_MEM_MIN_GT_MAX               195887229   0xbad007d    EINVAL        Memory min exceeds max
 VMK_MEM_MINLIMIT_LT_RESERVED     195887230   0xbad007e    ENOSPC        Memory minLimit less than memory already  reserved by children
 VMK_MEM_MAX_LT_RESERVED          195887231   0xbad007f    ENOSPC        Memory max less than memory already  reserved by children
 VMK_MEM_ADMIT_FAILED             195887232   0xbad0080    ENOSPC        Admission check failed for memory resource
 VMK_NO_SWAP_FILE                 195887233   0xbad0081    ENOENT        No swap file
 VMK_BAD_PARAM_COUNT              195887234   0xbad0082    EINVAL        Bad parameter count
 VMK_BAD_PARAM_TYPE               195887235   0xbad0083    EINVAL        Bad parameter type
 VMK_UNMAP_RETRY                  195887236   0xbad0084    ENOMEM        Dueling unmaps (ok to retry)
 VMK_INVALID_IOCTL                195887237   0xbad0085    ENOTTY        Inappropriate ioctl for device
 VMK_MAPFAULT_RETRY               195887238   0xbad0086    EBUSY         Mmap changed under page fault (ok to  retry)
 VMK_EINPROGRESS                  195887239   0xbad0087    EINPROGRESS   Operation now in progress
 VMK_ADDR_UNMAPPED                195887240   0xbad0088    EFAULT        Address temporarily unmapped
 VMK_INVALID_BUDDY_TYPE           195887241   0xbad0089    ENOMEM        Invalid buddy type
 VMK_LPAGE_INFO_NOT_FOUND         195887242   0xbad008a    ENOMEM        Large page info not found
 VMK_LPAGE_INFO_INVALID           195887243   0xbad008b    EINVAL        Invalid large page info
 VMK_SNAPSHOT_DEV                 195887244   0xbad008c    EIO           SCSI LUN is in snapshot state
 VMK_IN_TRANSITION                195887245   0xbad008d    EIO           SCSI LUN is in transition
 VMK_TXN_FULL                     195887246   0xbad008e    ENOSPC        Transaction ran out of lock space or log  space
 VMK_LOCK_NOT_FREE                195887247   0xbad008f    EBUSY         Lock was not free
 VMK_NUM_FILES_EXCEEDED           195887248   0xbad0090    ENOSPC        Exceed maximum number of files on the filesystem
 VMK_MIGRATE_VMX_FAILURE          195887249   0xbad0091    EINVAL        Migration determined a failure by the VMX
 VMK_VSI_LIST_OVERFLOW            195887250   0xbad0092    EFBIG         VSI GetList handler overflow
 VMK_INVALID_WORLD                195887251   0xbad0093    EINVAL        Invalid world
 VMK_INVALID_VMM                  195887252   0xbad0094    EINVAL        Invalid vmm
 VMK_INVALID_TXN                  195887253   0xbad0095    EINVAL        Invalid transaction
 VMK_FS_RETRY_OPERATION           195887254   0xbad0096    EAGAIN        Transient file system condition, suggest  retry
 VMK_VCPU_LIMIT_EXCEEDED          195887255   0xbad0097    EINVAL        Number of running VCPUs limit exceeded
 VMK_INVALID_METADATA             195887256   0xbad0098    EINVAL        Invalid metadata
 VMK_INVALID_PAGE_NUMBER          195887257   0xbad0099    EINVAL        Invalid page number
 VMK_NOT_EXEC                     195887258   0xbad009a    ENOEXEC       Not in executable format
 VMK_NFS_CONNECT_FAILURE          195887259   0xbad009b    EHOSTDOWN     Unable to connect to NFS server
 VMK_NFS_MOUNT_NOT_SUPPORTED      195887260   0xbad009c    EINVAL        The NFS server does not support MOUNT  version 3 over TCP
 VMK_NFS_NFS_NOT_SUPPORTED        195887261   0xbad009d    EINVAL        The NFS server does not support NFS  version 3 over TCP
 VMK_NFS_MOUNT_DENIED             195887262   0xbad009e    EPERM         The mount request was denied by the NFS  server. Check that the export exists and that the client is permitted to mount it
 VMK_NFS_MOUNT_NOT_DIR            195887263   0xbad009f    ENOTDIR       The specified mount path was not a directory
 VMK_NFS_BAD_FSINFO               195887264   0xbad00a0    EACCES        Unable to query remote mount point's attributes
 VMK_NFS_VOLUME_LIMIT_EXCEEDED    195887265   0xbad00a1    EINVAL        NFS has reached the maximum number of supported volumes
 VMK_NO_MEMORY_NICE               195887266   0xbad00a2    ENOMEM        Out of nice memory
 VMK_MIGRATE_PREEMPTIVE_FAIL      195887267   0xbad00a3    ENOMEM        VMotion failed to start due to lack of cpu or memory resources
 VMK_CACHE_MISS                   195887268   0xbad00a4    EFAULT        Cache miss
 VMK_STRESS_INDUCED_ERROR         195887269   0xbad00a5    EIO           Error induced when stress options are enabled
 VMK_TOO_MANY_LOCK_HOLDERS        195887270   0xbad00a6    EUSERS        Maximum number of concurrent hosts are already accessing this resource
 VMK_NO_JOURNAL                   195887271   0xbad00a7    EIO           Host doesn't have a journal
 VMK_RANK_VIOLATION               195887272   0xbad00a8    EDEADLK       Lock rank violation detected
 VMK_MODULE_FAILED                195887273   0xbad00a9    ENODEV        Module failed
 VMK_NO_MASTER_PTY                195887274   0xbad00aa    ENXIO         Unable to open slave if no master pty
 VMK_NOT_IOABLE                   195887275   0xbad00ab    EFAULT        Not IOAble
 VMK_NO_FREE_INODES               195887276   0xbad00ac    ENOSPC        No free inodes
 VMK_NO_MEMORY_FOR_FILEDATA       195887277   0xbad00ad    ENOSPC        No free memory for file data
 VMK_NO_TAR_SPACE                 195887278   0xbad00ae    ENOSPC        No free space to expand file or meta data
 VMK_NO_FIFO_READER               195887279   0xbad00af    ENXIO         Unable to open writer if no fifo reader
 VMK_NO_SUCH_DEVICE               195887280   0xbad00b0    EINVAL        No underlying device for major,minor
 VMK_MEM_MIN_GT_MEMSIZE           195887281   0xbad00b1    EINVAL        Memory min exceeds memSize
 VMK_NO_SUCH_VT                   195887282   0xbad00b2    ENXIO         No virtual terminal for number
 VMK_TOO_MANY_ELEMENTS            195887283   0xbad00b3    E2BIG         Too many elements for list
 VMK_SHAREDAREA_MISMATCH          195887284   0xbad00b4    ENOSYS        VMM&lt;-&gt;VMK shared are mismatch
 VMK_EXEC_FAILURE                 195887285   0xbad00b5    ESRCH         Failure during exec while original state already lost
 VMK_VMNIXMOD_NOT_LOADED          195887286   0xbad00b6    ENOSYS        vmnixmod kernel module not loaded
 VMK_INVALID_MODULE               195887287   0xbad00b7    EINVAL        Invalid module
 VMK_UNALIGNED_ADDRESS            195887288   0xbad00b8    EINVAL        Address is not aligned on page boundary
 VMK_NOT_MAPPED                   195887289   0xbad00b9    ENOMEM        Address is not mapped in address space
 VMK_NO_MESSAGE_SPACE             195887290   0xbad00ba    ENOMEM        No space to record a message
 VMK_PDI_STACK_OVERFLOW           195887291   0xbad00bb    EFBIG         No space left on PDI stack
 VMK_EXCEPTION_HANDLER_INVALID    195887292   0xbad00bc    EINVAL        Invalid exception handler
 VMK_EXCEPTION_NOT_HANDLED        195887293   0xbad00bd    EINVAL        Exception not handled by exception handler
 VMK_INVALID_MULTIWRITER_OBJECT   195887294   0xbad00be    EDEADLK       Can't open sparse/TBZ files in  multiwriter mode
 VMK_STORAGE_RETRY_OPERATION      195887295   0xbad00bf    EAGAIN        Transient storage condition, suggest retry
 VMK_HBA_ERROR                    195887296   0xbad00c0    EIO           Storage initiator error
 VMK_TIMER_INIT_FAILED            195887297   0xbad00c1    EINVAL        Timer initialization failed
 VMK_MODULE_NOT_FOUND             195887298   0xbad00c2    ENOENT        Module not found
 VMK_NOT_SOCKET_OWNER             195887299   0xbad00c3    EINVAL        Socket not owned by cartel
 VMK_VSI_HANDLER_NOT_FOUND        195887300   0xbad00c4    ENOENT        No VSI handler found for the requested node
 VMK_INVALID_MMAPPROTFLAGS        195887301   0xbad00c5    EINVAL        Invalid mmap protection flags
 VMK_INVALID_MAPCONTIG_SIZE       195887302   0xbad00c6    EINVAL        Invalid chunk size for contiguous mmap 
 VMK_INVALID_MAPCONTIG_MAX        195887303   0xbad00c7    EINVAL        Invalid MPN max for contiguous mmap 
 VMK_INVALID_MAPCONTIG_FLAG       195887304   0xbad00c8    EINVAL        Invalid mmap flag on contiguous mmap 
 VMK_NOT_LAZY_MMINFO              195887305   0xbad00c9    EINVAL        Unexpected fault on pre-faulted memory region
 VMK_MMINFO_WONT_SPLIT            195887306   0xbad00ca    EINVAL        Memory region cannot be split (remap/unmap)
 VMK_NO_CACHE_INFO                195887307   0xbad00cb    ENOENT        Cache Information not available
 VMK_CANNOT_REMAP_PINNED_MEMORY   195887308   0xbad00cc    EINVAL        Cannot remap pinned memory
 VMK_NO_SUCH_CARTELGROUP          195887309   0xbad00cd    ESRCH         No cartel group by that name
 VMK_SPLOCKSTATS_DISABLED         195887310   0xbad00ce    EINVAL        SPLock stats collection disabled
 VMK_BAD_TAR_IMAGE                195887311   0xbad00cf    EINVAL        Boot image is corrupted
 VMK_BRANCHED_ALREADY             195887312   0xbad00d0    EPERM         Branched file cannot be modified
 VMK_NAME_RESERVED_FOR_BRANCH     195887313   0xbad00d1    EPERM         Name is reserved for branched file
 VMK_CANNOT_BRANCH_UNLINKED       195887314   0xbad00d2    EPERM         Unlinked file cannot be branched
 VMK_MAX_RETRIES_EXCEEDED         195887315   0xbad00d3    EAGAIN        Maximum kernel-level retries exceeded
 VMK_OPTLOCK_STOLEN               195887316   0xbad00d4    EAGAIN        Optimistic lock acquired by another host
 VMK_NOT_MMAPABLE                 195887317   0xbad00d5    ENODEV        Object cannot be mmapped
 VMK_INVALID_CPU_AFFINITY         195887318   0xbad00d6    EINVAL        Invalid cpu affinity
 VMK_DEVICE_NOT_PARTOF_LV         195887319   0xbad00d7    ENXIO         Device does not contain a logical volume
 VMK_NO_SPACE                     195887320   0xbad00d8    ENOSPC        No space left on device
 VMK_VSI_INVALID_NODE_ID          195887321   0xbad00d9    EINVAL        Invalid vsi node ID
 VMK_TOO_MANY_USERS               195887322   0xbad00da    EUSERS        Too many users accessing this resource
 VMK_EALREADY                     195887323   0xbad00db    EALREADY      Operation already in progress
 VMK_BUF_TOO_SMALL                195887324   0xbad00dc    EINVAL        Buffer too small to complete the operation
 VMK_SNAPSHOT_DEV_DISALLOWED      195887325   0xbad00dd    EACCES        Snapshot device disallowed
 VMK_LVM_DEVICE_UNREACHABLE       195887326   0xbad00de    EIO           LVM device unreachable
 VMK_CPU_INVALID_RESOURCE_UNITS   195887327   0xbad00df    EINVAL        Invalid cpu resource units
 VMK_MEM_INVALID_RESOURCE_UNITS   195887328   0xbad00e0    EINVAL        Invalid memory resource units
 VMK_ABORTED                      195887329   0xbad00e1    ECANCELED     IO was aborted
 VMK_MEM_MIN_LT_RESERVED          195887330   0xbad00e2    ENOSPC        Memory min less than memory already reserved by children
 VMK_MEM_MIN_LT_CONSUMED          195887331   0xbad00e3    ENOSPC        Memory min less than memory required to support current consumption
 VMK_MEM_MAX_LT_CONSUMED          195887332   0xbad00e4    ENOSPC        Memory max less than memory required to support current consumption
 VMK_TIMEOUT_RETRY                195887333   0xbad00e5    ETIMEDOUT     Timeout (ok to retry)
 VMK_RESERVATION_LOST             195887334   0xbad00e6    EBUSY         Reservation Lost
 VMK_FS_STALE_METADATA            195887335   0xbad00e7    ENOENT        Cached metadata is stale
 VMK_NO_FCNTL_LOCK                195887336   0xbad00e8    ENOLCK        No fcntl lock slot left
 VMK_NO_FCNTL_LOCK_HOLDER         195887337   0xbad00e9    ENOLCK        No fcntl lock holder slot left
 VMK_NO_LICENSE                   195887338   0xbad00ea    EACCES        Not licensed to access VMFS volumes
 VMK_LVM_RETRY_OPERATION          195887339   0xbad00eb    EAGAIN        Transient LVM device condition, suggest retry
 VMK_SNAPSHOT_LV_INCOMPLETE       195887340   0xbad00ec    EAGAIN        Snapshot LV incomplete
 VMK_MEDIUM_NOT_FOUND             195887341   0xbad00ed    EIO           Medium not found
 VMK_MAX_PATHS_CLAIMED            195887342   0xbad00ee    ENOMEM        Maximum allowed SCSI paths have already  been claimed
 VMK_NOT_MOUNTABLE                195887343   0xbad00ef    ENODEV        Filesystem is not mountable
 VMK_MEMSIZE_GT_MEMSIZELIMIT      195887344   0xbad00f0    EINVAL        Memory size exceeds memSizeLimit
 VMK_GENERIC_LINUX_ERROR          732758016   0x2bad0000   EIO           Generic service console error</text>
    <sha1>35c75adeec41678014194f5a6926ecf6fd4827b8</sha1>
  </revision>
  <revision>
    <id>789</id>
    <parentid>787</parentid>
    <timestamp>2009-01-27T23:55:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Forgot categories</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24854" xml:space="preserve">==== vmkerrcode ====
Usage: 
 vmkerrcode [-l] [error code (hex or decimal)]
    -l list all error codes

This can be used in order to decode the error

==== Example output ====
 # vmkerrcode -l
 
 VMK_ReturnStatus table for VMware ESX Server, Build #130756
 Name                             Dec         Hex          errno equiv    Description                                                 
 -------------------------------------------------------------------------------
 VMK_OK                           0           0            OK            Success
 VMK_FAILURE                      195887105   0xbad0001    EINVAL        Failure
 VMK_WOULD_BLOCK                  195887106   0xbad0002    EAGAIN        Would block
 VMK_NOT_FOUND                    195887107   0xbad0003    ENOENT        Not found
 VMK_BUSY                         195887108   0xbad0004    EBUSY         Busy
 VMK_EXISTS                       195887109   0xbad0005    EEXIST        Already exists
 VMK_LIMIT_EXCEEDED               195887110   0xbad0006    EFBIG         Limit exceeded
 VMK_BAD_PARAM                    195887111   0xbad0007    EINVAL        Bad parameter
 VMK_METADATA_READ_ERROR          195887112   0xbad0008    EIO           Metadata read error
 VMK_METADATA_WRITE_ERROR         195887113   0xbad0009    EIO           Metadata write error
 VMK_IO_ERROR                     195887114   0xbad000a    EIO           I/O error
 VMK_READ_ERROR                   195887115   0xbad000b    EIO           Read error
 VMK_WRITE_ERROR                  195887116   0xbad000c    EIO           Write error
 VMK_INVALID_NAME                 195887117   0xbad000d    ENAMETOOLONG  Invalid name
 VMK_INVALID_HANDLE               195887118   0xbad000e    EBADF         Invalid handle
 VMK_INVALID_ADAPTER              195887119   0xbad000f    ENODEV        No such SCSI adapter
 VMK_INVALID_TARGET               195887120   0xbad0010    ENODEV        No such target on adapter
 VMK_INVALID_PARTITION            195887121   0xbad0011    ENXIO         No such partition on target
 VMK_INVALID_FS                   195887122   0xbad0012    ENXIO         No filesystem on the device
 VMK_INVALID_MEMMAP               195887123   0xbad0013    EFAULT        Memory map mismatch
 VMK_NO_MEMORY                    195887124   0xbad0014    ENOMEM        Out of memory
 VMK_NO_MEMORY_RETRY              195887125   0xbad0015    ENOMEM        Out of memory (ok to retry)
 VMK_NO_RESOURCES                 195887126   0xbad0016    ENOMEM        Out of resources
 VMK_NO_FREE_HANDLES              195887127   0xbad0017    EMFILE        No free handles
 VMK_NUM_HANDLES_EXCEEDED         195887128   0xbad0018    ENFILE        Exceeded maximum number of allowed handles
 VMK_DEPRECATED_NO_FREE_PTR_BLOCKS195887129   0xbad0019    ENOSPC        No free pointer blocks (deprecated)
 VMK_DEPRECATED_NO_FREE_DATA_BLOCKS195887130   0xbad001a    ENOSPC        No free data blocks (deprecated)
 VMK_CORRUPT_REDOLOG              195887131   0xbad001b    EBADF         Corrupt RedoLog
 VMK_STATUS_PENDING               195887132   0xbad001c    EAGAIN        Status pending
 VMK_STATUS_FREE                  195887133   0xbad001d    EAGAIN        Status free
 VMK_UNSUPPORTED_CPU              195887134   0xbad001e    ENODEV        Unsupported CPU
 VMK_NOT_SUPPORTED                195887135   0xbad001f    ENOSYS        Not supported
 VMK_TIMEOUT                      195887136   0xbad0020    ETIMEDOUT     Timeout
 VMK_READ_ONLY                    195887137   0xbad0021    EROFS         Read only
 VMK_RESERVATION_CONFLICT         195887138   0xbad0022    EAGAIN        SCSI reservation conflict
 VMK_FS_LOCKED                    195887139   0xbad0023    EADDRINUSE    File system locked
 VMK_NOT_ENOUGH_SLOTS             195887140   0xbad0024    ENFILE        Out of slots
 VMK_INVALID_ADDRESS              195887141   0xbad0025    EFAULT        Invalid address
 VMK_NOT_SHARED                   195887142   0xbad0026    ENOMEM        Not shared
 VMK_SHARED                       195887143   0xbad0027    ENOMEM        Page is shared
 VMK_KSEG_PAIR_FLUSHED            195887144   0xbad0028    ENOMEM        Kseg pair flushed
 VMK_MAX_ASYNCIO_PENDING          195887145   0xbad0029    ENOMEM        Max async I/O requests pending
 VMK_VERSION_MISMATCH_MINOR       195887146   0xbad002a    ENOSYS        Minor version mismatch
 VMK_VERSION_MISMATCH_MAJOR       195887147   0xbad002b    ENOSYS        Major version mismatch
 VMK_IS_CONNECTED                 195887148   0xbad002c    EINVAL        Already connected
 VMK_IS_DISCONNECTED              195887149   0xbad002d    ENOTCONN      Already disconnected
 VMK_IS_ENABLED                   195887150   0xbad002e    EINVAL        Already enabled
 VMK_IS_DISABLED                  195887151   0xbad002f    EINVAL        Already disabled
 VMK_NOT_INITIALIZED              195887152   0xbad0030    EINVAL        Not initialized
 VMK_WAIT_INTERRUPTED             195887153   0xbad0031    EINTR         Wait interrupted
 VMK_NAME_TOO_LONG                195887154   0xbad0032    ENAMETOOLONG  Name too long
 VMK_MISSING_FS_PES               195887155   0xbad0033    ENOTDIR       VMFS volume missing physical extents
 VMK_NICTEAMING_VALID_MASTER      195887156   0xbad0034    EINVAL        NIC teaming master valid
 VMK_NICTEAMING_SLAVE             195887157   0xbad0035    EEXIST        NIC teaming slave
 VMK_NICTEAMING_REGULAR_VMNIC     195887158   0xbad0036    EINVAL        NIC teaming regular VMNIC
 VMK_ABORT_NOT_RUNNING            195887159   0xbad0037    ECANCELED     Abort not running
 VMK_NOT_READY                    195887160   0xbad0038    EIO           Not ready
 VMK_CHECKSUM_MISMATCH            195887161   0xbad0039    EIO           Checksum mismatch
 VMK_VLAN_NO_HW_ACCEL             195887162   0xbad003a    EINVAL        VLan HW Acceleration not supported
 VMK_NO_VLAN_SUPPORT              195887163   0xbad003b    EOPNOTSUPP    VLan is not supported in vmkernel
 VMK_NOT_VLAN_HANDLE              195887164   0xbad003c    EINVAL        Not a VLan handle
 VMK_BAD_VLANID                   195887165   0xbad003d    EBADF         Couldn't retrieve VLan id
 VMK_MIG_PROTO_ERROR              195887166   0xbad003e    EINVAL        Migration protocol error
 VMK_NO_CONNECT                   195887167   0xbad003f    EIO           No connection
 VMK_SEGMENT_OVERLAP              195887168   0xbad0040    EINVAL        Segment overlap
 VMK_BAD_MPS                      195887169   0xbad0041    EIO           Error parsing MPS Table
 VMK_BAD_ACPI                     195887170   0xbad0042    EIO           Error parsing ACPI Table
 VMK_RESUME_ERROR                 195887171   0xbad0043    EIO           Failed to resume VM
 VMK_NO_ADDRESS_SPACE             195887172   0xbad0044    ENOMEM        Insufficient address space for operation
 VMK_BAD_ADDR_RANGE               195887173   0xbad0045    EINVAL        Bad address range
 VMK_ENETDOWN                     195887174   0xbad0046    ENETDOWN      Network is down
 VMK_ENETUNREACH                  195887175   0xbad0047    ENETUNREACH   Network unreachable
 VMK_ENETRESET                    195887176   0xbad0048    ENETRESET     Network dropped connection on reset
 VMK_ECONNABORTED                 195887177   0xbad0049    ECONNABORTED  Software caused connection abort
 VMK_ECONNRESET                   195887178   0xbad004a    ECONNRESET    Connection reset by peer
 VMK_ENOTCONN                     195887179   0xbad004b    ENOTCONN      Socket is not connected
 VMK_ESHUTDOWN                    195887180   0xbad004c    ESHUTDOWN     Can't send after socket shutdown
 VMK_ETOOMANYREFS                 195887181   0xbad004d    ETOOMANYREFS  Too many references: can't splice
 VMK_ECONNREFUSED                 195887182   0xbad004e    ECONNREFUSED  Connection refused
 VMK_EHOSTDOWN                    195887183   0xbad004f    EHOSTDOWN     Host is down
 VMK_EHOSTUNREACH                 195887184   0xbad0050    EHOSTUNREACH  No route to host
 VMK_EADDRINUSE                   195887185   0xbad0051    EADDRINUSE    Address already in use
 VMK_BROKEN_PIPE                  195887186   0xbad0052    EPIPE         Broken pipe
 VMK_NOT_A_DIRECTORY              195887187   0xbad0053    ENOTDIR       Not a directory
 VMK_IS_A_DIRECTORY               195887188   0xbad0054    EISDIR        Is a directory
 VMK_NOT_EMPTY                    195887189   0xbad0055    ENOTEMPTY     Directory not empty
 VMK_NOT_IMPLEMENTED              195887190   0xbad0056    ENOSYS        Not implemented
 VMK_NO_SIGNAL_HANDLER            195887191   0xbad0057    EINVAL        No signal handler
 VMK_FATAL_SIGNAL_BLOCKED         195887192   0xbad0058    EINVAL        Fatal signal blocked
 VMK_NO_ACCESS                    195887193   0xbad0059    EACCES        Permission denied
 VMK_NO_PERMISSION                195887194   0xbad005a    EPERM         Operation not permitted
 VMK_UNDEFINED_SYSCALL            195887195   0xbad005b    ENOSYS        Undefined syscall
 VMK_RESULT_TOO_LARGE             195887196   0xbad005c    ERANGE        Result too large
 VMK_VLAN_FILTERED                195887197   0xbad005d    ERANGE        Pkts dropped because of VLAN (support)  mismatch
 VMK_BAD_EXCFRAME                 195887198   0xbad005e    EFAULT        Unsafe exception frame
 VMK_MODULE_NOT_LOADED            195887199   0xbad005f    ENODEV        Necessary module isn't loaded
 VMK_NO_SUCH_ZOMBIE               195887200   0xbad0060    ECHILD        No dead world by that name
 VMK_NO_SUCH_CARTEL               195887201   0xbad0061    ESRCH         No cartel by that name
 VMK_IS_A_SYMLINK                 195887202   0xbad0062    ELOOP         Is a symbolic link
 VMK_CROSS_DEVICE_LINK            195887203   0xbad0063    EXDEV         Cross-device link
 VMK_NOT_A_SOCKET                 195887204   0xbad0064    ENOTSOCK      Not a socket
 VMK_ILLEGAL_SEEK                 195887205   0xbad0065    ESPIPE        Illegal seek
 VMK_ADDRFAM_UNSUPP               195887206   0xbad0066    EAFNOSUPPORT  Unsupported address family
 VMK_ALREADY_CONNECTED            195887207   0xbad0067    EISCONN       Already connected
 VMK_DEATH_PENDING                195887208   0xbad0068    ENOENT        World is marked for death
 VMK_NO_CELL_ASSIGNMENT           195887209   0xbad0069    EINVAL        No valid scheduler cell assignment
 VMK_CPU_MIN_INVALID              195887210   0xbad006a    EINVAL        Invalid cpu min
 VMK_CPU_MINLIMIT_INVALID         195887211   0xbad006b    EINVAL        Invalid cpu minLimit
 VMK_CPU_MAX_INVALID              195887212   0xbad006c    EINVAL        Invalid cpu max
 VMK_CPU_SHARES_INVALID           195887213   0xbad006d    EINVAL        Invalid cpu shares
 VMK_CPU_MIN_OVERFLOW             195887214   0xbad006e    EINVAL        Cpu min outside valid range
 VMK_CPU_MINLIMIT_OVERFLOW        195887215   0xbad006f    EINVAL        Cpu minLimit outside valid range
 VMK_CPU_MAX_OVERFLOW             195887216   0xbad0070    EINVAL        Cpu max outside valid range
 VMK_CPU_MIN_GT_MINLIMIT          195887217   0xbad0071    EINVAL        Cpu min exceeds minLimit
 VMK_CPU_MIN_GT_MAX               195887218   0xbad0072    EINVAL        Cpu min exceeds max
 VMK_CPU_MINLIMIT_LT_RESERVED     195887219   0xbad0073    ENOSPC        Cpu minLimit less than cpu already  reserved by children
 VMK_CPU_MAX_LT_RESERVED          195887220   0xbad0074    ENOSPC        Cpu max less than cpu already reserved by children
 VMK_CPU_ADMIT_FAILED             195887221   0xbad0075    ENOSPC        Admission check failed for cpu resource
 VMK_MEM_MIN_INVALID              195887222   0xbad0076    EINVAL        Invalid memory min
 VMK_MEM_MINLIMIT_INVALID         195887223   0xbad0077    EINVAL        Invalid memory minLimit
 VMK_MEM_MAX_INVALID              195887224   0xbad0078    EINVAL        Invalid memory max
 VMK_MEM_MIN_OVERFLOW             195887225   0xbad0079    EINVAL        Memory min outside valid range
 VMK_MEM_MINLIMIT_OVERFLOW        195887226   0xbad007a    EINVAL        Memory minLimit outside valid range
 VMK_MEM_MAX_OVERFLOW             195887227   0xbad007b    EINVAL        Memory max outside valid range
 VMK_MEM_MIN_GT_MINLIMIT          195887228   0xbad007c    EINVAL        Memory min exceeds minLimit
 VMK_MEM_MIN_GT_MAX               195887229   0xbad007d    EINVAL        Memory min exceeds max
 VMK_MEM_MINLIMIT_LT_RESERVED     195887230   0xbad007e    ENOSPC        Memory minLimit less than memory already  reserved by children
 VMK_MEM_MAX_LT_RESERVED          195887231   0xbad007f    ENOSPC        Memory max less than memory already  reserved by children
 VMK_MEM_ADMIT_FAILED             195887232   0xbad0080    ENOSPC        Admission check failed for memory resource
 VMK_NO_SWAP_FILE                 195887233   0xbad0081    ENOENT        No swap file
 VMK_BAD_PARAM_COUNT              195887234   0xbad0082    EINVAL        Bad parameter count
 VMK_BAD_PARAM_TYPE               195887235   0xbad0083    EINVAL        Bad parameter type
 VMK_UNMAP_RETRY                  195887236   0xbad0084    ENOMEM        Dueling unmaps (ok to retry)
 VMK_INVALID_IOCTL                195887237   0xbad0085    ENOTTY        Inappropriate ioctl for device
 VMK_MAPFAULT_RETRY               195887238   0xbad0086    EBUSY         Mmap changed under page fault (ok to  retry)
 VMK_EINPROGRESS                  195887239   0xbad0087    EINPROGRESS   Operation now in progress
 VMK_ADDR_UNMAPPED                195887240   0xbad0088    EFAULT        Address temporarily unmapped
 VMK_INVALID_BUDDY_TYPE           195887241   0xbad0089    ENOMEM        Invalid buddy type
 VMK_LPAGE_INFO_NOT_FOUND         195887242   0xbad008a    ENOMEM        Large page info not found
 VMK_LPAGE_INFO_INVALID           195887243   0xbad008b    EINVAL        Invalid large page info
 VMK_SNAPSHOT_DEV                 195887244   0xbad008c    EIO           SCSI LUN is in snapshot state
 VMK_IN_TRANSITION                195887245   0xbad008d    EIO           SCSI LUN is in transition
 VMK_TXN_FULL                     195887246   0xbad008e    ENOSPC        Transaction ran out of lock space or log  space
 VMK_LOCK_NOT_FREE                195887247   0xbad008f    EBUSY         Lock was not free
 VMK_NUM_FILES_EXCEEDED           195887248   0xbad0090    ENOSPC        Exceed maximum number of files on the filesystem
 VMK_MIGRATE_VMX_FAILURE          195887249   0xbad0091    EINVAL        Migration determined a failure by the VMX
 VMK_VSI_LIST_OVERFLOW            195887250   0xbad0092    EFBIG         VSI GetList handler overflow
 VMK_INVALID_WORLD                195887251   0xbad0093    EINVAL        Invalid world
 VMK_INVALID_VMM                  195887252   0xbad0094    EINVAL        Invalid vmm
 VMK_INVALID_TXN                  195887253   0xbad0095    EINVAL        Invalid transaction
 VMK_FS_RETRY_OPERATION           195887254   0xbad0096    EAGAIN        Transient file system condition, suggest  retry
 VMK_VCPU_LIMIT_EXCEEDED          195887255   0xbad0097    EINVAL        Number of running VCPUs limit exceeded
 VMK_INVALID_METADATA             195887256   0xbad0098    EINVAL        Invalid metadata
 VMK_INVALID_PAGE_NUMBER          195887257   0xbad0099    EINVAL        Invalid page number
 VMK_NOT_EXEC                     195887258   0xbad009a    ENOEXEC       Not in executable format
 VMK_NFS_CONNECT_FAILURE          195887259   0xbad009b    EHOSTDOWN     Unable to connect to NFS server
 VMK_NFS_MOUNT_NOT_SUPPORTED      195887260   0xbad009c    EINVAL        The NFS server does not support MOUNT  version 3 over TCP
 VMK_NFS_NFS_NOT_SUPPORTED        195887261   0xbad009d    EINVAL        The NFS server does not support NFS  version 3 over TCP
 VMK_NFS_MOUNT_DENIED             195887262   0xbad009e    EPERM         The mount request was denied by the NFS  server. Check that the export exists and that the client is permitted to mount it
 VMK_NFS_MOUNT_NOT_DIR            195887263   0xbad009f    ENOTDIR       The specified mount path was not a directory
 VMK_NFS_BAD_FSINFO               195887264   0xbad00a0    EACCES        Unable to query remote mount point's attributes
 VMK_NFS_VOLUME_LIMIT_EXCEEDED    195887265   0xbad00a1    EINVAL        NFS has reached the maximum number of supported volumes
 VMK_NO_MEMORY_NICE               195887266   0xbad00a2    ENOMEM        Out of nice memory
 VMK_MIGRATE_PREEMPTIVE_FAIL      195887267   0xbad00a3    ENOMEM        VMotion failed to start due to lack of cpu or memory resources
 VMK_CACHE_MISS                   195887268   0xbad00a4    EFAULT        Cache miss
 VMK_STRESS_INDUCED_ERROR         195887269   0xbad00a5    EIO           Error induced when stress options are enabled
 VMK_TOO_MANY_LOCK_HOLDERS        195887270   0xbad00a6    EUSERS        Maximum number of concurrent hosts are already accessing this resource
 VMK_NO_JOURNAL                   195887271   0xbad00a7    EIO           Host doesn't have a journal
 VMK_RANK_VIOLATION               195887272   0xbad00a8    EDEADLK       Lock rank violation detected
 VMK_MODULE_FAILED                195887273   0xbad00a9    ENODEV        Module failed
 VMK_NO_MASTER_PTY                195887274   0xbad00aa    ENXIO         Unable to open slave if no master pty
 VMK_NOT_IOABLE                   195887275   0xbad00ab    EFAULT        Not IOAble
 VMK_NO_FREE_INODES               195887276   0xbad00ac    ENOSPC        No free inodes
 VMK_NO_MEMORY_FOR_FILEDATA       195887277   0xbad00ad    ENOSPC        No free memory for file data
 VMK_NO_TAR_SPACE                 195887278   0xbad00ae    ENOSPC        No free space to expand file or meta data
 VMK_NO_FIFO_READER               195887279   0xbad00af    ENXIO         Unable to open writer if no fifo reader
 VMK_NO_SUCH_DEVICE               195887280   0xbad00b0    EINVAL        No underlying device for major,minor
 VMK_MEM_MIN_GT_MEMSIZE           195887281   0xbad00b1    EINVAL        Memory min exceeds memSize
 VMK_NO_SUCH_VT                   195887282   0xbad00b2    ENXIO         No virtual terminal for number
 VMK_TOO_MANY_ELEMENTS            195887283   0xbad00b3    E2BIG         Too many elements for list
 VMK_SHAREDAREA_MISMATCH          195887284   0xbad00b4    ENOSYS        VMM&lt;-&gt;VMK shared are mismatch
 VMK_EXEC_FAILURE                 195887285   0xbad00b5    ESRCH         Failure during exec while original state already lost
 VMK_VMNIXMOD_NOT_LOADED          195887286   0xbad00b6    ENOSYS        vmnixmod kernel module not loaded
 VMK_INVALID_MODULE               195887287   0xbad00b7    EINVAL        Invalid module
 VMK_UNALIGNED_ADDRESS            195887288   0xbad00b8    EINVAL        Address is not aligned on page boundary
 VMK_NOT_MAPPED                   195887289   0xbad00b9    ENOMEM        Address is not mapped in address space
 VMK_NO_MESSAGE_SPACE             195887290   0xbad00ba    ENOMEM        No space to record a message
 VMK_PDI_STACK_OVERFLOW           195887291   0xbad00bb    EFBIG         No space left on PDI stack
 VMK_EXCEPTION_HANDLER_INVALID    195887292   0xbad00bc    EINVAL        Invalid exception handler
 VMK_EXCEPTION_NOT_HANDLED        195887293   0xbad00bd    EINVAL        Exception not handled by exception handler
 VMK_INVALID_MULTIWRITER_OBJECT   195887294   0xbad00be    EDEADLK       Can't open sparse/TBZ files in  multiwriter mode
 VMK_STORAGE_RETRY_OPERATION      195887295   0xbad00bf    EAGAIN        Transient storage condition, suggest retry
 VMK_HBA_ERROR                    195887296   0xbad00c0    EIO           Storage initiator error
 VMK_TIMER_INIT_FAILED            195887297   0xbad00c1    EINVAL        Timer initialization failed
 VMK_MODULE_NOT_FOUND             195887298   0xbad00c2    ENOENT        Module not found
 VMK_NOT_SOCKET_OWNER             195887299   0xbad00c3    EINVAL        Socket not owned by cartel
 VMK_VSI_HANDLER_NOT_FOUND        195887300   0xbad00c4    ENOENT        No VSI handler found for the requested node
 VMK_INVALID_MMAPPROTFLAGS        195887301   0xbad00c5    EINVAL        Invalid mmap protection flags
 VMK_INVALID_MAPCONTIG_SIZE       195887302   0xbad00c6    EINVAL        Invalid chunk size for contiguous mmap 
 VMK_INVALID_MAPCONTIG_MAX        195887303   0xbad00c7    EINVAL        Invalid MPN max for contiguous mmap 
 VMK_INVALID_MAPCONTIG_FLAG       195887304   0xbad00c8    EINVAL        Invalid mmap flag on contiguous mmap 
 VMK_NOT_LAZY_MMINFO              195887305   0xbad00c9    EINVAL        Unexpected fault on pre-faulted memory region
 VMK_MMINFO_WONT_SPLIT            195887306   0xbad00ca    EINVAL        Memory region cannot be split (remap/unmap)
 VMK_NO_CACHE_INFO                195887307   0xbad00cb    ENOENT        Cache Information not available
 VMK_CANNOT_REMAP_PINNED_MEMORY   195887308   0xbad00cc    EINVAL        Cannot remap pinned memory
 VMK_NO_SUCH_CARTELGROUP          195887309   0xbad00cd    ESRCH         No cartel group by that name
 VMK_SPLOCKSTATS_DISABLED         195887310   0xbad00ce    EINVAL        SPLock stats collection disabled
 VMK_BAD_TAR_IMAGE                195887311   0xbad00cf    EINVAL        Boot image is corrupted
 VMK_BRANCHED_ALREADY             195887312   0xbad00d0    EPERM         Branched file cannot be modified
 VMK_NAME_RESERVED_FOR_BRANCH     195887313   0xbad00d1    EPERM         Name is reserved for branched file
 VMK_CANNOT_BRANCH_UNLINKED       195887314   0xbad00d2    EPERM         Unlinked file cannot be branched
 VMK_MAX_RETRIES_EXCEEDED         195887315   0xbad00d3    EAGAIN        Maximum kernel-level retries exceeded
 VMK_OPTLOCK_STOLEN               195887316   0xbad00d4    EAGAIN        Optimistic lock acquired by another host
 VMK_NOT_MMAPABLE                 195887317   0xbad00d5    ENODEV        Object cannot be mmapped
 VMK_INVALID_CPU_AFFINITY         195887318   0xbad00d6    EINVAL        Invalid cpu affinity
 VMK_DEVICE_NOT_PARTOF_LV         195887319   0xbad00d7    ENXIO         Device does not contain a logical volume
 VMK_NO_SPACE                     195887320   0xbad00d8    ENOSPC        No space left on device
 VMK_VSI_INVALID_NODE_ID          195887321   0xbad00d9    EINVAL        Invalid vsi node ID
 VMK_TOO_MANY_USERS               195887322   0xbad00da    EUSERS        Too many users accessing this resource
 VMK_EALREADY                     195887323   0xbad00db    EALREADY      Operation already in progress
 VMK_BUF_TOO_SMALL                195887324   0xbad00dc    EINVAL        Buffer too small to complete the operation
 VMK_SNAPSHOT_DEV_DISALLOWED      195887325   0xbad00dd    EACCES        Snapshot device disallowed
 VMK_LVM_DEVICE_UNREACHABLE       195887326   0xbad00de    EIO           LVM device unreachable
 VMK_CPU_INVALID_RESOURCE_UNITS   195887327   0xbad00df    EINVAL        Invalid cpu resource units
 VMK_MEM_INVALID_RESOURCE_UNITS   195887328   0xbad00e0    EINVAL        Invalid memory resource units
 VMK_ABORTED                      195887329   0xbad00e1    ECANCELED     IO was aborted
 VMK_MEM_MIN_LT_RESERVED          195887330   0xbad00e2    ENOSPC        Memory min less than memory already reserved by children
 VMK_MEM_MIN_LT_CONSUMED          195887331   0xbad00e3    ENOSPC        Memory min less than memory required to support current consumption
 VMK_MEM_MAX_LT_CONSUMED          195887332   0xbad00e4    ENOSPC        Memory max less than memory required to support current consumption
 VMK_TIMEOUT_RETRY                195887333   0xbad00e5    ETIMEDOUT     Timeout (ok to retry)
 VMK_RESERVATION_LOST             195887334   0xbad00e6    EBUSY         Reservation Lost
 VMK_FS_STALE_METADATA            195887335   0xbad00e7    ENOENT        Cached metadata is stale
 VMK_NO_FCNTL_LOCK                195887336   0xbad00e8    ENOLCK        No fcntl lock slot left
 VMK_NO_FCNTL_LOCK_HOLDER         195887337   0xbad00e9    ENOLCK        No fcntl lock holder slot left
 VMK_NO_LICENSE                   195887338   0xbad00ea    EACCES        Not licensed to access VMFS volumes
 VMK_LVM_RETRY_OPERATION          195887339   0xbad00eb    EAGAIN        Transient LVM device condition, suggest retry
 VMK_SNAPSHOT_LV_INCOMPLETE       195887340   0xbad00ec    EAGAIN        Snapshot LV incomplete
 VMK_MEDIUM_NOT_FOUND             195887341   0xbad00ed    EIO           Medium not found
 VMK_MAX_PATHS_CLAIMED            195887342   0xbad00ee    ENOMEM        Maximum allowed SCSI paths have already  been claimed
 VMK_NOT_MOUNTABLE                195887343   0xbad00ef    ENODEV        Filesystem is not mountable
 VMK_MEMSIZE_GT_MEMSIZELIMIT      195887344   0xbad00f0    EINVAL        Memory size exceeds memSizeLimit
 VMK_GENERIC_LINUX_ERROR          732758016   0x2bad0000   EIO           Generic service console error


[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>15cc330b240b7f97244003682924cd0cd43f8257</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>793</id>
    <parentid>159</parentid>
    <timestamp>2009-01-30T20:06:09Z</timestamp>
    <contributor>
      <username>Fixitchris</username>
      <id>11</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="57" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]</text>
    <sha1>477a8170a71c37f73f66af5efd177ce5739dc04b</sha1>
  </revision>
  <revision>
    <id>801</id>
    <parentid>793</parentid>
    <timestamp>2009-02-13T12:12:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="80" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]</text>
    <sha1>d539126a9b14cdd51432eeecd049a1b3b2038f24</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Vix Virtuozo Suite</title>
  <ns>0</ns>
  <id>418</id>
  <revision>
    <id>794</id>
    <timestamp>2009-01-30T20:07:40Z</timestamp>
    <contributor>
      <username>Fixitchris</username>
      <id>11</id>
    </contributor>
    <comment>New page: Vix_Virtuozo_Suite is a windows suite of applications for backing up guests across a domain.  [http://communities.vmware.com/thread/191565?tstart=0]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="148" xml:space="preserve">Vix_Virtuozo_Suite is a windows suite of applications for backing up guests across a domain.

[http://communities.vmware.com/thread/191565?tstart=0]</text>
    <sha1>d06dc579bc253ab7d15596117e4684fc80e91141</sha1>
  </revision>
  <revision>
    <id>795</id>
    <parentid>794</parentid>
    <timestamp>2009-01-30T20:08:20Z</timestamp>
    <contributor>
      <username>Fixitchris</username>
      <id>11</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">Vix_Virtuozo_Suite is a domain-wide Windows backup solution for VMDKs.

[http://communities.vmware.com/thread/191565?tstart=0]</text>
    <sha1>58bd457f1913a8f738e5224c0be753fbb1146b72</sha1>
  </revision>
  <revision>
    <id>796</id>
    <parentid>795</parentid>
    <timestamp>2009-01-30T22:55:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Categorized</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">Vix_Virtuozo_Suite is a domain-wide Windows backup solution for VMDKs.

[http://communities.vmware.com/thread/191565?tstart=0]

[[Category: VM Backup]]</text>
    <sha1>489f150b4d68e2f6b9b4195fbb3560ffd0d0e137</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>VMware Health Check Report</title>
  <ns>0</ns>
  <id>419</id>
  <revision>
    <id>798</id>
    <timestamp>2009-02-01T00:44:19Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/vmwareHealthCheck.pl vmwareHealthCheck.pl]  '''Compatible with''': ESX/ESXi 3.5+ and vCenter 2.5+  Please find more details...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1081" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/vmwareHealthCheck.pl vmwareHealthCheck.pl]

'''Compatible with''': ESX/ESXi 3.5+ and vCenter 2.5+

Please find more details located at: http://communities.vmware.com/docs/DOC-9420

This script generates a health check report of all attributes pertaining to a single ESX/ESXi 3.x+ host or VMware vCenter and its managed entities (i.e. clusters and individual ESX/ESXi 3.x+ hosts). The generated report is based off of some earlier Powershell script work created by Ivo Beerens/Duncan Eppping.

The script reports on the following and more:

    * vCenter Build/Release
    * ESX/ESXi Build/Release
    * Cluster(s) Name/Statistics (Hosts,CPU and MEM availabity, HA,DRS and DPM enabled)
    * ESX/ESXi Hardware configuration (NICs/HBAs)
    * ESX/ESXi State
    * ESX/ESXi Config (WIP)
    * ESX/ESXi Datastore summary
    * Virtual Machines summary
    * VM Storage summary
    * VM Network summary
    * VM w/Snapshots
    * VM w/RDMs
    * VM w/NPIV enabled
    * VM w/connected CD-ROMs
    * VM w/connected Floppys</text>
    <sha1>5dc4a5a2d322ad86cab6eb22d0be9481f0d6c9ea</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Build host vmware kernel modules</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>799</id>
    <parentid>231</parentid>
    <timestamp>2009-02-05T05:28:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Updated to force remove of the not_configured file as per http://communities.vmware.com/message/1162033</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2702" xml:space="preserve">====Integrated modules build script sometimes fails====
The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

====The solution====
You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm -f /etc/vmware/not_configured 

====Preconditions for the script to work====
You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko</text>
    <sha1>5aaa0fc677659c677655e1ffd12ba9dee2aace82</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Esxcfg-info</title>
  <ns>0</ns>
  <id>420</id>
  <revision>
    <id>800</id>
    <timestamp>2009-02-08T14:17:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== esxcfg-info ==== The esxcfg-info command can be used to query the setup information of your ESX configuration and hardware setup. The tool is originally designed for debugging/trouble...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3620" xml:space="preserve">==== esxcfg-info ====
The esxcfg-info command can be used to query the setup information of your ESX configuration and hardware setup. The tool is originally designed for debugging/troubleshooting your ESX configuration. Before ESX3.x this type of information could be retrieved from /proc/vmware but that use has now been depreciated and you should instead use this command.

The output of the esxcfg-info command does change per version of ESX, for this reason you should be careful when using it in scripting  and not to rely too much on the format. This dependency has been improved upon since ESX 3.5 by adding output formats that are more suitable for scripting.

Calling it with -a or -all parameter will print out all information unfiltered. The output can be used to save as a backup of your host setup. If you ever have to reinstall the host then this file can then be used as a baseline for verification if your setup matches the old configuration.

The command has the following additional options where most of them can be used to filter the output:
 -n --network
    Display the console and VMkernel network relevant configuration
 -s --storage
    Display everything about storage
 -w --hardware
    Display the hardware configuration from your server
 -y --software
    Display the software configuration of your ESX host
 -r --resource
    Get resource and schedule information
 -o --advopt
    Get advanced options
 -h --help
    print help
ESX3.5 has added the following options:
 -F xml for formatting the output as xml
 -F perl for formatting the output format for scripting with perl.

==== Usage examples ====
By combining the output of the esxcfg-info command with grep you can retrieve interesting information from your host. Following are a number of examples of what you can do with this.

===== Check 64 bits =====
You can use esxcfg-info as a way to check if your host is 64 bits capable AND if VT is enabled in the BIOS.

 esxcfg-info -w | grep HV
should return
 |----HV Support...............................................3
when it returns 2 it means that the host is capable, but that VT has not been enabled in the bios.

See also: [http://communities.vmware.com/message/1163510#1163510 How to tell if your host is 64 bit compatible without a reboot?]

===== Currently configured VLAN tags =====
You can retrieve what VLAN tags are configured on a physical switch that the ESX server connects to by querying for either the "_name" or the "Hint" keyword in the network part output from the esxcfg-info command.

To see a list of all of the network hints for each adapter run:
 esxcfg-info -n | grep -E -i "_name|hint"

taken from: [http://communities.vmware.com/thread/91189 esxcfg-info question]

===== Find storage device =====

 esxcfg-info -s | grep vmhb | grep -i vmkernel
which should give an output like:

 |---VmKernel Device Name..................vmhba0


===== Identify LUN locks =====
How-to identify hosts with unreleased SCSI reservations on LUNs.
 esxcfg-info -s | grep -i -B 12 pending

[http://communities.vmware.com/message/1086636 LUN locks]

===== Find software iSCSI vmhba number =====
By querying 2 lines before the iscsi kernel module, you can find the name of the vmhba device used for the software iSCSI stack:  
 root# esxcfg-info -s | grep -B 2 iscsi_mod
 |----Name...............................................vmhba34
 |----Console Name.......................................scsi3
 |----Driver.............................................iscsi_mod

[http://communities.vmware.com/message/912975 esx 3.5 (unix) command line to get the S/W iSCSI vmhba number]</text>
    <sha1>09297b8fdfa09589e77d8547db87deac56326a9c</sha1>
  </revision>
</page>
<page arvcontinue="20090105232042|753">
  <title>Build ESX drivers</title>
  <ns>0</ns>
  <id>421</id>
  <revision>
    <id>802</id>
    <timestamp>2009-02-13T12:13:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: [http://communities.vmware.com/people/nick.couchman Nick Couchman] has started a topic on how-to build your own ESX/ESXi drivers using linux sources and the freely GPL code from VMware and...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1430" xml:space="preserve">[http://communities.vmware.com/people/nick.couchman Nick Couchman] has started a topic on how-to build your own ESX/ESXi drivers using linux sources and the freely GPL code from VMware and he has been successful in doing so.

==== Required components ====
In order to do this you need to get yourself the following components:
* The code of the module that you want to add support for
* CentOS 3.9 in a virtual machine build environment is going to be the easiest way to get going, you can use the [http://isoredirect.centos.org/centos/3/isos/i386/ latest update] from the [http://www.centos.org centOS] web site.
* The [http://www.vmware.com/download/vi/open_source.html GPL components] from ESX. Here's a link to the [http://download3.vmware.com/software/vi/VMware-esx-public-source-3.5.0-123630.tar.gz ESX3.5 Update 3] sources.
 

''' Beware that VMware will NOT support your configuration with home-grown drivers '''


==== External links ====
* The communities thread [http://communities.vmware.com/thread/188244 GPL Components - build ESX Drivers?]
* The project at sourceforge [https://sourceforge.net/projects/open-vdrivers/ open-vdrivers]


At the time of writing this, the project has not released any sources, yet, but it has these entries on the wiki:

[http://open-vdrivers.wiki.sourceforge.net/intro Wiki - Intro]

[http://open-vdrivers.wiki.sourceforge.net/Getting_Started Wiki - Getting started]

[[Category: ESX]]</text>
    <sha1>0355da086bbcaad999dd9611bd8474ef415153f5</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>VMware Health Check Report</title>
  <ns>0</ns>
  <id>419</id>
  <revision>
    <id>803</id>
    <parentid>798</parentid>
    <timestamp>2009-02-18T18:47:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1110" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/vmwareHealthCheck.pl vmwareHealthCheck.pl]

'''Compatible with''': ESX/ESXi 3.5+ and vCenter 2.5+

Please find more details located at: http://communities.vmware.com/docs/DOC-9420

This script generates a health check report of all attributes pertaining to a single ESX/ESXi 3.x+ host or VMware vCenter and its managed entities (i.e. clusters and individual ESX/ESXi 3.x+ hosts). The generated report is based off of some earlier Powershell script work created by Ivo Beerens/Duncan Eppping.

The script reports on the following and more:

    * vCenter Build/Release
    * ESX/ESXi Build/Release
    * Cluster(s) Name/Statistics (Hosts,CPU and MEM availabity, HA,DRS and DPM enabled)
    * ESX/ESXi Hardware configuration (NICs/HBAs)
    * ESX/ESXi State
    * ESX/ESXi Config (WIP)
    * ESX/ESXi Datastore summary
    * Virtual Machines summary
    * VM Storage summary
    * VM Network summary
    * VM w/Snapshots
    * VM w/RDMs
    * VM w/NPIV enabled
    * VM w/connected CD-ROMs
    * VM w/connected Floppys

[[Category: VM Management]]</text>
    <sha1>49f7924a16754f070851fa90a56355258ac8b7f1</sha1>
  </revision>
  <revision>
    <id>804</id>
    <parentid>803</parentid>
    <timestamp>2009-02-18T18:49:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Category host management created as that better describes it.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1112" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/vmwareHealthCheck.pl vmwareHealthCheck.pl]

'''Compatible with''': ESX/ESXi 3.5+ and vCenter 2.5+

Please find more details located at: http://communities.vmware.com/docs/DOC-9420

This script generates a health check report of all attributes pertaining to a single ESX/ESXi 3.x+ host or VMware vCenter and its managed entities (i.e. clusters and individual ESX/ESXi 3.x+ hosts). The generated report is based off of some earlier Powershell script work created by Ivo Beerens/Duncan Eppping.

The script reports on the following and more:

    * vCenter Build/Release
    * ESX/ESXi Build/Release
    * Cluster(s) Name/Statistics (Hosts,CPU and MEM availabity, HA,DRS and DPM enabled)
    * ESX/ESXi Hardware configuration (NICs/HBAs)
    * ESX/ESXi State
    * ESX/ESXi Config (WIP)
    * ESX/ESXi Datastore summary
    * Virtual Machines summary
    * VM Storage summary
    * VM Network summary
    * VM w/Snapshots
    * VM w/RDMs
    * VM w/NPIV enabled
    * VM w/connected CD-ROMs
    * VM w/connected Floppys

[[Category: Host Management]]</text>
    <sha1>c7802afbc4374bef02037ecf48291f6a431ade88</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>"Quick" migration utility for VM(s) on ESX and ESXi</title>
  <ns>0</ns>
  <id>415</id>
  <revision>
    <id>805</id>
    <parentid>784</parentid>
    <timestamp>2009-02-18T18:50:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1197" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoQuickMigrate.sh ghettoQuickMigrate.sh]

'''Compatible with''': ESX/ESXi 3.5u2+

Please find more details located at: http://communities.vmware.com/docs/DOC-9400

This script provides administrators running the free version of ESXi on several hosts with the capability to perform Hyper-V-like "'''quick'''" migrations of virtual machines residing on shared storage between the hosts. [http://www.vmware.com/support/developer/vima/ VMware's VIMA] virtual appliance was chosen as the central launch point for the quick migration process. '''ghettoQuickMigration.sh''' is executed from within VIMA and is compatible with ESXi 3.5u2+.

This script follows similarly to the Hyper-V Quick Migration process with the exception of replacing the disk resource swap with a virtual machine unregister/register command on the source and target hosts respectively. The state (powered ON/Suspended/OFF) of the virtual machine designated for migration is preserved through the entire process. Online virtual machines undergoing this migration will experience a temporary pause due to the suspend and resume steps.

[[Category: VM Automation]]</text>
    <sha1>dc248560c92bbcdab5a03c92e6232f40781f7b16</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Build ESX drivers</title>
  <ns>0</ns>
  <id>421</id>
  <revision>
    <id>806</id>
    <parentid>802</parentid>
    <timestamp>2009-02-18T18:52:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1449" xml:space="preserve">[http://communities.vmware.com/people/nick.couchman Nick Couchman] has started a topic on how-to build your own ESX/ESXi drivers using linux sources and the freely GPL code from VMware and he has been successful in doing so.

==== Required components ====
In order to do this you need to get yourself the following components:
* The code of the module that you want to add support for
* CentOS 3.9 in a virtual machine build environment is going to be the easiest way to get going, you can use the [http://isoredirect.centos.org/centos/3/isos/i386/ latest update] from the [http://www.centos.org centOS] web site.
* The [http://www.vmware.com/download/vi/open_source.html GPL components] from ESX. Here's a link to the [http://download3.vmware.com/software/vi/VMware-esx-public-source-3.5.0-123630.tar.gz ESX3.5 Update 3] sources.
 

''' Beware that VMware will NOT support your configuration with home-grown drivers '''


==== External links ====
* The communities thread [http://communities.vmware.com/thread/188244 GPL Components - build ESX Drivers?]
* The project at sourceforge [https://sourceforge.net/projects/open-vdrivers/ open-vdrivers]


At the time of writing this, the project has not released any sources, yet, but it has these entries on the wiki:

[http://open-vdrivers.wiki.sourceforge.net/intro Wiki - Intro]

[http://open-vdrivers.wiki.sourceforge.net/Getting_Started Wiki - Getting started]

[[Category: ESX]] [[Category: ESXi]]</text>
    <sha1>3631f5ec5d00fecc8938e09f5e0028d47045f938</sha1>
  </revision>
  <revision>
    <id>812</id>
    <parentid>806</parentid>
    <timestamp>2009-02-18T19:13:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1474" xml:space="preserve">[http://communities.vmware.com/people/nick.couchman Nick Couchman] has started a topic on how-to build your own ESX/ESXi drivers using linux sources and the freely GPL code from VMware and he has been successful in doing so.

==== Required components ====
In order to do this you need to get yourself the following components:
* The code of the module that you want to add support for
* CentOS 3.9 in a virtual machine build environment is going to be the easiest way to get going, you can use the [http://isoredirect.centos.org/centos/3/isos/i386/ latest update] from the [http://www.centos.org centOS] web site.
* The [http://www.vmware.com/download/vi/open_source.html GPL components] from ESX. Here's a link to the [http://download3.vmware.com/software/vi/VMware-esx-public-source-3.5.0-123630.tar.gz ESX3.5 Update 3] sources.
 

''' Beware that VMware will NOT support your configuration with home-grown drivers '''


==== External links ====
* The communities thread [http://communities.vmware.com/thread/188244 GPL Components - build ESX Drivers?]
* The project at sourceforge [https://sourceforge.net/projects/open-vdrivers/ open-vdrivers]


At the time of writing this, the project has not released any sources, yet, but it has these entries on the wiki:

[http://open-vdrivers.wiki.sourceforge.net/intro Wiki - Intro]

[http://open-vdrivers.wiki.sourceforge.net/Getting_Started Wiki - Getting started]

[[Category: ESX]] [[Category: ESXi]] [[Category: Hypervisor]]</text>
    <sha1>a16fbf3b70870ca4ba10f3ae833b23fc442901dc</sha1>
  </revision>
  <revision>
    <id>821</id>
    <parentid>812</parentid>
    <timestamp>2009-02-19T16:36:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1499" xml:space="preserve">[http://communities.vmware.com/people/nick.couchman Nick Couchman] has started a topic on how-to build your own ESX/ESXi drivers using linux sources and the freely GPL code from VMware and he has been successful in doing so.

==== Required components ====
In order to do this you need to get yourself the following components:
* The code of the module that you want to add support for
* CentOS 3.9 in a virtual machine build environment is going to be the easiest way to get going, you can use the [http://isoredirect.centos.org/centos/3/isos/i386/ latest update] from the [http://www.centos.org centOS] web site.
* The [http://www.vmware.com/download/vi/open_source.html GPL components] from ESX. Here's a link to the [http://download3.vmware.com/software/vi/VMware-esx-public-source-3.5.0-123630.tar.gz ESX3.5 Update 3] sources.
 

''' Beware that VMware will NOT support your configuration with home-grown drivers '''


==== External links ====
* The communities thread [http://communities.vmware.com/thread/188244 GPL Components - build ESX Drivers?]
* The project at sourceforge [https://sourceforge.net/projects/open-vdrivers/ open-vdrivers]


At the time of writing this, the project has not released any sources, yet, but it has these entries on the wiki:

[http://open-vdrivers.wiki.sourceforge.net/intro Wiki - Intro]

[http://open-vdrivers.wiki.sourceforge.net/Getting_Started Wiki - Getting started]

[[Category: ESX]] [[Category: ESXi]] [[Category: Hypervisor]] [[Category: VMware OSS]]</text>
    <sha1>b529061902db2839fe60869967417eaa2d872287</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Free VM Clone utility for ESX and ESXi</title>
  <ns>0</ns>
  <id>413</id>
  <revision>
    <id>807</id>
    <parentid>776</parentid>
    <timestamp>2009-02-18T18:54:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="956" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoClone.sh ghettoClone.sh]

'''Requires''': [http://www.engr.ucsb.edu/~duonglt/vmware/my-vmregister.pl my-vmregister.pl]

'''Compatible with''': ESX/ESXi 3.5u2+

Please find more details located at: http://communities.vmware.com/docs/DOC-9321

This script provide administrators with a means to automatically clone and deploy a large subset of virtual machines into a virtual environment without requiring tedious Service Console work or Virtual Center. Furthermore, for ease of accessibility, the free [http://www.vmware.com/support/developer/vima/ VMware VIMA] appliance was chosen as the central launch point for the cloning process. '''ghettoClone.sh''' is executed from within VIMA and is compatible with both ESX and ESXi 3.5u2+. It accepts a single source virtual machine along with inputted configuration parameters to tailor cloned virtual machines.

[[Category: VM Automation]]</text>
    <sha1>13c3107039be6671cb721a769842c170d4a685e8</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Esxcfg-info</title>
  <ns>0</ns>
  <id>420</id>
  <revision>
    <id>808</id>
    <parentid>800</parentid>
    <timestamp>2009-02-18T18:55:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3657" xml:space="preserve">==== esxcfg-info ====
The esxcfg-info command can be used to query the setup information of your ESX configuration and hardware setup. The tool is originally designed for debugging/troubleshooting your ESX configuration. Before ESX3.x this type of information could be retrieved from /proc/vmware but that use has now been depreciated and you should instead use this command.

The output of the esxcfg-info command does change per version of ESX, for this reason you should be careful when using it in scripting  and not to rely too much on the format. This dependency has been improved upon since ESX 3.5 by adding output formats that are more suitable for scripting.

Calling it with -a or -all parameter will print out all information unfiltered. The output can be used to save as a backup of your host setup. If you ever have to reinstall the host then this file can then be used as a baseline for verification if your setup matches the old configuration.

The command has the following additional options where most of them can be used to filter the output:
 -n --network
    Display the console and VMkernel network relevant configuration
 -s --storage
    Display everything about storage
 -w --hardware
    Display the hardware configuration from your server
 -y --software
    Display the software configuration of your ESX host
 -r --resource
    Get resource and schedule information
 -o --advopt
    Get advanced options
 -h --help
    print help
ESX3.5 has added the following options:
 -F xml for formatting the output as xml
 -F perl for formatting the output format for scripting with perl.

==== Usage examples ====
By combining the output of the esxcfg-info command with grep you can retrieve interesting information from your host. Following are a number of examples of what you can do with this.

===== Check 64 bits =====
You can use esxcfg-info as a way to check if your host is 64 bits capable AND if VT is enabled in the BIOS.

 esxcfg-info -w | grep HV
should return
 |----HV Support...............................................3
when it returns 2 it means that the host is capable, but that VT has not been enabled in the bios.

See also: [http://communities.vmware.com/message/1163510#1163510 How to tell if your host is 64 bit compatible without a reboot?]

===== Currently configured VLAN tags =====
You can retrieve what VLAN tags are configured on a physical switch that the ESX server connects to by querying for either the "_name" or the "Hint" keyword in the network part output from the esxcfg-info command.

To see a list of all of the network hints for each adapter run:
 esxcfg-info -n | grep -E -i "_name|hint"

taken from: [http://communities.vmware.com/thread/91189 esxcfg-info question]

===== Find storage device =====

 esxcfg-info -s | grep vmhb | grep -i vmkernel
which should give an output like:

 |---VmKernel Device Name..................vmhba0


===== Identify LUN locks =====
How-to identify hosts with unreleased SCSI reservations on LUNs.
 esxcfg-info -s | grep -i -B 12 pending

[http://communities.vmware.com/message/1086636 LUN locks]

===== Find software iSCSI vmhba number =====
By querying 2 lines before the iscsi kernel module, you can find the name of the vmhba device used for the software iSCSI stack:  
 root# esxcfg-info -s | grep -B 2 iscsi_mod
 |----Name...............................................vmhba34
 |----Console Name.......................................scsi3
 |----Driver.............................................iscsi_mod

[http://communities.vmware.com/message/912975 esx 3.5 (unix) command line to get the S/W iSCSI vmhba number]

[[Category: ESX]] [[Category: SDK]]</text>
    <sha1>e540fedc58ece2be06db7c74dd79d4b17904ba18</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Linked Clones for ESX 3.+</title>
  <ns>0</ns>
  <id>402</id>
  <revision>
    <id>809</id>
    <parentid>729</parentid>
    <timestamp>2009-02-18T18:57:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1911" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghetto-esx-linked-clones.sh ghetto-esx-linked-clones.sh]

'''Compatiable with''': ESX 3.x+

Please find more details located at: http://communities.vmware.com/docs/DOC-9020

This script allows users to create linked cloned virtual machine(s) from a master (or golden) virtual machine. Clones may be stored on any type of datastore (LOCAL, SAN, NFS) that is presented to the ESX host. The script is very capable in deploying a large VDI environment in a relatively short amount of time.

There are currently 3 supported use cases:

1) '''Default'''&lt;br&gt;
--Description: Generate linked clones located in the same datastore that houses the master (golden) virtual machine. Writes will be directed to their respective linked virtual machine delta file with reads originating from the master virtual machine. 

2) '''Distributed Write(s) I/O'''&lt;br&gt;
--Description: Generate linked clones evenly across available datastores of choice. Reads will originate from the specified master virtual machine while writes are directed towards their respective virtual machine delta files that have been dispersed across the specified datastores. 

3) '''Distributed Read(s) &amp; Write(s) I/O'''&lt;br&gt;
--Description: Duplicate the master virtual machine on available datastores of choice and evenly generate linked clones off of each duplicated master virtual machine. Reads and writes will be isolated onto the datastore of the linked clone(s) in question. This process is similar to running multiple instances of the default behavior of the script. 

'''Note''': This linked clones script is virtual machine OS independent (i.e. it is not restricted to just Windows OS's for VDI environment). For example, one can utilize this script to their advantage in development environments where new VMs need to be (mass) cloned quickly for testing.

[[Category: VM Automation]]</text>
    <sha1>0d912aee71a0d1b92aa79ab7f3678bf1dadf2816</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>810</id>
    <parentid>801</parentid>
    <timestamp>2009-02-18T19:08:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="95" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]</text>
    <sha1>063256eb24d47ee4627606b5eda21043c9c3b00b</sha1>
  </revision>
  <revision>
    <id>828</id>
    <parentid>810</parentid>
    <timestamp>2009-02-19T17:49:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>adding libview</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]</text>
    <sha1>3e9afddc2e15c9384ccb1536e5f5a1a175ef3c10</sha1>
  </revision>
  <revision>
    <id>830</id>
    <parentid>828</parentid>
    <timestamp>2009-02-19T17:55:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="127" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]</text>
    <sha1>9c8e272786797d43bb37a2b94b62b277f38df509</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>VMI Linux</title>
  <ns>0</ns>
  <id>422</id>
  <revision>
    <id>811</id>
    <timestamp>2009-02-18T19:11:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== VMI Linux ====  VMI-Linux is a virtualization interface for Linux with the goal of introducing cross hypervisor compatibility, so a single Linux kernel can run unmodified on L4, VMwar...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="767" xml:space="preserve">==== VMI Linux ====

VMI-Linux is a virtualization interface for Linux with the goal of introducing cross hypervisor compatibility, so a single Linux kernel can run unmodified on L4, VMware, Xen and other hypervisors, as well as native hardware, with excellent performance. 

Here's the project for the ROM code:

* http://sourceforge.net/projects/vmi-linux/

and this is the specification of the paravirtualisation layer.

* [http://www.vmware.com/pdf/vmi_specs.pdf The VMI specification]


A totally unrelated remark...
With sufficient thrust, pigs fly just fine. However this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925

[[Category: Hypervisor]]</text>
    <sha1>5cd0212b5de69c882db1a9a24b0275eb0d0d04fb</sha1>
  </revision>
  <revision>
    <id>813</id>
    <parentid>811</parentid>
    <timestamp>2009-02-18T19:14:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>removed bad joke</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="518" xml:space="preserve">==== VMI Linux ====

VMI-Linux is a virtualization interface for Linux with the goal of introducing cross hypervisor compatibility, so a single Linux kernel can run unmodified on L4, VMware, Xen and other hypervisors, as well as native hardware, with excellent performance. 

Here's the project for the ROM code:

* http://sourceforge.net/projects/vmi-linux/

and this is the specification of the paravirtualisation layer.

* [http://www.vmware.com/pdf/vmi_specs.pdf The VMI specification]


[[Category: Hypervisor]]</text>
    <sha1>263b1649f51cedf0acda8d51b137c3f5fa665858</sha1>
  </revision>
  <revision>
    <id>820</id>
    <parentid>813</parentid>
    <timestamp>2009-02-19T16:35:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="543" xml:space="preserve">==== VMI Linux ====

VMI-Linux is a virtualization interface for Linux with the goal of introducing cross hypervisor compatibility, so a single Linux kernel can run unmodified on L4, VMware, Xen and other hypervisors, as well as native hardware, with excellent performance. 

Here's the project for the ROM code:

* http://sourceforge.net/projects/vmi-linux/

and this is the specification of the paravirtualisation layer.

* [http://www.vmware.com/pdf/vmi_specs.pdf The VMI specification]


[[Category: Hypervisor]] [[Category: VMware OSS]]</text>
    <sha1>58b42131aac5bcb2cbf390d8c407d35ff1c54a13</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>VProbe Toolkit</title>
  <ns>0</ns>
  <id>14</id>
  <revision>
    <id>814</id>
    <parentid>22</parentid>
    <timestamp>2009-02-18T20:18:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2388" xml:space="preserve">==== VProbe Toolkit ====

This provides an interactive, programmer-friendly interface to VMware's VProbes facility. VProbes is a safe, dynamic technology for instrumenting software running in virtual machines, and the software stack itself. 

http://sourceforge.net/projects/vprobe-toolkit/

==== Advantages and disadvantages of using VProbe ====
Debugging your applications/kernel from outside the VM has some big pluses, and some big minuses. On the pro 

# Most importantly, VProbes is '''safe'''. Using a kernel debugger or something from within a guest provides some very dangerous opportunities: e.g., you could poke a hole in a critical guest memory structure. Also, kernel debuggers usually stop the target program to allow inspection. VProbes keeps things moving along while data is harvested, so it can be used even on mission-critical, highly available systems.
# VProbes doesn't rely on any in-guest tools. If the target is, for instance, an appliance that doesn't even have a login shell, let alone /usr/bin/top, VProbes works no better or worse.
# It doesn't care what state the guest is in. If the guest is hard hung, or is swapping too hard for a shell to come up, or whatever, VProbes can be a "tool of last resort" to try to harvest information.
# VProbes is also immune to guest attempts to fool it. For instance, malware often tries to change in-guest instrumentation tools to make itself undetectable. Since the VM/hypervisor trust boundary protects vprobes, it is immune to this weirdness.
# VProbes is neutral as to the identity of the guest; since it's machine-level, you can use the same tools for Windows, Linux, Solaris, FreeBSD, MacOS, etc. To the extent the preload scripts work, even some common, but OS-specific, notions, like processes, can be captured.


The big negatives all boil down to the same fundamental problem: the machine abstraction level is sometimes very far away from the application abstraction level. If it's a java application running, for instance, VProbes will sit there telling you: "java.exe is running!" Well, no kidding; you probably wanted to know, e.g., which method invocation it was in. VMware is thinking about ways to bridge that gap, but alas, there's very little to offer for serious discussion at this time.

==== External links ====
[http://communities.vmware.com/thread/194591 Vprobe-toolkit in Windows]

[[Category:SDK]]</text>
    <sha1>69cf1a7ed0f9cc3263e5ffcab4443e6eb16386d8</sha1>
  </revision>
  <revision>
    <id>815</id>
    <parentid>814</parentid>
    <timestamp>2009-02-19T16:23:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added a "you have to see this" link :)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2474" xml:space="preserve">==== VProbe Toolkit ====

This provides an interactive, programmer-friendly interface to VMware's VProbes facility. VProbes is a safe, dynamic technology for instrumenting software running in virtual machines, and the software stack itself. 

http://sourceforge.net/projects/vprobe-toolkit/

==== Advantages and disadvantages of using VProbe ====
Debugging your applications/kernel from outside the VM has some big pluses, and some big minuses. On the pro 

# Most importantly, VProbes is '''safe'''. Using a kernel debugger or something from within a guest provides some very dangerous opportunities: e.g., you could poke a hole in a critical guest memory structure. Also, kernel debuggers usually stop the target program to allow inspection. VProbes keeps things moving along while data is harvested, so it can be used even on mission-critical, highly available systems.
# VProbes doesn't rely on any in-guest tools. If the target is, for instance, an appliance that doesn't even have a login shell, let alone /usr/bin/top, VProbes works no better or worse.
# It doesn't care what state the guest is in. If the guest is hard hung, or is swapping too hard for a shell to come up, or whatever, VProbes can be a "tool of last resort" to try to harvest information.
# VProbes is also immune to guest attempts to fool it. For instance, malware often tries to change in-guest instrumentation tools to make itself undetectable. Since the VM/hypervisor trust boundary protects vprobes, it is immune to this weirdness.
# VProbes is neutral as to the identity of the guest; since it's machine-level, you can use the same tools for Windows, Linux, Solaris, FreeBSD, MacOS, etc. To the extent the preload scripts work, even some common, but OS-specific, notions, like processes, can be captured.


The big negatives all boil down to the same fundamental problem: the machine abstraction level is sometimes very far away from the application abstraction level. If it's a java application running, for instance, VProbes will sit there telling you: "java.exe is running!" Well, no kidding; you probably wanted to know, e.g., which method invocation it was in. VMware is thinking about ways to bridge that gap, but alas, there's very little to offer for serious discussion at this time.

==== External links ====
[http://blogs.vmware.com/vmtn/2008/06/introducing-vpr.html Video introducing VProbes]
[http://communities.vmware.com/thread/194591 Vprobe-toolkit in Windows]

[[Category:SDK]]</text>
    <sha1>526f0ca40b94c96f241c93f625af56874bf9820d</sha1>
  </revision>
  <revision>
    <id>816</id>
    <parentid>815</parentid>
    <timestamp>2009-02-19T16:23:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2478" xml:space="preserve">==== VProbe Toolkit ====

This provides an interactive, programmer-friendly interface to VMware's VProbes facility. VProbes is a safe, dynamic technology for instrumenting software running in virtual machines, and the software stack itself. 

http://sourceforge.net/projects/vprobe-toolkit/

==== Advantages and disadvantages of using VProbe ====
Debugging your applications/kernel from outside the VM has some big pluses, and some big minuses. On the pro 

# Most importantly, VProbes is '''safe'''. Using a kernel debugger or something from within a guest provides some very dangerous opportunities: e.g., you could poke a hole in a critical guest memory structure. Also, kernel debuggers usually stop the target program to allow inspection. VProbes keeps things moving along while data is harvested, so it can be used even on mission-critical, highly available systems.
# VProbes doesn't rely on any in-guest tools. If the target is, for instance, an appliance that doesn't even have a login shell, let alone /usr/bin/top, VProbes works no better or worse.
# It doesn't care what state the guest is in. If the guest is hard hung, or is swapping too hard for a shell to come up, or whatever, VProbes can be a "tool of last resort" to try to harvest information.
# VProbes is also immune to guest attempts to fool it. For instance, malware often tries to change in-guest instrumentation tools to make itself undetectable. Since the VM/hypervisor trust boundary protects vprobes, it is immune to this weirdness.
# VProbes is neutral as to the identity of the guest; since it's machine-level, you can use the same tools for Windows, Linux, Solaris, FreeBSD, MacOS, etc. To the extent the preload scripts work, even some common, but OS-specific, notions, like processes, can be captured.


The big negatives all boil down to the same fundamental problem: the machine abstraction level is sometimes very far away from the application abstraction level. If it's a java application running, for instance, VProbes will sit there telling you: "java.exe is running!" Well, no kidding; you probably wanted to know, e.g., which method invocation it was in. VMware is thinking about ways to bridge that gap, but alas, there's very little to offer for serious discussion at this time.

==== External links ====
* [http://blogs.vmware.com/vmtn/2008/06/introducing-vpr.html Video introducing VProbes]
* [http://communities.vmware.com/thread/194591 Vprobe-toolkit in Windows]

[[Category:SDK]]</text>
    <sha1>899b3357f0e3950504df93481c56cd86032da4a2</sha1>
  </revision>
  <revision>
    <id>817</id>
    <parentid>816</parentid>
    <timestamp>2009-02-19T16:29:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>and even more links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2730" xml:space="preserve">==== VProbe Toolkit ====

This provides an interactive, programmer-friendly interface to VMware's VProbes facility. VProbes is a safe, dynamic technology for instrumenting software running in virtual machines, and the software stack itself. 


* [http://sourceforge.net/projects/vprobe-toolkit/ Sourceforge project vprobe-toolkit]
* [http://www.vmware.com/products/beta/ws/vprobes_reference.pdf official reference]
* [http://www.vmware.com/download/ws/ download]
* [http://communities.vmware.com/community/developer/vprobes VProbes community]

==== Advantages and disadvantages of using VProbe ====
Debugging your applications/kernel from outside the VM has some big pluses, and some big minuses. On the pro 

# Most importantly, VProbes is '''safe'''. Using a kernel debugger or something from within a guest provides some very dangerous opportunities: e.g., you could poke a hole in a critical guest memory structure. Also, kernel debuggers usually stop the target program to allow inspection. VProbes keeps things moving along while data is harvested, so it can be used even on mission-critical, highly available systems.
# VProbes doesn't rely on any in-guest tools. If the target is, for instance, an appliance that doesn't even have a login shell, let alone /usr/bin/top, VProbes works no better or worse.
# It doesn't care what state the guest is in. If the guest is hard hung, or is swapping too hard for a shell to come up, or whatever, VProbes can be a "tool of last resort" to try to harvest information.
# VProbes is also immune to guest attempts to fool it. For instance, malware often tries to change in-guest instrumentation tools to make itself undetectable. Since the VM/hypervisor trust boundary protects vprobes, it is immune to this weirdness.
# VProbes is neutral as to the identity of the guest; since it's machine-level, you can use the same tools for Windows, Linux, Solaris, FreeBSD, MacOS, etc. To the extent the preload scripts work, even some common, but OS-specific, notions, like processes, can be captured.


The big negatives all boil down to the same fundamental problem: the machine abstraction level is sometimes very far away from the application abstraction level. If it's a java application running, for instance, VProbes will sit there telling you: "java.exe is running!" Well, no kidding; you probably wanted to know, e.g., which method invocation it was in. VMware is thinking about ways to bridge that gap, but alas, there's very little to offer for serious discussion at this time.

==== External links ====
* [http://blogs.vmware.com/vmtn/2008/06/introducing-vpr.html Video introducing VProbes]
* [http://communities.vmware.com/thread/194591 Vprobe-toolkit in Windows]

[[Category:SDK]]</text>
    <sha1>cdbac56fca0509808af9f3850ad85d0f3b133760</sha1>
  </revision>
  <revision>
    <id>818</id>
    <parentid>817</parentid>
    <timestamp>2009-02-19T16:33:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added new catogory for tracking open source projects from VMware</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2755" xml:space="preserve">==== VProbe Toolkit ====

This provides an interactive, programmer-friendly interface to VMware's VProbes facility. VProbes is a safe, dynamic technology for instrumenting software running in virtual machines, and the software stack itself. 


* [http://sourceforge.net/projects/vprobe-toolkit/ Sourceforge project vprobe-toolkit]
* [http://www.vmware.com/products/beta/ws/vprobes_reference.pdf official reference]
* [http://www.vmware.com/download/ws/ download]
* [http://communities.vmware.com/community/developer/vprobes VProbes community]

==== Advantages and disadvantages of using VProbe ====
Debugging your applications/kernel from outside the VM has some big pluses, and some big minuses. On the pro 

# Most importantly, VProbes is '''safe'''. Using a kernel debugger or something from within a guest provides some very dangerous opportunities: e.g., you could poke a hole in a critical guest memory structure. Also, kernel debuggers usually stop the target program to allow inspection. VProbes keeps things moving along while data is harvested, so it can be used even on mission-critical, highly available systems.
# VProbes doesn't rely on any in-guest tools. If the target is, for instance, an appliance that doesn't even have a login shell, let alone /usr/bin/top, VProbes works no better or worse.
# It doesn't care what state the guest is in. If the guest is hard hung, or is swapping too hard for a shell to come up, or whatever, VProbes can be a "tool of last resort" to try to harvest information.
# VProbes is also immune to guest attempts to fool it. For instance, malware often tries to change in-guest instrumentation tools to make itself undetectable. Since the VM/hypervisor trust boundary protects vprobes, it is immune to this weirdness.
# VProbes is neutral as to the identity of the guest; since it's machine-level, you can use the same tools for Windows, Linux, Solaris, FreeBSD, MacOS, etc. To the extent the preload scripts work, even some common, but OS-specific, notions, like processes, can be captured.


The big negatives all boil down to the same fundamental problem: the machine abstraction level is sometimes very far away from the application abstraction level. If it's a java application running, for instance, VProbes will sit there telling you: "java.exe is running!" Well, no kidding; you probably wanted to know, e.g., which method invocation it was in. VMware is thinking about ways to bridge that gap, but alas, there's very little to offer for serious discussion at this time.

==== External links ====
* [http://blogs.vmware.com/vmtn/2008/06/introducing-vpr.html Video introducing VProbes]
* [http://communities.vmware.com/thread/194591 Vprobe-toolkit in Windows]

[[Category:SDK]] [[Category: VMware OSS]]</text>
    <sha1>b814d690efe0c46f24588a0a98b446e80788a4d7</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Vassert Linux SDK</title>
  <ns>0</ns>
  <id>13</id>
  <revision>
    <id>819</id>
    <parentid>21</parentid>
    <timestamp>2009-02-19T16:34:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="327" xml:space="preserve">==== Vassert Linux SDK ====

Vassert is a new feature from VMware Workstation. It is promising for developers to enhance code reliablity with less run-time cost. This project is a library to enable vassert usage under Linux guest os. 

http://sourceforge.net/projects/vassertlinuxsdk/

[[Category:SDK]] [[Category: VMware OSS]]</text>
    <sha1>8cb8e204877aef4d3b593f0de5252c1afebc3540</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>SDK</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>822</id>
    <parentid>423</parentid>
    <timestamp>2009-02-19T16:37:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="296" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

[[VMware Icons]]

==== External links ====

[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's


[[Category: SDK]]</text>
    <sha1>cbe18b5b5e17f2c33dbc3a5559aa333ba4bb6c6f</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>VMware Icons</title>
  <ns>0</ns>
  <id>423</id>
  <revision>
    <id>823</id>
    <timestamp>2009-02-19T16:41:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== VMware Icons ====  VMware icons and powerpoint backgrounds that you can use in your own products. Please do check out the guidelines as well.  http://communities.vmware.com/blogs/Deve...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="310" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints disappeared while I posted this... hmm... they might come back :)</text>
    <sha1>f28f8a20e2cec9b9b8e3cc9f99f7a7bddd047a1c</sha1>
  </revision>
  <revision>
    <id>824</id>
    <parentid>823</parentid>
    <timestamp>2009-02-19T16:50:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="326" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints disappeared while I posted this... hmm... they might come back :)

[[VMware OSS]]</text>
    <sha1>bee73baa73d73794b6a4774606e25cd8b7cc4e24</sha1>
  </revision>
  <revision>
    <id>827</id>
    <parentid>824</parentid>
    <timestamp>2009-02-19T17:27:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="335" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints disappeared while I posted this... hmm... they might come back :)

[[Category:VMware OSS]]</text>
    <sha1>8d454360033daa2a3a9ff9dab2177cc43416f014</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Category:VMware OSS</title>
  <ns>14</ns>
  <id>425</id>
  <revision>
    <id>826</id>
    <timestamp>2009-02-19T17:26:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: This category contains pages that directly relate to open source software (OSS) released by VMware.  There's a growing number of projects here and it is good to be able to check things out...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="216" xml:space="preserve">This category contains pages that directly relate to open source software (OSS) released by VMware.

There's a growing number of projects here and it is good to be able to check things out "from the source" directly.</text>
    <sha1>bc239f9d90a7b84cad08f483cb9da8fa3c761c81</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>LibView</title>
  <ns>0</ns>
  <id>426</id>
  <revision>
    <id>829</id>
    <timestamp>2009-02-19T17:49:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page:  libview is VMware's Incredibly Exciting Widgets, a useful collection of GTK+ widgets used within VMware products, free for everybody's use.   http://sourceforge.net/projects/view/  [[Cate...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="206" xml:space="preserve">
libview is VMware's Incredibly Exciting Widgets, a useful collection of GTK+ widgets used within VMware products, free for everybody's use. 

http://sourceforge.net/projects/view/

[[Category: VMware OSS]]</text>
    <sha1>32a027cc2de6e47f0b57f64f19b68ff417d13066</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Open-vm-tools</title>
  <ns>0</ns>
  <id>427</id>
  <revision>
    <id>831</id>
    <timestamp>2009-02-19T17:56:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ==== Open Virtual Machine Tools ====  The Open Virtual Machine Tools project aims to provide a suite of open source virtualization utilities and drivers to improve the functionality and us...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="469" xml:space="preserve">==== Open Virtual Machine Tools ====

The Open Virtual Machine Tools project aims to provide a suite of open source virtualization utilities and drivers to improve the functionality and user experience of virtualization. The project currently runs in guest operating systems under VMware hypervisors.

* [http://sourceforge.net/projects/open-vm-tools/ sourceforge open-vm-tools project page]

* [http://open-vm-tools.sourceforge.net/ homepage]

[[Category: VMware OSS]]</text>
    <sha1>8df6558fe9b9d33d9259662f695d386f751bba44</sha1>
  </revision>
  <revision>
    <id>832</id>
    <parentid>831</parentid>
    <timestamp>2009-02-19T17:57:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="571" xml:space="preserve">==== Open Virtual Machine Tools ====


The Open Virtual Machine Tools (open-vm-tools) are the open source implementation of VMware Tools.

The Open Virtual Machine Tools project aims to provide a suite of open source virtualization utilities and drivers to improve the functionality and user experience of virtualization. The project currently runs in guest operating systems under VMware hypervisors.

* [http://sourceforge.net/projects/open-vm-tools/ sourceforge open-vm-tools project page]

* [http://open-vm-tools.sourceforge.net/ homepage]

[[Category: VMware OSS]]</text>
    <sha1>df9bd7bc88e12483c00422c15f8eca8094f59ec2</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>833</id>
    <parentid>797</parentid>
    <timestamp>2009-02-20T03:04:53Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2650" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

[[APC/APCUPSD ESX/ESXi Host shutdown script]]

==== Perl scripts ====
[[Recover vmx from log file]]</text>
    <sha1>0e8ed082502ca95e69787e6d458b76668bb894c4</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>APC/APCUPSD ESX/ESXi Host shutdown script</title>
  <ns>0</ns>
  <id>428</id>
  <revision>
    <id>834</id>
    <timestamp>2009-02-20T03:07:12Z</timestamp>
    <contributor>
      <username>Lamw</username>
      <id>5</id>
    </contributor>
    <comment>New page: '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoShutdown.pl ghettoShutdown.pl]  '''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/upsVIShutdown.pl ups...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="837" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoShutdown.pl ghettoShutdown.pl]

'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/upsVIShutdown.pl upsVIShutdown.pl]

'''Compatible with''': ESX/ESXi 3.5+

Please find more details located at: http://communities.vmware.com/docs/DOC-9531

This script is similar to Joseph’s work [http://viops.vmware.com/home/docs/DOC-1341 How to configure ESXi to shutdown using an APC SmartUPS] although it will not necessitate enabling the unsupported SSH console on the ESXi hosts. This is made possible by utilizing the VI Perl Toolkit to communicate with the ESXi hosts. The only possible drawback however is that next revision of ESXi may disallow write operations and require that the user purchase ESXi license(s) to make full use of the VI API (read/write).</text>
    <sha1>d2fb0cdac9dbf1c5496f1cc390f9c3f5b94b7120</sha1>
  </revision>
  <revision>
    <id>835</id>
    <parentid>834</parentid>
    <timestamp>2009-02-20T19:17:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="887" xml:space="preserve">'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/ghettoShutdown.pl ghettoShutdown.pl]

'''Download script''': [http://www.engr.ucsb.edu/~duonglt/vmware/upsVIShutdown.pl upsVIShutdown.pl]

'''Compatible with''': ESX/ESXi 3.5+

Please find more details located at: http://communities.vmware.com/docs/DOC-9531

This script is similar to Joseph’s work [http://viops.vmware.com/home/docs/DOC-1341 How to configure ESXi to shutdown using an APC SmartUPS] although it will not necessitate enabling the unsupported SSH console on the ESXi hosts. This is made possible by utilizing the VI Perl Toolkit to communicate with the ESXi hosts. The only possible drawback however is that next revision of ESXi may disallow write operations and require that the user purchase ESXi license(s) to make full use of the VI API (read/write).

[[Category: Host Management]] [[Category: Perl]]</text>
    <sha1>64dbf71c0e887b904017963b8019900807bf9288</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>836</id>
    <parentid>540</parentid>
    <timestamp>2009-03-03T13:20:00Z</timestamp>
    <contributor>
      <username>RobMokkink</username>
      <id>13</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="853" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [ http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]</text>
    <sha1>0ac8b9853bfc3f76703e16a4e0d7cf587411ecff</sha1>
  </revision>
  <revision>
    <id>837</id>
    <parentid>836</parentid>
    <timestamp>2009-03-03T13:20:24Z</timestamp>
    <contributor>
      <username>RobMokkink</username>
      <id>13</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="852" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]</text>
    <sha1>35df1acd857844747fe2c2eea8e86b2e48555c5f</sha1>
  </revision>
  <revision>
    <id>838</id>
    <parentid>837</parentid>
    <timestamp>2009-03-24T12:15:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="920" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]</text>
    <sha1>4c119ba2aca878e48da453d643b8a64875793bd8</sha1>
  </revision>
  <revision>
    <id>839</id>
    <parentid>838</parentid>
    <timestamp>2009-03-24T12:16:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="937" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]</text>
    <sha1>4278bf98eb0b3f75c592c76567bb0b68f7a5c610</sha1>
  </revision>
  <revision>
    <id>841</id>
    <parentid>839</parentid>
    <timestamp>2009-03-24T12:19:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added categories</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="987" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>8258f8a46d1999ef38c5c691dc7652670f41a2aa</sha1>
  </revision>
  <revision>
    <id>848</id>
    <parentid>841</parentid>
    <timestamp>2009-03-24T12:46:00Z</timestamp>
    <contributor>
      <username>Virtu-al</username>
      <id>14</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="988" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>0379cef2e1eccc4fd1143659d6c2b59e05a8b1e0</sha1>
  </revision>
  <revision>
    <id>853</id>
    <parentid>848</parentid>
    <timestamp>2009-04-01T08:18:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1014" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>cffa8bb704e529eafd6b5e1ecf1815edfc9bf4ee</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Powershell CMDLET list</title>
  <ns>0</ns>
  <id>429</id>
  <revision>
    <id>840</id>
    <timestamp>2009-03-24T12:17:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>CMDLET list, content is from Alan Renouf</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3778" xml:space="preserve">The following cmdlets currently exist in the latest version of the VI Toolkit, follow the link for a description and example of how to use these.  If you have a better example or some more information about the cmdlet why not share your knowledge by editing the page.

This is still work in progress !

[[Add-VMHost]]

[[Add-VMHostNtpServer]]

[[Connect-VIServer]]

[[Disconnect-VIServer]]

[[Dismount-Tools]]

[[Get-CDDrive]]

[[Get-Cluster]]

[[Get-Datacenter]]

[[Get-Datastore]]

[[Get-DrsRule]]

[[Get-FloppyDrive]]

[[Get-Folder]]

[[Get-HardDisk]]

[[Get-Inventory]]

[[Get-Log]]

[[Get-LogType]]

[[Get-NetworkAdapter]]

[[Get-OSCustomizationSpec]]

[[Get-ResourcePool]]

[[Get-ScsiLun]]

[[Get-ScsiLunPath]]

[[Get-Snapshot]]

[[Get-Stat]]

[[Get-StatInterval]]

[[Get-StatType]]

[[Get-Task]]

[[Get-Template]]

[[Get-VICredentialStoreItem]]

[[Get-VIEvent]]

[[Get-View]]

[[Get-VIObjectByVIView]]

[[Get-VirtualPortGroup]]

[[Get-VirtualSwitch]]

[[Get-VIToolkitConfiguration]]

[[Get-VIToolkitVersion]]

[[Get-VM]]

[[Get-VMGuest]]

[[Get-VMHost]]

[[Get-VMHostAccount]]

[[Get-VMHostAdvancedConfiguration]]

[[Get-VMHostDiagnosticPartition]]

[[Get-VMHostFirewallDefaultPolicy]]

[[Get-VMHostFirewallException]]

[[Get-VMHostFirmware]]

[[Get-VMHostModule]]

[[Get-VMHostNetwork]]

[[Get-VMHostNtpServer]]

[[Get-VMHostService]]

[[Get-VMHostSnmp]]

[[Get-VMHostStartPolicy]]

[[Get-VMHostStorage]]

[[Get-VMHostSysLogServer]]

[[Get-VMResourceConfiguration]]

[[Get-VMStartPolicy]]

[[Invoke-VMScript]]

[[Mount-Tools]]

[[Move-Cluster]]

[[Move-Datacenter]]

[[Move-Folder]]

[[Move-Inventory]]

[[Move-ResourcePool]]

[[Move-VM]]

[[Move-VMHost]]

[[New-CDDrive]]

[[New-Cluster]]

[[New-CustomField]]

[[New-Datacenter]]

[[New-Datastore]]

[[New-DrsRule]]

[[New-FloppyDrive]]

[[New-Folder]]

[[New-HardDisk]]

[[New-NetworkAdapter]]

[[New-OSCustomizationSpec]]

[[New-ResourcePool]]

[[New-Snapshot]]

[[New-StatInterval]]

[[New-Template]]

[[New-VICredentialStoreItem]]

[[New-VirtualPortGroup]]

[[New-VirtualSwitch]]

[[New-VM]]

[[New-VMHostAccount]]

[[New-VMHostNetworkAdapter]]

[[Remove-CDDrive]]

[[Remove-Cluster]]

[[Remove-CustomField]]

[[Remove-Datacenter]]

[[Remove-Datastore]]

[[Remove-DrsRule]]

[[Remove-FloppyDrive]]

[[Remove-Folder]]

[[Remove-Inventory]]

[[Remove-NetworkAdapter]]

[[Remove-OSCustomizationSpec]]

[[Remove-ResourcePool]]

[[Remove-Snapshot]]

[[Remove-StatInterval]]

[[Remove-Template]]

[[Remove-VICredentialStoreItem]]

[[Remove-VirtualPortGroup]]

[[Remove-VirtualSwitch]]

[[Remove-VM]]

[[Remove-VMHost]]

[[Remove-VMHostAccount]]

[[Remove-VMHostNetworkAdapter]]

[[Remove-VMHostNtpServer]]

[[Restart-VMGuest]]

[[Restart-VMHostService]]

[[Set-CDDrive]]

[[Set-Cluster]]

[[Set-CustomField]]

[[Set-Datacenter]]

[[Set-Datastore]]

[[Set-DrsRule]]

[[Set-FloppyDrive]]

[[Set-Folder]]

[[Set-HardDisk]]

[[Set-NetworkAdapter]]

[[Set-OSCustomizationSpec]]

[[Set-ResourcePool]]

[[Set-ScsiLun]]

[[Set-ScsiLunPath]]

[[Set-Snapshot]]

[[Set-StatInterval]]

[[Set-Template]]

[[Set-VirtualPortGroup]]

[[Set-VirtualSwitch]]

[[Set-VIToolkitConfiguration]]

[[Set-VM]]

[[Set-VMHost]]

[[Set-VMHostAccount]]

[[Set-VMHostAdvancedConfiguration]]

[[Set-VMHostDiagnosticPartition]]

[[Set-VMHostFirewallDefaultPolicy]]

[[Set-VMHostFirewallException]]

[[Set-VMHostFirmware]]

[[Set-VMHostModule]]

[[Set-VMHostNetwork]]

[[Set-VMHostNetworkAdapter]]

[[Set-VMHostService]]

[[Set-VMHostSnmp]]

[[Set-VMHostStartPolicy]]

[[Set-VMHostSysLogServer]]

[[Set-VMResourceConfiguration]]

[[Set-VMStartPolicy]]

[[Shutdown-VMGuest]]

[[Start-VM]]

[[Start-VMHostService]]

[[Stop-Task]]

[[Stop-VM]]

[[Stop-VMHostService]]

[[Suspend-VM]]

[[Suspend-VMGuest]]

[[Test-VMHostSnmp]]

[[Update-Tools]]

[[Wait-Task]]</text>
    <sha1>7c90ff78d19a2fd6f59be17ff27105fbd0599eec</sha1>
  </revision>
  <revision>
    <id>842</id>
    <parentid>840</parentid>
    <timestamp>2009-03-24T12:20:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3828" xml:space="preserve">The following cmdlets currently exist in the latest version of the VI Toolkit, follow the link for a description and example of how to use these.  If you have a better example or some more information about the cmdlet why not share your knowledge by editing the page.

This is still work in progress !

[[Add-VMHost]]

[[Add-VMHostNtpServer]]

[[Connect-VIServer]]

[[Disconnect-VIServer]]

[[Dismount-Tools]]

[[Get-CDDrive]]

[[Get-Cluster]]

[[Get-Datacenter]]

[[Get-Datastore]]

[[Get-DrsRule]]

[[Get-FloppyDrive]]

[[Get-Folder]]

[[Get-HardDisk]]

[[Get-Inventory]]

[[Get-Log]]

[[Get-LogType]]

[[Get-NetworkAdapter]]

[[Get-OSCustomizationSpec]]

[[Get-ResourcePool]]

[[Get-ScsiLun]]

[[Get-ScsiLunPath]]

[[Get-Snapshot]]

[[Get-Stat]]

[[Get-StatInterval]]

[[Get-StatType]]

[[Get-Task]]

[[Get-Template]]

[[Get-VICredentialStoreItem]]

[[Get-VIEvent]]

[[Get-View]]

[[Get-VIObjectByVIView]]

[[Get-VirtualPortGroup]]

[[Get-VirtualSwitch]]

[[Get-VIToolkitConfiguration]]

[[Get-VIToolkitVersion]]

[[Get-VM]]

[[Get-VMGuest]]

[[Get-VMHost]]

[[Get-VMHostAccount]]

[[Get-VMHostAdvancedConfiguration]]

[[Get-VMHostDiagnosticPartition]]

[[Get-VMHostFirewallDefaultPolicy]]

[[Get-VMHostFirewallException]]

[[Get-VMHostFirmware]]

[[Get-VMHostModule]]

[[Get-VMHostNetwork]]

[[Get-VMHostNtpServer]]

[[Get-VMHostService]]

[[Get-VMHostSnmp]]

[[Get-VMHostStartPolicy]]

[[Get-VMHostStorage]]

[[Get-VMHostSysLogServer]]

[[Get-VMResourceConfiguration]]

[[Get-VMStartPolicy]]

[[Invoke-VMScript]]

[[Mount-Tools]]

[[Move-Cluster]]

[[Move-Datacenter]]

[[Move-Folder]]

[[Move-Inventory]]

[[Move-ResourcePool]]

[[Move-VM]]

[[Move-VMHost]]

[[New-CDDrive]]

[[New-Cluster]]

[[New-CustomField]]

[[New-Datacenter]]

[[New-Datastore]]

[[New-DrsRule]]

[[New-FloppyDrive]]

[[New-Folder]]

[[New-HardDisk]]

[[New-NetworkAdapter]]

[[New-OSCustomizationSpec]]

[[New-ResourcePool]]

[[New-Snapshot]]

[[New-StatInterval]]

[[New-Template]]

[[New-VICredentialStoreItem]]

[[New-VirtualPortGroup]]

[[New-VirtualSwitch]]

[[New-VM]]

[[New-VMHostAccount]]

[[New-VMHostNetworkAdapter]]

[[Remove-CDDrive]]

[[Remove-Cluster]]

[[Remove-CustomField]]

[[Remove-Datacenter]]

[[Remove-Datastore]]

[[Remove-DrsRule]]

[[Remove-FloppyDrive]]

[[Remove-Folder]]

[[Remove-Inventory]]

[[Remove-NetworkAdapter]]

[[Remove-OSCustomizationSpec]]

[[Remove-ResourcePool]]

[[Remove-Snapshot]]

[[Remove-StatInterval]]

[[Remove-Template]]

[[Remove-VICredentialStoreItem]]

[[Remove-VirtualPortGroup]]

[[Remove-VirtualSwitch]]

[[Remove-VM]]

[[Remove-VMHost]]

[[Remove-VMHostAccount]]

[[Remove-VMHostNetworkAdapter]]

[[Remove-VMHostNtpServer]]

[[Restart-VMGuest]]

[[Restart-VMHostService]]

[[Set-CDDrive]]

[[Set-Cluster]]

[[Set-CustomField]]

[[Set-Datacenter]]

[[Set-Datastore]]

[[Set-DrsRule]]

[[Set-FloppyDrive]]

[[Set-Folder]]

[[Set-HardDisk]]

[[Set-NetworkAdapter]]

[[Set-OSCustomizationSpec]]

[[Set-ResourcePool]]

[[Set-ScsiLun]]

[[Set-ScsiLunPath]]

[[Set-Snapshot]]

[[Set-StatInterval]]

[[Set-Template]]

[[Set-VirtualPortGroup]]

[[Set-VirtualSwitch]]

[[Set-VIToolkitConfiguration]]

[[Set-VM]]

[[Set-VMHost]]

[[Set-VMHostAccount]]

[[Set-VMHostAdvancedConfiguration]]

[[Set-VMHostDiagnosticPartition]]

[[Set-VMHostFirewallDefaultPolicy]]

[[Set-VMHostFirewallException]]

[[Set-VMHostFirmware]]

[[Set-VMHostModule]]

[[Set-VMHostNetwork]]

[[Set-VMHostNetworkAdapter]]

[[Set-VMHostService]]

[[Set-VMHostSnmp]]

[[Set-VMHostStartPolicy]]

[[Set-VMHostSysLogServer]]

[[Set-VMResourceConfiguration]]

[[Set-VMStartPolicy]]

[[Shutdown-VMGuest]]

[[Start-VM]]

[[Start-VMHostService]]

[[Stop-Task]]

[[Stop-VM]]

[[Stop-VMHostService]]

[[Suspend-VM]]

[[Suspend-VMGuest]]

[[Test-VMHostSnmp]]

[[Update-Tools]]

[[Wait-Task]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>68d09d811855852717f8f29c14dca2f88c50c1e7</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Get-VMHost</title>
  <ns>0</ns>
  <id>430</id>
  <revision>
    <id>843</id>
    <timestamp>2009-03-24T12:24:07Z</timestamp>
    <contributor>
      <username>Virtu-al</username>
      <id>14</id>
    </contributor>
    <comment>New page: NAME     Get-VMHost      SYNOPSIS     Gets from a VMware Infrastructure server one or more virtual machine hosts.      SYNTAX     Get-VMHost [-Datastore &lt;Datastore[]&gt;] [-State &lt;VMHostState...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6164" xml:space="preserve">NAME
    Get-VMHost
    
SYNOPSIS
    Gets from a VMware Infrastructure server one or more virtual machine hosts.
    
SYNTAX
    Get-VMHost [-Datastore &lt;Datastore[]&gt;] [-State &lt;VMHostState[]&gt;] [-Location &lt;
    VIContainer[]&gt;] [[-Name] &lt;String[]&gt;] [-Id &lt;String[]&gt;] [-NoRecursion] [-Serv
    er &lt;VIServer[]&gt;] [&lt;CommonParameters&gt;]
    
    Get-VMHost [-VM &lt;VirtualMachine[]&gt;] [-ResourcePool &lt;ResourcePool[]&gt;] [-Data
    store &lt;Datastore[]&gt;] [-Location &lt;VIContainer[]&gt;] [[-Name] &lt;String[]&gt;] [-Id 
    &lt;String[]&gt;] [-NoRecursion] [-Server &lt;VIServer[]&gt;] [&lt;CommonParameters&gt;]
    
    
DETAILED DESCRIPTION
    Gets from a VMware Infrastructure server one or more objects that represent
     virtual machine hosts. Returns the set of virtual machine hosts that corre
    spond to the filter criteria provided by the cmdlet parameters.  To specify
     a server different from the default one, use the -Server parameter.
    When connected directly to an ESX host, the Name property of the returned V
    MHost object  contains either the DNS name of the host, or the IP of the ES
    X host, depending on which of them was specified when connecting with Conne
    ct-VIServer.
    

PARAMETERS
    -Datastore &lt;Datastore[]&gt;
        If set, the command retrieves the virtual machine hosts associated with
         one or more of the specified datastores. Passing values to this parame
        ter through a pipeline is deprecated and will be removed after one of t
        he following releases.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -State &lt;VMHostState[]&gt;
        Specifies the state of the virtual machine hosts to be returned by the 
        Get-VMHost command. It must be one of the following: Connected, Disconn
        ected, NotResponding, Maintenance.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    -Location &lt;VIContainer[]&gt;
        Specifies one or more virtual infrastructure container objects (e.g. fo
        lders, datacenters, clusters) to search for virtual machine hosts.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -Name &lt;String[]&gt;
        Specifies one or more names of virtual machine hosts to get. Use commas
         to separate multiple names. Using wildcards is supported.
        
        Required?                    false
        Position?                    1
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  true
        
    -Id &lt;String[]&gt;
        Specifies one or more virtual machine hosts by Id. To specify multiple 
        Ids, use commas to separate the Ids.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  true
        
    -NoRecursion
        Get-VMHost searches recursively from any provided starting point. Setti
        ng this parameter disables the command recursive behavior.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    -Server &lt;VIServer[]&gt;
        A VMware Infrastructure server to apply the command on. If no value is 
        given to this parameter, the command takes the server currently specifi
        ed in the $DefaultVIServer variable.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    -VM &lt;VirtualMachine[]&gt;
        Specifies one or more virtual machines running on the virtual machine h
        osts retrieved by the command.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -ResourcePool &lt;ResourcePool[]&gt;
        Specifies one or more resource pools associated with the standalone vir
        tual machine hosts retrieved by the command.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    &lt;CommonParameters&gt;
        This cmdlet supports the common parameters: -Verbose, -Debug,
        -ErrorAction, -ErrorVariable, -WarningAction, -WarningVariable,
        -OutBuffer and -OutVariable. For more information, type,
        "get-help about_commonparameters".
    
INPUT TYPE
    
     
RETURN TYPE
    VMHost[]
     
    
NOTES
    
    
        When connected directly to ESX, the Name property of the returned VMHos
        t object  contains either the DNS name of the host, or the
        IP of the ESX, depending on which of them was specified when connecting
         with Connect-VIServer.
    
    --------------  Example 1 --------------
    
    C:\PS&gt;Get-VMHost -Location (Get-Datacenter -Name New) -VM (Get-VM -Name "MS
     Win XP SP2") | fl
    
    
    Retrieves the virtual machine host, which is located in the New datacenter 
    and on which the MS Win XP SP2 virtual machine is hosted.
    
    
    State        : Connected
    CustomFields : {}
    ID           : HostSystem-host-8
    Name         : 10.23.113.212
    
    
RELATED LINKS
    [[Remove-VMHost]]
    [[Move-VMHost]]
    [[Set-VMHost]]
    [[Add-VMHost]]</text>
    <sha1>4331a08afd0a1b42e4e0e833740d424caa4eabbd</sha1>
  </revision>
  <revision>
    <id>849</id>
    <parentid>843</parentid>
    <timestamp>2009-03-24T13:24:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6164" xml:space="preserve">=====NAME=====
    Get-VMHost
    
SYNOPSIS
    Gets from a VMware Infrastructure server one or more virtual machine hosts.
    
SYNTAX
    Get-VMHost [-Datastore &lt;Datastore[]&gt;] [-State &lt;VMHostState[]&gt;] [-Location &lt;
    VIContainer[]&gt;] [[-Name] &lt;String[]&gt;] [-Id &lt;String[]&gt;] [-NoRecursion] [-Serv
    er &lt;VIServer[]&gt;] [&lt;CommonParameters&gt;]
    
    Get-VMHost [-VM &lt;VirtualMachine[]&gt;] [-ResourcePool &lt;ResourcePool[]&gt;] [-Data
    store &lt;Datastore[]&gt;] [-Location &lt;VIContainer[]&gt;] [[-Name] &lt;String[]&gt;] [-Id 
    &lt;String[]&gt;] [-NoRecursion] [-Server &lt;VIServer[]&gt;] [&lt;CommonParameters&gt;]
    
    
=====DETAILED DESCRIPTION=====
Gets from a VMware Infrastructure server one or more objects that represent virtual machine hosts. Returns the set of virtual machine hosts that correspond to the filter criteria provided by the cmdlet parameters.  To specify a server different from the default one, use the -Server parameter.

When connected directly to an ESX host, the Name property of the returned VMHost object  contains either the DNS name of the host, or the IP of the ESX host, depending on which of them was specified when connecting with Connect-VIServer.
    

PARAMETERS
    -Datastore &lt;Datastore[]&gt;
        If set, the command retrieves the virtual machine hosts associated with
         one or more of the specified datastores. Passing values to this parameter 
        through a pipeline is deprecated and will be removed after one of the 
        following releases.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -State &lt;VMHostState[]&gt;
        Specifies the state of the virtual machine hosts to be returned by the 
        Get-VMHost command. It must be one of the following: Connected, Disconn
        ected, NotResponding, Maintenance.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    -Location &lt;VIContainer[]&gt;
        Specifies one or more virtual infrastructure container objects (e.g. folders, 
        datacenters, clusters) to search for virtual machine hosts.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -Name &lt;String[]&gt;
        Specifies one or more names of virtual machine hosts to get. Use commas
         to separate multiple names. Using wildcards is supported.
        
        Required?                    false
        Position?                    1
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  true
        
    -Id &lt;String[]&gt;
        Specifies one or more virtual machine hosts by Id. To specify multiple 
        Ids, use commas to separate the Ids.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  true
        
    -NoRecursion
        Get-VMHost searches recursively from any provided starting point. Setting 
        this parameter disables the command recursive behavior.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    -Server &lt;VIServer[]&gt;
        A VMware Infrastructure server to apply the command on. If no value is 
        given to this parameter, the command takes the server currently specified 
        in the $DefaultVIServer variable.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    -VM &lt;VirtualMachine[]&gt;
        Specifies one or more virtual machines running on the virtual machine hosts 
        retrieved by the command.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -ResourcePool &lt;ResourcePool[]&gt;
        Specifies one or more resource pools associated with the standalone virtual 
        machine hosts retrieved by the command.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    &lt;CommonParameters&gt;
        This cmdlet supports the common parameters: -Verbose, -Debug,
        -ErrorAction, -ErrorVariable, -WarningAction, -WarningVariable,
        -OutBuffer and -OutVariable. For more information, type,
        "get-help about_commonparameters".
    
INPUT TYPE
    
     
RETURN TYPE
    VMHost[]
     
    
=====NOTES=====
    
    
When connected directly to ESX, the Name property of the returned VMHost object  contains either the DNS name of the host, or the IP of the ESX, depending on which of them was specified when connecting with Connect-VIServer.
    
    --------------  Example 1 --------------
    
    C:\PS&gt;Get-VMHost -Location (Get-Datacenter -Name New) -VM (Get-VM -Name "MS Win XP SP2") | fl
    
Retrieves the virtual machine host, which is located in the New datacenter and on which the MS Win XP SP2 virtual machine is hosted.
    
    
    State        : Connected
    CustomFields : {}
    ID           : HostSystem-host-8
    Name         : 10.23.113.212
    
    
=====RELATED LINKS=====
    [[Remove-VMHost]]
    [[Move-VMHost]]
    [[Set-VMHost]]
    [[Add-VMHost]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>2db494559f1bdec5aacbd1fcaf5acf2cd2f0cc71</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Get-VM</title>
  <ns>0</ns>
  <id>431</id>
  <revision>
    <id>844</id>
    <timestamp>2009-03-24T12:24:46Z</timestamp>
    <contributor>
      <username>Virtu-al</username>
      <id>14</id>
    </contributor>
    <comment>New page: NAME     Get-VM      SYNOPSIS     Gets from a VMware Infrastructure server one or more virtual machines.      SYNTAX     Get-VM [-Datastore &lt;Datastore[]&gt;] [-Location &lt;VIContainer[]&gt;] [[-Na...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4351" xml:space="preserve">NAME
    Get-VM
    
SYNOPSIS
    Gets from a VMware Infrastructure server one or more virtual machines.
    
SYNTAX
    Get-VM [-Datastore &lt;Datastore[]&gt;] [-Location &lt;VIContainer[]&gt;] [[-Name] &lt;Str
    ing[]&gt;] [-Id &lt;String[]&gt;] [-NoRecursion] [-Server &lt;VIServer[]&gt;] [&lt;CommonPara
    meters&gt;]
    
    
DETAILED DESCRIPTION
    Gets from a VMware Infrastructure server one or more objects that represent
     virtual machines. Returns a set of virtual machines that correspond to the
     filter criteria provided by the cmdlet parameters. For virtual machines wi
    th multiple NICs and therefore multiple IP addresses, the "IPAddress" prope
    rty of the VMGuest object contains all IP addresses of the virtual machine.
     The IP at position 0 is the primary IP address.
    

PARAMETERS
    -Datastore &lt;Datastore[]&gt;
        Gets the virtual machines associated with one or more of the specified 
        datastores. Passing values to this parameter through a pipeline is depr
        ecated and will be removed in one of the following releases.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -Location &lt;VIContainer[]&gt;
        Specifies one or more virtual infrastructure container objects (e.g. fo
        lders, datacenters, clusters) to search for virtual machines.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -Name &lt;String[]&gt;
        Specifies one or more names of virtual machine names to get. Use commas
         to separate multiple names. Using wildcards is supported.
        
        Required?                    false
        Position?                    1
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  true
        
    -Id &lt;String[]&gt;
        Specifies one or more virtual machine hosts by ID. Use commas to separa
        te multiple IDs.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  true
        
    -NoRecursion
        Get-VM searches recursively from any provided starting point. Setting t
        his parameter disables the command recursive behavior.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    -Server &lt;VIServer[]&gt;
        One or more virtual Infrastructure servers to apply the command on. If 
        no value is given to this parameter, the command takes the server curre
        ntly specified in the $DefaultVIServer variable.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    &lt;CommonParameters&gt;
        This cmdlet supports the common parameters: -Verbose, -Debug,
        -ErrorAction, -ErrorVariable, -WarningAction, -WarningVariable,
        -OutBuffer and -OutVariable. For more information, type,
        "get-help about_commonparameters".
    
INPUT TYPE
    
     
RETURN TYPE
    VirtualMachine[]
     
    
NOTES
    
    
    --------------  EXAMPLE 1 --------------
    
    C:\PS&gt;Get-VM
    
    
    Retrieves information about all of the virtual machines registered with the
     currently selected VMware Infrastructure server.
    
    
    --------------  EXAMPLE 2 --------------
    
    C:\PS&gt;Get-VM -Name webTier*
    
    
    This command retrieves information about all virtual machines registered wi
    th the currently-selected VMware Infrastructure server whose names begin wi
    th "webTier."
    
    
RELATED LINKS
    [[Remove-VM]] 
    [[New-VM]] 
    [[Set-VM]] 
    [[Move-VM]] 
    [[Start-VM]] 
    [[Stop-VM]] 
    [[Suspend-VM]]</text>
    <sha1>b44d94c8815609e5e2b429a2c9ede6f5f21694d1</sha1>
  </revision>
  <revision>
    <id>845</id>
    <parentid>844</parentid>
    <timestamp>2009-03-24T12:32:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>applied a bit of formatting, added categories</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4400" xml:space="preserve">=====NAME=====
    Get-VM
    
SYNOPSIS
    Gets from a VMware Infrastructure server one or more virtual machines.
    
SYNTAX
    Get-VM [-Datastore &lt;Datastore[]&gt;] [-Location &lt;VIContainer[]&gt;] [[-Name] &lt;Str
    ing[]&gt;] [-Id &lt;String[]&gt;] [-NoRecursion] [-Server &lt;VIServer[]&gt;] [&lt;CommonPara
    meters&gt;]
    
    
=====DETAILED DESCRIPTION=====
Gets from a VMware Infrastructure server one or more objects that represent virtual machines. Returns a set of virtual machines that correspond to the filter criteria provided by the cmdlet parameters. For virtual machines with multiple NICs and therefore multiple IP addresses, the "IPAddress" property of the VMGuest object contains all IP addresses of the virtual machine.

The IP at position 0 is the primary IP address.
    

PARAMETERS
    -Datastore &lt;Datastore[]&gt;
        Gets the virtual machines associated with one or more of the specified datastores. 
        Passing values to this parameter through a pipeline is deprecated 
        and will be removed in one of the following releases.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -Location &lt;VIContainer[]&gt;
        Specifies one or more virtual infrastructure container objects (e.g. folders, 
        datacenters, clusters) to search for virtual machines.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       true (ByValue)
        Accept wildcard characters?  true
        
    -Name &lt;String[]&gt;
        Specifies one or more names of virtual machine names to get. Use commas
         to separate multiple names. Using wildcards is supported.
        
        Required?                    false
        Position?                    1
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  true
        
    -Id &lt;String[]&gt;
        Specifies one or more virtual machine hosts by ID. Use commas to separate 
        multiple IDs.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  true
        
    -NoRecursion
        Get-VM searches recursively from any provided starting point. Setting this 
        parameter disables the command recursive behavior.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    -Server &lt;VIServer[]&gt;
        One or more virtual Infrastructure servers to apply the command on. If 
        no value is given to this parameter, the command takes the server curre
        ntly specified in the $DefaultVIServer variable.
        
        Required?                    false
        Position?                    named
        Default value                
        Accept pipeline input?       false
        Accept wildcard characters?  false
        
    &lt;CommonParameters&gt;
        This cmdlet supports the common parameters: -Verbose, -Debug,
        -ErrorAction, -ErrorVariable, -WarningAction, -WarningVariable,
        -OutBuffer and -OutVariable. For more information, type,
        "get-help about_commonparameters".
    
=====INPUT TYPE=====
    
     
=====RETURN TYPE=====
    VirtualMachine[]
     
    
=====NOTES=====
    
    
    --------------  EXAMPLE 1 --------------
    
    C:\PS&gt;Get-VM
    
    
Retrieves information about all of the virtual machines registered with the currently selected VMware Infrastructure server.
    
    
    --------------  EXAMPLE 2 --------------
    
    C:\PS&gt;Get-VM -Name webTier*
    
    
This command retrieves information about all virtual machines registered with the currently-selected VMware Infrastructure server whose names begin with "webTier."
    
    
=====RELATED LINKS=====
    [[Remove-VM]] 
    [[New-VM]] 
    [[Set-VM]] 
    [[Move-VM]] 
    [[Start-VM]] 
    [[Stop-VM]] 
    [[Suspend-VM]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>7bd3c999a298372bd12c0db928e12726f3cd2cbf</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Category:Powershell</title>
  <ns>14</ns>
  <id>432</id>
  <revision>
    <id>846</id>
    <timestamp>2009-03-24T12:36:12Z</timestamp>
    <contributor>
      <username>Virtu-al</username>
      <id>14</id>
    </contributor>
    <comment>New page: The Powershell Catergory is a place to store all VI Toolkit / PowerCLI knowledge, a central place for VI Admins to find scripts which have already been shared by other VI Admins.  If you r...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1035" xml:space="preserve">The Powershell Catergory is a place to store all VI Toolkit / PowerCLI knowledge, a central place for VI Admins to find scripts which have already been shared by other VI Admins.

If you require help with scripts or are looking for something which can not be found on this site please search the great  [http://communities.vmware.com/community/developer/windows_toolkit VMware VI Toolkit communities site] where LucD will probably answer your question within 5 minutes.


Please feel free to add your own scripts/pages/examples/links the intention is to add all cmdlets to this area to help people by enabling a quick help to the scripts which are added to this site.

So what now ?

Why not visit the [[Powershell CMDLET list]] to get a list of all cmdlets in the current version of the VI Toolkit and some help with each one.

Or if your new to the VI Toolkit check out the [[BEGINNERS PAGE]] where you can find links to the best VI Toolkit related sites or tips and tricks on getting started in the big wide world of the VI Toolkit.</text>
    <sha1>03cbc3c7632ae74012eb690978972c81c6ed8a32</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>BEGINNERS PAGE</title>
  <ns>0</ns>
  <id>433</id>
  <revision>
    <id>847</id>
    <timestamp>2009-03-24T12:37:40Z</timestamp>
    <contributor>
      <username>Virtu-al</username>
      <id>14</id>
    </contributor>
    <comment>New page: Looking to Get-Started with the VI Toolkit ?  Check out the below links to find useful resources or add your own:  * [http://communities.vmware.com/docs/DOC-4210 Managing VMware with Power...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="572" xml:space="preserve">Looking to Get-Started with the VI Toolkit ?

Check out the below links to find useful resources or add your own:

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell FAQ]
* [http://www.virtu-al.net/2009/02/23/vi-toolkit-quick-reference-guide/ VI Toolkit Quick Reference Guide]

Podcasts you should listen to:

* [http://get-scripting.blogspot.com/ Get-Scripting Podcast] by [[Alan Renouf]] and [[Jonathan Medd]]
* [http://powerscripting.wordpress.com/ PowerScripting Podcast] by [[Jonathan Walz]] and [[Hal Rottenberg]]

Add your own Tips here:</text>
    <sha1>fb1ac9d89f261ff7c0d2afcee70158685a464cff</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>850</id>
    <parentid>534</parentid>
    <timestamp>2009-03-28T10:07:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1215" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>747a71aedbea84044142b34ded01ef6233c3574e</sha1>
  </revision>
  <revision>
    <id>851</id>
    <parentid>850</parentid>
    <timestamp>2009-03-28T10:10:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1279" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]


==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>a5eef2913451ba1584a361d25ee244e9339cee41</sha1>
  </revision>
</page>
<page arvcontinue="20090218184727|803">
  <title>VI Plugin</title>
  <ns>0</ns>
  <id>7</id>
  <revision>
    <id>852</id>
    <parentid>122</parentid>
    <timestamp>2009-03-29T19:02:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added VI client plugin community link that lamw tweeted about</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="902" xml:space="preserve">=== VI plugins ===
We could dub this the akutz page if it wasn't for the link to the official VMware VI plugin documentation below. ;)

[[vip-svmotion]]

[http://communities.vmware.com/thread/126786 Add Port Groups]

=== VMware documentation ===

[http://www.vmware.com/support/developer/vc-sdk/vcplugin-exp/index.html VMware VI Plugin documentation]

[http://communities.vmware.com/docs/DOC-5881 Developing a Complete VI Client Plug-in with Tomcat and VI Java API]

[http://communities.vmware.com/community/developer/viclientplugins developer VI Client plugins community]

==== External links ====

Excellent article from David Davis about VI Plugins
* [http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1321254,00.html VMware VI Client plug-ins and how to manage them]

Andrew Kutz's open source VI Plugin projects
* http://code.google.com/p/akutz/

and his blog
* http://akutz.wordpress.com/</text>
    <sha1>5de5de5143133ef30df8faee4d22129f85c27f01</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Out-Dataset Cmdlet</title>
  <ns>0</ns>
  <id>434</id>
  <revision>
    <id>854</id>
    <timestamp>2009-04-01T08:21:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Out-DataSet is an extremely useful and needed cmdlet. You can use it to pipe any type of data that can be formatted with the built-in cmdlet, Format-Table, into a typed Microsoft .NET Syst...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="792" xml:space="preserve">Out-DataSet is an extremely useful and needed cmdlet. You can use it to pipe any type of data that can be formatted with the built-in cmdlet, Format-Table, into a typed Microsoft .NET System.Data.DataSet. This allows an unlimited manipulation of data that you simply cannot achieve with text globbing. This cmdlet is experimental in nature because it was achieved by reverse engineering the Format-Table cmdlet to pull the data directly from internal data structures that Microsoft does not expose via its public API. This was a necessary task in order to represent the data with 100% accuracy every single time.

==== External links ====

http://h9labscmdlets.wiki.sourceforge.net/

http://www.ntpro.nl/blog/archives/1036-Andrew-Kutz-is-finally-into-PowerShell.html

[[Category: Powershell]]</text>
    <sha1>229a28295be19c9c43e64b245aed863f934a5209</sha1>
  </revision>
  <revision>
    <id>855</id>
    <parentid>854</parentid>
    <timestamp>2009-04-01T08:27:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added Andrews own text from his blog</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="882" xml:space="preserve">Out-DataSet is an extremely useful and needed cmdlet. You can use it to pipe any type of data that can be formatted with the built-in cmdlet, Format-Table, into a typed Microsoft .NET System.Data.DataSet. This allows an unlimited manipulation of data that you simply cannot achieve with text globbing. This cmdlet is experimental in nature because it was achieved by reverse engineering the Format-Table cmdlet to pull the data directly from internal data structures that Microsoft does not expose via its public API. This was a necessary task in order to represent the data with 100% accuracy every single time.

==== External links ====

http://akutz.wordpress.com/2009/03/30/introducing-h9labs-powershell-cmdlets-out-dataset/

http://h9labscmdlets.wiki.sourceforge.net/

http://www.ntpro.nl/blog/archives/1036-Andrew-Kutz-is-finally-into-PowerShell.html

[[Category: Powershell]]</text>
    <sha1>62332a1ceee391c3a54a5c22782799d9f8dc8a25</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>856</id>
    <parentid>853</parentid>
    <timestamp>2009-04-01T08:35:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1168" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

==== General powershell ====

* [[http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>d63ba69d6a0bb1a23a945b21286e9ec15ed1c3d7</sha1>
  </revision>
  <revision>
    <id>857</id>
    <parentid>856</parentid>
    <timestamp>2009-04-01T08:35:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1166" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>b02b89256cf35735bfea743d2892cafcc5aff0ae</sha1>
  </revision>
  <revision>
    <id>861</id>
    <parentid>857</parentid>
    <timestamp>2009-04-29T12:39:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1355" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Ecoshell initiative]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>0a61310be43a17b4a7dc435777201e775d26972d</sha1>
  </revision>
  <revision>
    <id>862</id>
    <parentid>861</parentid>
    <timestamp>2009-04-29T12:40:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1370" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>cf449e43fb46877a41d0c9da19579b71ffc737cd</sha1>
  </revision>
  <revision>
    <id>864</id>
    <parentid>862</parentid>
    <timestamp>2009-04-29T23:19:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added powergui</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1423" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>befb16d759a3886263cb8e20a0683260b183f6f2</sha1>
  </revision>
  <revision>
    <id>866</id>
    <parentid>864</parentid>
    <timestamp>2009-05-07T09:01:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1538" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Introduction to the vSphere SDK in Java and C#]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>13f84726131cd7f96750b1f999e477ba32f69761</sha1>
  </revision>
  <revision>
    <id>875</id>
    <parentid>866</parentid>
    <timestamp>2009-05-12T08:03:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1608" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>4d023628cf6b2469652d2023214d5966c3192a27</sha1>
  </revision>
  <revision>
    <id>877</id>
    <parentid>875</parentid>
    <timestamp>2009-05-14T10:07:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1688" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>689a3c5df8873c2865e8c21aaf83a18e4fe3a210</sha1>
  </revision>
  <revision>
    <id>880</id>
    <parentid>877</parentid>
    <timestamp>2009-05-14T10:16:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1826" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>e3e9c09df021656545985d0964afc3840b9231d8</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>BEGINNERS PAGE</title>
  <ns>0</ns>
  <id>433</id>
  <revision>
    <id>858</id>
    <parentid>847</parentid>
    <timestamp>2009-04-03T10:35:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added some more links from Tom's planetvm.net</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="841" xml:space="preserve">Looking to Get-Started with the VI Toolkit ?

Check out the below links to find useful resources or add your own:

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell FAQ]
* [http://www.virtu-al.net/2009/02/23/vi-toolkit-quick-reference-guide/ VI Toolkit Quick Reference Guide]
* [http://vinternals.com/powercli-mastery/ vinternals VI Toolkit mastery]
* [http://keithhill.spaces.live.com/blog Keith hill blog]
* [http://blogs.vmware.com/files/vi-toolkit-lab----vmworld-europe-2009.pdf VI Toolkit lab VMworld europe 2009]

Podcasts you should listen to:

* [http://get-scripting.blogspot.com/ Get-Scripting Podcast] by [[Alan Renouf]] and [[Jonathan Medd]]
* [http://powerscripting.wordpress.com/ PowerScripting Podcast] by [[Jonathan Walz]] and [[Hal Rottenberg]]

Add your own Tips here:

[[Category: Powershell]]</text>
    <sha1>0d308b3961869df882cc1588d4792a43e6ae94be</sha1>
  </revision>
  <revision>
    <id>888</id>
    <parentid>858</parentid>
    <timestamp>2009-05-14T15:21:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="840" xml:space="preserve">Looking to Get-Started with the VI Toolkit ?

Check out the below links to find useful resources or add your own:

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell FAQ]
* [http://www.virtu-al.net/2009/02/23/vi-toolkit-quick-reference-guide/ VI Toolkit Quick Reference Guide]
* [http://vinternals.com/powercli-mastery/ vinternals: PowerCLI mastery]
* [http://keithhill.spaces.live.com/blog Keith hill blog]
* [http://blogs.vmware.com/files/vi-toolkit-lab----vmworld-europe-2009.pdf VI Toolkit lab VMworld europe 2009]

Podcasts you should listen to:

* [http://get-scripting.blogspot.com/ Get-Scripting Podcast] by [[Alan Renouf]] and [[Jonathan Medd]]
* [http://powerscripting.wordpress.com/ PowerScripting Podcast] by [[Jonathan Walz]] and [[Hal Rottenberg]]

Add your own Tips here:

[[Category: Powershell]]</text>
    <sha1>37a6e2db8fa1603f09a4672e0a056e2f3a9661a0</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>859</id>
    <parentid>851</parentid>
    <timestamp>2009-04-03T23:06:38Z</timestamp>
    <contributor>
      <username>Rchase</username>
      <id>15</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1350" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]


==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>178a57ecf80f0c988f8090307e5bae7bc00272a1</sha1>
  </revision>
  <revision>
    <id>860</id>
    <parentid>859</parentid>
    <timestamp>2009-04-24T10:48:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added devcenter blog to the list</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1442" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>fe813ffaa53f6a0cf469265824b1d15d91baaab0</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>VI Toolkit for windows</title>
  <ns>0</ns>
  <id>11</id>
  <revision>
    <id>863</id>
    <parentid>59</parentid>
    <timestamp>2009-04-29T13:55:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Updated link from Powershell 2.0 CTP2 to CTP3</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="989" xml:space="preserve">==== VI Toolkit for windows ====

The official [http://www.vmware.com/support/developer/windowstoolkit/ VMware VI Toolkit for windows landing page] for accessing the Virtual Infrastructure API using [[PowerShell]] or .net

==== VI Toolkit extensions ====

For this you'll need to upgrade to [http://www.microsoft.com/downloads/details.aspx?familyid=C913AEAB-D7B4-4BB1-A958-EE6D7FE307BC&amp;displaylang=en PowerShell 2 CTP3] and the code is at:
http://www.codeplex.com/vitoolkitextensions

See this NTPRO.nl article for details:
[http://www.ntpro.nl/blog/archives/741-Enabling-the-VI-Toolkit-Extensions.html Enabling the VI Toolkit Extensions]

==== VI Toolkit for .net ====

The VI Toolkit for .NET is a .NET library designed to bring object-oriented design to the VI API by transforming managed object references into first class objects, as well as providing helpful method, property, and class abstractions.

http://sourceforge.net/projects/vitfordotnet/

[[Category:SDK]] [[Category:.net]]</text>
    <sha1>66966e9bf6e371cf1ded83b23c8c116402ef3230</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Vmsvc/reload</title>
  <ns>0</ns>
  <id>205</id>
  <revision>
    <id>865</id>
    <parentid>379</parentid>
    <timestamp>2009-05-03T10:17:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="295" xml:space="preserve">==== vimsh vmsvc/reload ====
Usage: reload vmid

Reload the virtual machine state from afresh.

==== External link ====

* [http://www.boche.net/blog/index.php/2009/05/02/force-vcenter-server-update-to-reflect-vmx-changes/ Force vCenter Server update to reflext vmx changes]

[[Category: Vimsh]]</text>
    <sha1>0e5eb7519382fabf0bfea19a7d64ab88a0ffd891</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Introduction to scripting vi using perl or powershell</title>
  <ns>0</ns>
  <id>435</id>
  <revision>
    <id>867</id>
    <timestamp>2009-05-07T10:47:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Hello, my name is David Deeths and I’m a new contributor to the VMware Developer Blog. I wanted to share with the community the scripting lab we put together for VMworld 2008. This is a ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="629" xml:space="preserve">Hello, my name is David Deeths and I’m a new contributor to the VMware Developer Blog. I wanted to share with the community the scripting lab we put together for VMworld 2008. This is a great introduction to scripting with the VI Toolkits in Perl or PowerShell. The PowerShell version doesn’t require any programming or scripting experience at all.

Read more at:
[http://communities.vmware.com/blogs/DeveloperCenter/2009/01/14/an-introduction-to-scripting-vi-using-perl-or-powershell VMware Blog: An Introduction to scripting VI using perl or Powershell]

[[Category: VI-Toolkit]] [[Category: Perl]] [[Category: Powershell]]</text>
    <sha1>48bf85f86cc569ccc5fbffd15249fc2119c32f9f</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Introduction to the vSphere SDK in Java and C</title>
  <ns>0</ns>
  <id>436</id>
  <revision>
    <id>868</id>
    <timestamp>2009-05-07T10:51:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: We ran a very successful vSphere SDK lab at Partner Exchange / Tech Exchange a few weeks ago in Orlando. For those of you who missed the event, I'm posting the manuals and code files. Goin...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="597" xml:space="preserve">We ran a very successful vSphere SDK lab at Partner Exchange / Tech Exchange a few weeks ago in Orlando. For those of you who missed the event, I'm posting the manuals and code files. Going through the lab is a great way to get started with the API and includes handy sample code for modification or inclusion in your own programs.

Read more at: 
[http://communities.vmware.com/blogs/DeveloperCenter/2009/05/06/introduction-to-the-vsphere-sdk-vi-sdk-in-java-and-c VMware Blog: Introduction to the vSphere SDK (VI SDK) in Java and C#]

[[Category: vSphere SDK]][[Category: Java]][[Category: .net]]</text>
    <sha1>2b8085097055eea321dcb9f590bc2296edec3f05</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>ESX CLI Commands</title>
  <ns>0</ns>
  <id>416</id>
  <revision>
    <id>869</id>
    <parentid>791</parentid>
    <timestamp>2009-05-10T19:24:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2709" xml:space="preserve">==== ESX CLI Commands ====

Virtual Infrastructure ESX has a service console which can be used to management purposes.
This is a light weight linux based (RHEL3) Virtual Machine which has special privileges that can be used in order to manage your host and Virtual Machines.
Down here we will be trying to document the available commands that you can use on this service console from the so called Command Line Interface (CLI).

In ESXi (3.x) the service console has been removed from the host and there's only a remote alternative available, which is called the [[RCLI]].
The chapter here only contains the documentation for the full blown version not the RCLI.

Any changes made to the configuration of the host will not be seen by vCenter Server or the host itself until you restart the vmware-hostd daemon. By restarting this daemon, the configuration file /etc/vmware/esx.conf will be re-read.

 service mgmt-vmware restart

will restart this daemon.


==== The available commands ====

 [[esxcfg-advcfg]]      
 [[esxcfg-auth]]        
 [[esxcfg-boot]]        
 [[esxcfg-configcheck]]
 [[esxcfg-dumppart]]   
 [[esxcfg-firewall]]   
 [[esxcfg-hwiscsi]]    
 [[esxcfg-info]]     
 [[esxcfg-init]]
 [[esxcfg-linuxnet]]
 [[esxcfg-module]]
 [[esxcfg-mpath]]
 [[esxcfg-nas]]
 [[esxcfg-nics]]
 [[esxcfg-pciid]]
 [[esxcfg-rescan]]
 [[esxcfg-resgrp]]
 [[esxcfg-route]]
 [[esxcfg-swiscsi]]
 [[esxcfg-upgrade]]
 [[esxcfg-vmhbadevs]]
 [[esxcfg-vmknic]]
 [[esxcfg-vswif]]
 [[esxcfg-vswitch]]
 [[esxupdate]]
 [[vcbExport]]
 [[vcbMounter]]
 [[vcbResAll]]
 [[vcbRestore]]
 [[vcbSnapAll]]
 [[vcbSnapshot]]
 [[vcbUtil]]
 [[vcbVmName]]
 [[vdf]]
 [[vimsh]]
 [[vmfsqhtool]]
 [[vmfsqueuetool]]
 [[vmkchdev]]
 [[vmkdump]]
 [[vmkerrcode]]
 [[vmkfstools]]
 [[vmkiscsid]]
 [[vmkiscsi-device]]
 [[vmkiscsi-ls]]
 [[vmkiscsi-tool]]
 [[vmkiscsi-util]]
 [[vmkloader]]
 [[vmkload_mod]]
 [[vmklogger]]
 [[vmkpcidivy]]
 [[vmkping]]
 [[vmkuptime.pl]]
 [[vmres.pl]]
 [[vmsnap_all]]
 [[vmsnap.pl]]
 [[vmstat]]
 [[vm-support]]
 [[vmware]]
 [[vmware-authd]]
 [[vmware-autopoweron.sh]]
 [[vmware-cmd]]
 [[vmware-configcheck]]
 [[vmware-config.pl]]
 [[vmware-hostd]]
 [[vmware-hostd-support]]
 [[vmware-mkinitrd]]
 [[vmware-vim-cmd]]         
 [[vmware-vimdump]]         
 [[vmware-vimsh]]
 [[vmware-watchdog]]
 [[vmware-webAccess]]

==== External Links ====

* [http://download3.vmware.com/vmworld/2006/tac9685.pdf VMworld 2006: Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

* [http://www.rtfm-ed.co.uk/docs/vmwdocs/ESX3.x-VC2.x-ServiceConsole-Guide.pdf RTFM Education: ESX3.x Service Console Guide]

* [http://www.b2v.co.uk/b2vguide2vmware.htm B2V Guide to VMware ESX Server 2.x]

[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>e1cd8e58c0398f30923526f1963831e548b487bf</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Vmkerrcode</title>
  <ns>0</ns>
  <id>417</id>
  <revision>
    <id>870</id>
    <parentid>789</parentid>
    <timestamp>2009-05-12T07:29:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24957" xml:space="preserve">==== vmkerrcode ====
Usage: 
 vmkerrcode [-l] [error code (hex or decimal)]
    -l list all error codes

This can be used in order to decode the error

==== Example output ====
 # vmkerrcode -l
 
 VMK_ReturnStatus table for VMware ESX Server, Build #130756
 Name                             Dec         Hex          errno equiv    Description                                                 
 -------------------------------------------------------------------------------
 VMK_OK                           0           0            OK            Success
 VMK_FAILURE                      195887105   0xbad0001    EINVAL        Failure
 VMK_WOULD_BLOCK                  195887106   0xbad0002    EAGAIN        Would block
 VMK_NOT_FOUND                    195887107   0xbad0003    ENOENT        Not found
 VMK_BUSY                         195887108   0xbad0004    EBUSY         Busy
 VMK_EXISTS                       195887109   0xbad0005    EEXIST        Already exists
 VMK_LIMIT_EXCEEDED               195887110   0xbad0006    EFBIG         Limit exceeded
 VMK_BAD_PARAM                    195887111   0xbad0007    EINVAL        Bad parameter
 VMK_METADATA_READ_ERROR          195887112   0xbad0008    EIO           Metadata read error
 VMK_METADATA_WRITE_ERROR         195887113   0xbad0009    EIO           Metadata write error
 VMK_IO_ERROR                     195887114   0xbad000a    EIO           I/O error
 VMK_READ_ERROR                   195887115   0xbad000b    EIO           Read error
 VMK_WRITE_ERROR                  195887116   0xbad000c    EIO           Write error
 VMK_INVALID_NAME                 195887117   0xbad000d    ENAMETOOLONG  Invalid name
 VMK_INVALID_HANDLE               195887118   0xbad000e    EBADF         Invalid handle
 VMK_INVALID_ADAPTER              195887119   0xbad000f    ENODEV        No such SCSI adapter
 VMK_INVALID_TARGET               195887120   0xbad0010    ENODEV        No such target on adapter
 VMK_INVALID_PARTITION            195887121   0xbad0011    ENXIO         No such partition on target
 VMK_INVALID_FS                   195887122   0xbad0012    ENXIO         No filesystem on the device
 VMK_INVALID_MEMMAP               195887123   0xbad0013    EFAULT        Memory map mismatch
 VMK_NO_MEMORY                    195887124   0xbad0014    ENOMEM        Out of memory
 VMK_NO_MEMORY_RETRY              195887125   0xbad0015    ENOMEM        Out of memory (ok to retry)
 VMK_NO_RESOURCES                 195887126   0xbad0016    ENOMEM        Out of resources
 VMK_NO_FREE_HANDLES              195887127   0xbad0017    EMFILE        No free handles
 VMK_NUM_HANDLES_EXCEEDED         195887128   0xbad0018    ENFILE        Exceeded maximum number of allowed handles
 VMK_DEPRECATED_NO_FREE_PTR_BLOCKS195887129   0xbad0019    ENOSPC        No free pointer blocks (deprecated)
 VMK_DEPRECATED_NO_FREE_DATA_BLOCKS195887130   0xbad001a    ENOSPC        No free data blocks (deprecated)
 VMK_CORRUPT_REDOLOG              195887131   0xbad001b    EBADF         Corrupt RedoLog
 VMK_STATUS_PENDING               195887132   0xbad001c    EAGAIN        Status pending
 VMK_STATUS_FREE                  195887133   0xbad001d    EAGAIN        Status free
 VMK_UNSUPPORTED_CPU              195887134   0xbad001e    ENODEV        Unsupported CPU
 VMK_NOT_SUPPORTED                195887135   0xbad001f    ENOSYS        Not supported
 VMK_TIMEOUT                      195887136   0xbad0020    ETIMEDOUT     Timeout
 VMK_READ_ONLY                    195887137   0xbad0021    EROFS         Read only
 VMK_RESERVATION_CONFLICT         195887138   0xbad0022    EAGAIN        SCSI reservation conflict
 VMK_FS_LOCKED                    195887139   0xbad0023    EADDRINUSE    File system locked
 VMK_NOT_ENOUGH_SLOTS             195887140   0xbad0024    ENFILE        Out of slots
 VMK_INVALID_ADDRESS              195887141   0xbad0025    EFAULT        Invalid address
 VMK_NOT_SHARED                   195887142   0xbad0026    ENOMEM        Not shared
 VMK_SHARED                       195887143   0xbad0027    ENOMEM        Page is shared
 VMK_KSEG_PAIR_FLUSHED            195887144   0xbad0028    ENOMEM        Kseg pair flushed
 VMK_MAX_ASYNCIO_PENDING          195887145   0xbad0029    ENOMEM        Max async I/O requests pending
 VMK_VERSION_MISMATCH_MINOR       195887146   0xbad002a    ENOSYS        Minor version mismatch
 VMK_VERSION_MISMATCH_MAJOR       195887147   0xbad002b    ENOSYS        Major version mismatch
 VMK_IS_CONNECTED                 195887148   0xbad002c    EINVAL        Already connected
 VMK_IS_DISCONNECTED              195887149   0xbad002d    ENOTCONN      Already disconnected
 VMK_IS_ENABLED                   195887150   0xbad002e    EINVAL        Already enabled
 VMK_IS_DISABLED                  195887151   0xbad002f    EINVAL        Already disabled
 VMK_NOT_INITIALIZED              195887152   0xbad0030    EINVAL        Not initialized
 VMK_WAIT_INTERRUPTED             195887153   0xbad0031    EINTR         Wait interrupted
 VMK_NAME_TOO_LONG                195887154   0xbad0032    ENAMETOOLONG  Name too long
 VMK_MISSING_FS_PES               195887155   0xbad0033    ENOTDIR       VMFS volume missing physical extents
 VMK_NICTEAMING_VALID_MASTER      195887156   0xbad0034    EINVAL        NIC teaming master valid
 VMK_NICTEAMING_SLAVE             195887157   0xbad0035    EEXIST        NIC teaming slave
 VMK_NICTEAMING_REGULAR_VMNIC     195887158   0xbad0036    EINVAL        NIC teaming regular VMNIC
 VMK_ABORT_NOT_RUNNING            195887159   0xbad0037    ECANCELED     Abort not running
 VMK_NOT_READY                    195887160   0xbad0038    EIO           Not ready
 VMK_CHECKSUM_MISMATCH            195887161   0xbad0039    EIO           Checksum mismatch
 VMK_VLAN_NO_HW_ACCEL             195887162   0xbad003a    EINVAL        VLan HW Acceleration not supported
 VMK_NO_VLAN_SUPPORT              195887163   0xbad003b    EOPNOTSUPP    VLan is not supported in vmkernel
 VMK_NOT_VLAN_HANDLE              195887164   0xbad003c    EINVAL        Not a VLan handle
 VMK_BAD_VLANID                   195887165   0xbad003d    EBADF         Couldn't retrieve VLan id
 VMK_MIG_PROTO_ERROR              195887166   0xbad003e    EINVAL        Migration protocol error
 VMK_NO_CONNECT                   195887167   0xbad003f    EIO           No connection
 VMK_SEGMENT_OVERLAP              195887168   0xbad0040    EINVAL        Segment overlap
 VMK_BAD_MPS                      195887169   0xbad0041    EIO           Error parsing MPS Table
 VMK_BAD_ACPI                     195887170   0xbad0042    EIO           Error parsing ACPI Table
 VMK_RESUME_ERROR                 195887171   0xbad0043    EIO           Failed to resume VM
 VMK_NO_ADDRESS_SPACE             195887172   0xbad0044    ENOMEM        Insufficient address space for operation
 VMK_BAD_ADDR_RANGE               195887173   0xbad0045    EINVAL        Bad address range
 VMK_ENETDOWN                     195887174   0xbad0046    ENETDOWN      Network is down
 VMK_ENETUNREACH                  195887175   0xbad0047    ENETUNREACH   Network unreachable
 VMK_ENETRESET                    195887176   0xbad0048    ENETRESET     Network dropped connection on reset
 VMK_ECONNABORTED                 195887177   0xbad0049    ECONNABORTED  Software caused connection abort
 VMK_ECONNRESET                   195887178   0xbad004a    ECONNRESET    Connection reset by peer
 VMK_ENOTCONN                     195887179   0xbad004b    ENOTCONN      Socket is not connected
 VMK_ESHUTDOWN                    195887180   0xbad004c    ESHUTDOWN     Can't send after socket shutdown
 VMK_ETOOMANYREFS                 195887181   0xbad004d    ETOOMANYREFS  Too many references: can't splice
 VMK_ECONNREFUSED                 195887182   0xbad004e    ECONNREFUSED  Connection refused
 VMK_EHOSTDOWN                    195887183   0xbad004f    EHOSTDOWN     Host is down
 VMK_EHOSTUNREACH                 195887184   0xbad0050    EHOSTUNREACH  No route to host
 VMK_EADDRINUSE                   195887185   0xbad0051    EADDRINUSE    Address already in use
 VMK_BROKEN_PIPE                  195887186   0xbad0052    EPIPE         Broken pipe
 VMK_NOT_A_DIRECTORY              195887187   0xbad0053    ENOTDIR       Not a directory
 VMK_IS_A_DIRECTORY               195887188   0xbad0054    EISDIR        Is a directory
 VMK_NOT_EMPTY                    195887189   0xbad0055    ENOTEMPTY     Directory not empty
 VMK_NOT_IMPLEMENTED              195887190   0xbad0056    ENOSYS        Not implemented
 VMK_NO_SIGNAL_HANDLER            195887191   0xbad0057    EINVAL        No signal handler
 VMK_FATAL_SIGNAL_BLOCKED         195887192   0xbad0058    EINVAL        Fatal signal blocked
 VMK_NO_ACCESS                    195887193   0xbad0059    EACCES        Permission denied
 VMK_NO_PERMISSION                195887194   0xbad005a    EPERM         Operation not permitted
 VMK_UNDEFINED_SYSCALL            195887195   0xbad005b    ENOSYS        Undefined syscall
 VMK_RESULT_TOO_LARGE             195887196   0xbad005c    ERANGE        Result too large
 VMK_VLAN_FILTERED                195887197   0xbad005d    ERANGE        Pkts dropped because of VLAN (support)  mismatch
 VMK_BAD_EXCFRAME                 195887198   0xbad005e    EFAULT        Unsafe exception frame
 VMK_MODULE_NOT_LOADED            195887199   0xbad005f    ENODEV        Necessary module isn't loaded
 VMK_NO_SUCH_ZOMBIE               195887200   0xbad0060    ECHILD        No dead world by that name
 VMK_NO_SUCH_CARTEL               195887201   0xbad0061    ESRCH         No cartel by that name
 VMK_IS_A_SYMLINK                 195887202   0xbad0062    ELOOP         Is a symbolic link
 VMK_CROSS_DEVICE_LINK            195887203   0xbad0063    EXDEV         Cross-device link
 VMK_NOT_A_SOCKET                 195887204   0xbad0064    ENOTSOCK      Not a socket
 VMK_ILLEGAL_SEEK                 195887205   0xbad0065    ESPIPE        Illegal seek
 VMK_ADDRFAM_UNSUPP               195887206   0xbad0066    EAFNOSUPPORT  Unsupported address family
 VMK_ALREADY_CONNECTED            195887207   0xbad0067    EISCONN       Already connected
 VMK_DEATH_PENDING                195887208   0xbad0068    ENOENT        World is marked for death
 VMK_NO_CELL_ASSIGNMENT           195887209   0xbad0069    EINVAL        No valid scheduler cell assignment
 VMK_CPU_MIN_INVALID              195887210   0xbad006a    EINVAL        Invalid cpu min
 VMK_CPU_MINLIMIT_INVALID         195887211   0xbad006b    EINVAL        Invalid cpu minLimit
 VMK_CPU_MAX_INVALID              195887212   0xbad006c    EINVAL        Invalid cpu max
 VMK_CPU_SHARES_INVALID           195887213   0xbad006d    EINVAL        Invalid cpu shares
 VMK_CPU_MIN_OVERFLOW             195887214   0xbad006e    EINVAL        Cpu min outside valid range
 VMK_CPU_MINLIMIT_OVERFLOW        195887215   0xbad006f    EINVAL        Cpu minLimit outside valid range
 VMK_CPU_MAX_OVERFLOW             195887216   0xbad0070    EINVAL        Cpu max outside valid range
 VMK_CPU_MIN_GT_MINLIMIT          195887217   0xbad0071    EINVAL        Cpu min exceeds minLimit
 VMK_CPU_MIN_GT_MAX               195887218   0xbad0072    EINVAL        Cpu min exceeds max
 VMK_CPU_MINLIMIT_LT_RESERVED     195887219   0xbad0073    ENOSPC        Cpu minLimit less than cpu already  reserved by children
 VMK_CPU_MAX_LT_RESERVED          195887220   0xbad0074    ENOSPC        Cpu max less than cpu already reserved by children
 VMK_CPU_ADMIT_FAILED             195887221   0xbad0075    ENOSPC        Admission check failed for cpu resource
 VMK_MEM_MIN_INVALID              195887222   0xbad0076    EINVAL        Invalid memory min
 VMK_MEM_MINLIMIT_INVALID         195887223   0xbad0077    EINVAL        Invalid memory minLimit
 VMK_MEM_MAX_INVALID              195887224   0xbad0078    EINVAL        Invalid memory max
 VMK_MEM_MIN_OVERFLOW             195887225   0xbad0079    EINVAL        Memory min outside valid range
 VMK_MEM_MINLIMIT_OVERFLOW        195887226   0xbad007a    EINVAL        Memory minLimit outside valid range
 VMK_MEM_MAX_OVERFLOW             195887227   0xbad007b    EINVAL        Memory max outside valid range
 VMK_MEM_MIN_GT_MINLIMIT          195887228   0xbad007c    EINVAL        Memory min exceeds minLimit
 VMK_MEM_MIN_GT_MAX               195887229   0xbad007d    EINVAL        Memory min exceeds max
 VMK_MEM_MINLIMIT_LT_RESERVED     195887230   0xbad007e    ENOSPC        Memory minLimit less than memory already  reserved by children
 VMK_MEM_MAX_LT_RESERVED          195887231   0xbad007f    ENOSPC        Memory max less than memory already  reserved by children
 VMK_MEM_ADMIT_FAILED             195887232   0xbad0080    ENOSPC        Admission check failed for memory resource
 VMK_NO_SWAP_FILE                 195887233   0xbad0081    ENOENT        No swap file
 VMK_BAD_PARAM_COUNT              195887234   0xbad0082    EINVAL        Bad parameter count
 VMK_BAD_PARAM_TYPE               195887235   0xbad0083    EINVAL        Bad parameter type
 VMK_UNMAP_RETRY                  195887236   0xbad0084    ENOMEM        Dueling unmaps (ok to retry)
 VMK_INVALID_IOCTL                195887237   0xbad0085    ENOTTY        Inappropriate ioctl for device
 VMK_MAPFAULT_RETRY               195887238   0xbad0086    EBUSY         Mmap changed under page fault (ok to  retry)
 VMK_EINPROGRESS                  195887239   0xbad0087    EINPROGRESS   Operation now in progress
 VMK_ADDR_UNMAPPED                195887240   0xbad0088    EFAULT        Address temporarily unmapped
 VMK_INVALID_BUDDY_TYPE           195887241   0xbad0089    ENOMEM        Invalid buddy type
 VMK_LPAGE_INFO_NOT_FOUND         195887242   0xbad008a    ENOMEM        Large page info not found
 VMK_LPAGE_INFO_INVALID           195887243   0xbad008b    EINVAL        Invalid large page info
 VMK_SNAPSHOT_DEV                 195887244   0xbad008c    EIO           SCSI LUN is in snapshot state
 VMK_IN_TRANSITION                195887245   0xbad008d    EIO           SCSI LUN is in transition
 VMK_TXN_FULL                     195887246   0xbad008e    ENOSPC        Transaction ran out of lock space or log  space
 VMK_LOCK_NOT_FREE                195887247   0xbad008f    EBUSY         Lock was not free
 VMK_NUM_FILES_EXCEEDED           195887248   0xbad0090    ENOSPC        Exceed maximum number of files on the filesystem
 VMK_MIGRATE_VMX_FAILURE          195887249   0xbad0091    EINVAL        Migration determined a failure by the VMX
 VMK_VSI_LIST_OVERFLOW            195887250   0xbad0092    EFBIG         VSI GetList handler overflow
 VMK_INVALID_WORLD                195887251   0xbad0093    EINVAL        Invalid world
 VMK_INVALID_VMM                  195887252   0xbad0094    EINVAL        Invalid vmm
 VMK_INVALID_TXN                  195887253   0xbad0095    EINVAL        Invalid transaction
 VMK_FS_RETRY_OPERATION           195887254   0xbad0096    EAGAIN        Transient file system condition, suggest  retry
 VMK_VCPU_LIMIT_EXCEEDED          195887255   0xbad0097    EINVAL        Number of running VCPUs limit exceeded
 VMK_INVALID_METADATA             195887256   0xbad0098    EINVAL        Invalid metadata
 VMK_INVALID_PAGE_NUMBER          195887257   0xbad0099    EINVAL        Invalid page number
 VMK_NOT_EXEC                     195887258   0xbad009a    ENOEXEC       Not in executable format
 VMK_NFS_CONNECT_FAILURE          195887259   0xbad009b    EHOSTDOWN     Unable to connect to NFS server
 VMK_NFS_MOUNT_NOT_SUPPORTED      195887260   0xbad009c    EINVAL        The NFS server does not support MOUNT  version 3 over TCP
 VMK_NFS_NFS_NOT_SUPPORTED        195887261   0xbad009d    EINVAL        The NFS server does not support NFS  version 3 over TCP
 VMK_NFS_MOUNT_DENIED             195887262   0xbad009e    EPERM         The mount request was denied by the NFS  server. Check that the export exists and that the client is permitted to mount it
 VMK_NFS_MOUNT_NOT_DIR            195887263   0xbad009f    ENOTDIR       The specified mount path was not a directory
 VMK_NFS_BAD_FSINFO               195887264   0xbad00a0    EACCES        Unable to query remote mount point's attributes
 VMK_NFS_VOLUME_LIMIT_EXCEEDED    195887265   0xbad00a1    EINVAL        NFS has reached the maximum number of supported volumes
 VMK_NO_MEMORY_NICE               195887266   0xbad00a2    ENOMEM        Out of nice memory
 VMK_MIGRATE_PREEMPTIVE_FAIL      195887267   0xbad00a3    ENOMEM        VMotion failed to start due to lack of cpu or memory resources
 VMK_CACHE_MISS                   195887268   0xbad00a4    EFAULT        Cache miss
 VMK_STRESS_INDUCED_ERROR         195887269   0xbad00a5    EIO           Error induced when stress options are enabled
 VMK_TOO_MANY_LOCK_HOLDERS        195887270   0xbad00a6    EUSERS        Maximum number of concurrent hosts are already accessing this resource
 VMK_NO_JOURNAL                   195887271   0xbad00a7    EIO           Host doesn't have a journal
 VMK_RANK_VIOLATION               195887272   0xbad00a8    EDEADLK       Lock rank violation detected
 VMK_MODULE_FAILED                195887273   0xbad00a9    ENODEV        Module failed
 VMK_NO_MASTER_PTY                195887274   0xbad00aa    ENXIO         Unable to open slave if no master pty
 VMK_NOT_IOABLE                   195887275   0xbad00ab    EFAULT        Not IOAble
 VMK_NO_FREE_INODES               195887276   0xbad00ac    ENOSPC        No free inodes
 VMK_NO_MEMORY_FOR_FILEDATA       195887277   0xbad00ad    ENOSPC        No free memory for file data
 VMK_NO_TAR_SPACE                 195887278   0xbad00ae    ENOSPC        No free space to expand file or meta data
 VMK_NO_FIFO_READER               195887279   0xbad00af    ENXIO         Unable to open writer if no fifo reader
 VMK_NO_SUCH_DEVICE               195887280   0xbad00b0    EINVAL        No underlying device for major,minor
 VMK_MEM_MIN_GT_MEMSIZE           195887281   0xbad00b1    EINVAL        Memory min exceeds memSize
 VMK_NO_SUCH_VT                   195887282   0xbad00b2    ENXIO         No virtual terminal for number
 VMK_TOO_MANY_ELEMENTS            195887283   0xbad00b3    E2BIG         Too many elements for list
 VMK_SHAREDAREA_MISMATCH          195887284   0xbad00b4    ENOSYS        VMM&lt;-&gt;VMK shared are mismatch
 VMK_EXEC_FAILURE                 195887285   0xbad00b5    ESRCH         Failure during exec while original state already lost
 VMK_VMNIXMOD_NOT_LOADED          195887286   0xbad00b6    ENOSYS        vmnixmod kernel module not loaded
 VMK_INVALID_MODULE               195887287   0xbad00b7    EINVAL        Invalid module
 VMK_UNALIGNED_ADDRESS            195887288   0xbad00b8    EINVAL        Address is not aligned on page boundary
 VMK_NOT_MAPPED                   195887289   0xbad00b9    ENOMEM        Address is not mapped in address space
 VMK_NO_MESSAGE_SPACE             195887290   0xbad00ba    ENOMEM        No space to record a message
 VMK_PDI_STACK_OVERFLOW           195887291   0xbad00bb    EFBIG         No space left on PDI stack
 VMK_EXCEPTION_HANDLER_INVALID    195887292   0xbad00bc    EINVAL        Invalid exception handler
 VMK_EXCEPTION_NOT_HANDLED        195887293   0xbad00bd    EINVAL        Exception not handled by exception handler
 VMK_INVALID_MULTIWRITER_OBJECT   195887294   0xbad00be    EDEADLK       Can't open sparse/TBZ files in  multiwriter mode
 VMK_STORAGE_RETRY_OPERATION      195887295   0xbad00bf    EAGAIN        Transient storage condition, suggest retry
 VMK_HBA_ERROR                    195887296   0xbad00c0    EIO           Storage initiator error
 VMK_TIMER_INIT_FAILED            195887297   0xbad00c1    EINVAL        Timer initialization failed
 VMK_MODULE_NOT_FOUND             195887298   0xbad00c2    ENOENT        Module not found
 VMK_NOT_SOCKET_OWNER             195887299   0xbad00c3    EINVAL        Socket not owned by cartel
 VMK_VSI_HANDLER_NOT_FOUND        195887300   0xbad00c4    ENOENT        No VSI handler found for the requested node
 VMK_INVALID_MMAPPROTFLAGS        195887301   0xbad00c5    EINVAL        Invalid mmap protection flags
 VMK_INVALID_MAPCONTIG_SIZE       195887302   0xbad00c6    EINVAL        Invalid chunk size for contiguous mmap 
 VMK_INVALID_MAPCONTIG_MAX        195887303   0xbad00c7    EINVAL        Invalid MPN max for contiguous mmap 
 VMK_INVALID_MAPCONTIG_FLAG       195887304   0xbad00c8    EINVAL        Invalid mmap flag on contiguous mmap 
 VMK_NOT_LAZY_MMINFO              195887305   0xbad00c9    EINVAL        Unexpected fault on pre-faulted memory region
 VMK_MMINFO_WONT_SPLIT            195887306   0xbad00ca    EINVAL        Memory region cannot be split (remap/unmap)
 VMK_NO_CACHE_INFO                195887307   0xbad00cb    ENOENT        Cache Information not available
 VMK_CANNOT_REMAP_PINNED_MEMORY   195887308   0xbad00cc    EINVAL        Cannot remap pinned memory
 VMK_NO_SUCH_CARTELGROUP          195887309   0xbad00cd    ESRCH         No cartel group by that name
 VMK_SPLOCKSTATS_DISABLED         195887310   0xbad00ce    EINVAL        SPLock stats collection disabled
 VMK_BAD_TAR_IMAGE                195887311   0xbad00cf    EINVAL        Boot image is corrupted
 VMK_BRANCHED_ALREADY             195887312   0xbad00d0    EPERM         Branched file cannot be modified
 VMK_NAME_RESERVED_FOR_BRANCH     195887313   0xbad00d1    EPERM         Name is reserved for branched file
 VMK_CANNOT_BRANCH_UNLINKED       195887314   0xbad00d2    EPERM         Unlinked file cannot be branched
 VMK_MAX_RETRIES_EXCEEDED         195887315   0xbad00d3    EAGAIN        Maximum kernel-level retries exceeded
 VMK_OPTLOCK_STOLEN               195887316   0xbad00d4    EAGAIN        Optimistic lock acquired by another host
 VMK_NOT_MMAPABLE                 195887317   0xbad00d5    ENODEV        Object cannot be mmapped
 VMK_INVALID_CPU_AFFINITY         195887318   0xbad00d6    EINVAL        Invalid cpu affinity
 VMK_DEVICE_NOT_PARTOF_LV         195887319   0xbad00d7    ENXIO         Device does not contain a logical volume
 VMK_NO_SPACE                     195887320   0xbad00d8    ENOSPC        No space left on device
 VMK_VSI_INVALID_NODE_ID          195887321   0xbad00d9    EINVAL        Invalid vsi node ID
 VMK_TOO_MANY_USERS               195887322   0xbad00da    EUSERS        Too many users accessing this resource
 VMK_EALREADY                     195887323   0xbad00db    EALREADY      Operation already in progress
 VMK_BUF_TOO_SMALL                195887324   0xbad00dc    EINVAL        Buffer too small to complete the operation
 VMK_SNAPSHOT_DEV_DISALLOWED      195887325   0xbad00dd    EACCES        Snapshot device disallowed
 VMK_LVM_DEVICE_UNREACHABLE       195887326   0xbad00de    EIO           LVM device unreachable
 VMK_CPU_INVALID_RESOURCE_UNITS   195887327   0xbad00df    EINVAL        Invalid cpu resource units
 VMK_MEM_INVALID_RESOURCE_UNITS   195887328   0xbad00e0    EINVAL        Invalid memory resource units
 VMK_ABORTED                      195887329   0xbad00e1    ECANCELED     IO was aborted
 VMK_MEM_MIN_LT_RESERVED          195887330   0xbad00e2    ENOSPC        Memory min less than memory already reserved by children
 VMK_MEM_MIN_LT_CONSUMED          195887331   0xbad00e3    ENOSPC        Memory min less than memory required to support current consumption
 VMK_MEM_MAX_LT_CONSUMED          195887332   0xbad00e4    ENOSPC        Memory max less than memory required to support current consumption
 VMK_TIMEOUT_RETRY                195887333   0xbad00e5    ETIMEDOUT     Timeout (ok to retry)
 VMK_RESERVATION_LOST             195887334   0xbad00e6    EBUSY         Reservation Lost
 VMK_FS_STALE_METADATA            195887335   0xbad00e7    ENOENT        Cached metadata is stale
 VMK_NO_FCNTL_LOCK                195887336   0xbad00e8    ENOLCK        No fcntl lock slot left
 VMK_NO_FCNTL_LOCK_HOLDER         195887337   0xbad00e9    ENOLCK        No fcntl lock holder slot left
 VMK_NO_LICENSE                   195887338   0xbad00ea    EACCES        Not licensed to access VMFS volumes
 VMK_LVM_RETRY_OPERATION          195887339   0xbad00eb    EAGAIN        Transient LVM device condition, suggest retry
 VMK_SNAPSHOT_LV_INCOMPLETE       195887340   0xbad00ec    EAGAIN        Snapshot LV incomplete
 VMK_MEDIUM_NOT_FOUND             195887341   0xbad00ed    EIO           Medium not found
 VMK_MAX_PATHS_CLAIMED            195887342   0xbad00ee    ENOMEM        Maximum allowed SCSI paths have already  been claimed
 VMK_NOT_MOUNTABLE                195887343   0xbad00ef    ENODEV        Filesystem is not mountable
 VMK_MEMSIZE_GT_MEMSIZELIMIT      195887344   0xbad00f0    EINVAL        Memory size exceeds memSizeLimit
 VMK_GENERIC_LINUX_ERROR          732758016   0x2bad0000   EIO           Generic service console error

==== External Links ====

* [http://kb.vmware.com/kb/1004250 VMware KB: Decoding Purple Screen errors]

[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>11382f4931e80d4bfecf465635c371a3899ab68a</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:ESXi</title>
  <ns>14</ns>
  <id>437</id>
  <revision>
    <id>871</id>
    <timestamp>2009-05-12T07:56:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ESXi is the lightweight version of the bare metal hypervisor from VMware with a disk footprint of only 32MB.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">ESXi is the lightweight version of the bare metal hypervisor from VMware with a disk footprint of only 32MB.</text>
    <sha1>d6d7198422aa3c95177da5fad33b69491c6b9fba</sha1>
  </revision>
  <revision>
    <id>872</id>
    <parentid>871</parentid>
    <timestamp>2009-05-12T07:59:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">ESXi is the lightweight version of the bare metal hypervisor from VMware with a disk footprint of only 32MB.

[[Special:Categories]]</text>
    <sha1>e581baf885474202696e277e9920bbe0361d4dc3</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:ESX</title>
  <ns>14</ns>
  <id>438</id>
  <revision>
    <id>873</id>
    <timestamp>2009-05-12T08:00:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: ESX is the full blown version of the enterprise class bare metal hypervisor from VMware.  [[Special:Categories]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="112" xml:space="preserve">ESX is the full blown version of the enterprise class bare metal hypervisor from VMware.

[[Special:Categories]]</text>
    <sha1>9a927a183b5422f51548138b422554a59da18cd1</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:VM Management</title>
  <ns>14</ns>
  <id>439</id>
  <revision>
    <id>874</id>
    <timestamp>2009-05-12T08:01:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Virtual Machine Management category has links to tools for Virtual Machine Management  [[Special:Categories]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">Virtual Machine Management category has links to tools for Virtual Machine Management

[[Special:Categories]]</text>
    <sha1>2e06a8448b6b6ae8bc5dea1500d6a01d6745b2d0</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>PowerCLI: Report every VM added to vCenter in the last 30 days</title>
  <ns>0</ns>
  <id>440</id>
  <revision>
    <id>876</id>
    <timestamp>2009-05-12T08:05:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: At seemingly random intervals I get requests from management to report every Virtual Machine that was added/removed in the last x days. This has traditionally been a manual process, and on...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="588" xml:space="preserve">At seemingly random intervals I get requests from management to report every Virtual Machine that was added/removed in the last x days. This has traditionally been a manual process, and one that I loath.

While deploying a VM this morning I set up my normal tell me when your done one-liner…

 Get-Task|?{$_.Name -eq "CloneVM_Task"}|Wait-Task; `a`a`a

As I was typing I wondered how long a task’s history was kept, and if I could query it via the SDK? Low and behold not only can I but it’s too easy!

http://get-admin.com/blog/?p=725

[[Category: Powershell]] [[Category:PowerCLI]]</text>
    <sha1>2ef06930a767816ff7966235f37b0c66f223f915</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Virtu-Al: Lesson 1 Time Source</title>
  <ns>0</ns>
  <id>441</id>
  <revision>
    <id>878</id>
    <timestamp>2009-05-14T10:09:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: I thought I would help people learn the VI Toolkit whilst also creating a nice script which you can customise to your own environment, hopefully this is a script that will save you time in...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="737" xml:space="preserve">I thought I would help people learn the VI Toolkit whilst also creating a nice script which you can customise to your own environment, hopefully this is a script that will save you time in the future.

The script we are going to build together in step by step instructions is a Customisation script.

You have built your host and now have to go through the configuration and tweaks of all the after-build areas, you have to make sure that these are setup the same on each host so that things like VMotion and DRS work so what better than a script to help us limit the amount of mistakes when typing names or missing steps.

[http://www.virtu-al.net/2009/04/03/customisation-lesson-1-%E2%80%93-time-source/ Virtu-Al: Lesson 1 Time Source]</text>
    <sha1>9d14a4a3a675f4ccfb3c044572977d935aecfa22</sha1>
  </revision>
  <revision>
    <id>879</id>
    <parentid>878</parentid>
    <timestamp>2009-05-14T10:12:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="788" xml:space="preserve">I thought I would help people learn the VI Toolkit whilst also creating a nice script which you can customise to your own environment, hopefully this is a script that will save you time in the future.

The script we are going to build together in step by step instructions is a Customisation script.

You have built your host and now have to go through the configuration and tweaks of all the after-build areas, you have to make sure that these are setup the same on each host so that things like VMotion and DRS work so what better than a script to help us limit the amount of mistakes when typing names or missing steps.

[http://www.virtu-al.net/2009/04/03/customisation-lesson-1-%E2%80%93-time-source/ Virtu-Al: Lesson 1 Time Source]

[[Category: Powershell]] [[Category: VI-Toolkit]]</text>
    <sha1>8279f2e49414e521e191b5a8da98e6532e272120</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Virtu-Al: Lesson 2 Service and Firewall Configuration</title>
  <ns>0</ns>
  <id>442</id>
  <revision>
    <id>881</id>
    <timestamp>2009-05-14T10:19:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: In this post I will show you how to open some of the firewall ports on your host which are needed for various applications and services to talk to our ESX Host.  In the last post we setup ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="820" xml:space="preserve">In this post I will show you how to open some of the firewall ports on your host which are needed for various applications and services to talk to our ESX Host.

In the last post we setup the NTP server, I figure it would be a good start to make sure that now we have added the time server to our host we should start the NTP Service or as the Linux type people will know it, the NTP Daemon or NTPD.

So, if we use the Get-VmHostService cmdlet which is part of the VI Toolkit we can easily start our required service.  This cmdlet will give us a list of the services on our host and there current state ...

[http://www.virtu-al.net/2009/04/14/customisation-lesson-2-%E2%80%93-service-and-firewall-configuration/ Virtu-al: Lesson 2 - Service and firewall configuration]

[[Category: Powershell]] [[Category: VI-Toolkit]]</text>
    <sha1>c98092cc1abfd637ad1ab12a1c1f0af70d86b208</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Virtu-Al: Lesson 3 Networking</title>
  <ns>0</ns>
  <id>443</id>
  <revision>
    <id>882</id>
    <timestamp>2009-05-14T10:22:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Lets get down and dirty, by now you should not only starting to become familiar with the way things are working but also probably trying new things out, Great !  Now, as there are multiple...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="529" xml:space="preserve">Lets get down and dirty, by now you should not only starting to become familiar with the way things are working but also probably trying new things out, Great !

Now, as there are multiple ways of configuring your vSwitches/Portgroups and Nics I will explain a few ways that should show you the basics, everything else you should be able to work out from there...

[http://www.virtu-al.net/2009/04/29/customisation-lesson-3-%e2%80%93-networking/ Virtu-al: Lesson 3 - Networking]

[[Category: Powershell]] [[Category: VI-Toolkit]]</text>
    <sha1>7e15b2fbb3676305b3fe678d69c5e5b76b9dde99</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>883</id>
    <parentid>830</parentid>
    <timestamp>2009-05-14T10:36:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="156" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]</text>
    <sha1>f580d6a35980347023ecae6b653c355f94381738</sha1>
  </revision>
  <revision>
    <id>886</id>
    <parentid>883</parentid>
    <timestamp>2009-05-14T14:52:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="204" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]</text>
    <sha1>37dda720ec800f1ccb281c849798330f8a93a887</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Open Source VMFS Driver</title>
  <ns>0</ns>
  <id>444</id>
  <revision>
    <id>884</id>
    <timestamp>2009-05-14T10:38:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: This driver enables read-only access to files and folders on partitions formatted with the Virtual Machine File System (VMFS). VMFS is a clustered file system that is used by the VMware ES...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="822" xml:space="preserve">This driver enables read-only access to files and folders on partitions formatted with the Virtual Machine File System (VMFS). VMFS is a clustered file system that is used by the VMware ESX hosts to store virtual machines and virtual disk files.

The VMFS driver is developed and maintained by fluid Operations and is included in upcoming releases of the eCloudManager product, where it is used to allow enhanced features like offloaded backups of virtual machines hosted on VMware ESX hosts.

The VMFS driver comes with a command line interface (CLI) to mount and analyze VMFS volumes. The VMFS driver was tested on Linux and Windows based hosts, but should work on any platform that supports Java. The driver supports VMFS version 3 (VMFS3). 

[http://code.google.com/p/vmfs/ Open Source VMFS Driver]

[[Category: Java]]</text>
    <sha1>6a0c5490ad9014392fed9583827723e6bd237bf3</sha1>
  </revision>
  <revision>
    <id>885</id>
    <parentid>884</parentid>
    <timestamp>2009-05-14T10:39:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="883" xml:space="preserve">This driver enables read-only access to files and folders on partitions formatted with the Virtual Machine File System (VMFS). VMFS is a clustered file system that is used by the VMware ESX hosts to store virtual machines and virtual disk files.

The VMFS driver is developed and maintained by fluid Operations and is included in upcoming releases of the eCloudManager product, where it is used to allow enhanced features like offloaded backups of virtual machines hosted on VMware ESX hosts.

The VMFS driver comes with a command line interface (CLI) to mount and analyze VMFS volumes. The VMFS driver was tested on Linux and Windows based hosts, but should work on any platform that supports Java. The driver supports VMFS version 3 (VMFS3). 

[http://code.google.com/p/vmfs/ Open Source VMFS Driver]

[[Category: Java]] [[Category: Forensics]] [[Category: ESX]] [[Category: ESXi]]</text>
    <sha1>b114e71520d3f25aea20ea25534e5b9027551f53</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Protecting ESX VMFS Stores with Automation</title>
  <ns>0</ns>
  <id>445</id>
  <revision>
    <id>887</id>
    <timestamp>2009-05-14T14:57:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Some time ago I shared some interesting information about VMFS volumes that I found using direct analysis in my blog named [http://blog.laspina.ca/roller/Ubiquitous/entry/understanding_vmf...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1224" xml:space="preserve">Some time ago I shared some interesting information about VMFS volumes that I found using direct analysis in my blog named [http://blog.laspina.ca/roller/Ubiquitous/entry/understanding_vmfs_volumes Understanding VMFS volumes]. This spawned some discussions on the VMware Community forums and it became apparent that an automated backup of the critical VMFS info could be useful in the event of an undesirable security event that impacts our system availability. By creating a simple backup script process we can provide the ability to recover much more quickly from such events. In this howto guide we will enable this process with a cron job using the existing /etc/cron.daily/ job location directory. We simply need to copy an automation script to this location and it will run daily. Or if your change rate is less frequent maybe the /etc/cron.weekly location is more suitable.  ...

[http://blog.laspina.ca/roller/Ubiquitous/entry/understanding_vmfs_volumes Ubiquitous: Protecting ESX VMFS Stores with Automation]

See also:
[http://blog.laspina.ca/roller/Ubiquitous/entry/additional_vmfs_backup_automation_script Ubiquitous: Additional VMFS Backup Automation script features]

[[Category: Bash]] [[Category: Forensics]]</text>
    <sha1>14faa9ecc48bc315397ac27f23bdf129f9c01c9e</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:Java</title>
  <ns>14</ns>
  <id>446</id>
  <revision>
    <id>889</id>
    <timestamp>2009-05-15T10:28:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Java is a programming language originally developed by James Gosling at Sun Microsystems and released in 1995 as a core component of Sun Microsystems' Java</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve">Java is a programming language originally developed by James Gosling at Sun Microsystems and released in 1995 as a core component of Sun Microsystems' Java</text>
    <sha1>45bc216e17ea59c35a20dc62e211fa3490969a9f</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:.net</title>
  <ns>14</ns>
  <id>447</id>
  <revision>
    <id>890</id>
    <timestamp>2009-05-15T10:29:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: The .NET Framework is a software framework that can be installed on computers running Microsoft Windows operating systems</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="121" xml:space="preserve">The .NET Framework is a software framework that can be installed on computers running Microsoft Windows operating systems</text>
    <sha1>7e0aec893f03d3d6730b28ddc7a919cfbb29e01c</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:Bash</title>
  <ns>14</ns>
  <id>448</id>
  <revision>
    <id>891</id>
    <timestamp>2009-05-15T10:32:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Bash is a free software Unix shell written for the GNU Project. Its name is an acronym which stands for Bourne-again shell</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">Bash is a free software Unix shell written for the GNU Project. Its name is an acronym which stands for Bourne-again shell</text>
    <sha1>1c2fb70d95a7ab9b44c510039ff7e8b7cdb8e079</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:CLI</title>
  <ns>14</ns>
  <id>449</id>
  <revision>
    <id>892</id>
    <timestamp>2009-05-15T10:33:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: A command-line interface (CLI) is a mechanism for interacting with a computer operating system or software by typing commands to perform specific tasks</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">A command-line interface (CLI) is a mechanism for interacting with a computer operating system or software by typing commands to perform specific tasks</text>
    <sha1>fed8270bd7a4911f15cf7607fce3c1c0fb059372</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:Forensics</title>
  <ns>14</ns>
  <id>450</id>
  <revision>
    <id>893</id>
    <timestamp>2009-05-15T10:34:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: To recover data in the event of a hardware or software failure.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="63" xml:space="preserve">To recover data in the event of a hardware or software failure.</text>
    <sha1>2dcde9314f24367febc5e2ecccaa24446211085a</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:Host Management</title>
  <ns>14</ns>
  <id>451</id>
  <revision>
    <id>894</id>
    <timestamp>2009-05-15T10:35:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Tools to help you manage your VMware hosts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42" xml:space="preserve">Tools to help you manage your VMware hosts</text>
    <sha1>7fcfb09b1295dcbf2c36ee1d5b8e36fed7e36a83</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:Hypervisor</title>
  <ns>14</ns>
  <id>452</id>
  <revision>
    <id>895</id>
    <timestamp>2009-05-15T10:36:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Software that directly interacts with the hypervisor. A hypervisor, also called virtual machine monitor (VMM), is a computer software/hardware platform virtualization software that allows ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="247" xml:space="preserve">Software that directly interacts with the hypervisor. A hypervisor, also called virtual machine monitor (VMM), is a computer software/hardware platform virtualization software that allows multiple operating systems to run on one hardware platform.</text>
    <sha1>8b4aba3d73d1b2d2a5cdf17d46244c2c02f9324e</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:Perl</title>
  <ns>14</ns>
  <id>453</id>
  <revision>
    <id>896</id>
    <timestamp>2009-05-15T10:37:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Software written in perl. Perl is a high-level, general-purpose, interpreted, dynamic programming language. Perl was originally developed by Larry Wall, a linguist working as a systems adm...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="296" xml:space="preserve">Software written in perl. Perl is a high-level, general-purpose, interpreted, dynamic programming language. Perl was originally developed by Larry Wall, a linguist working as a systems administrator for NASA, in 1987, as a general purpose Unix scripting language to make report processing easier.</text>
    <sha1>d813e1c05769633e76929534b4c9a7a714a129cf</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:PowerCLI</title>
  <ns>14</ns>
  <id>454</id>
  <revision>
    <id>897</id>
    <timestamp>2009-05-15T10:38:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Software written in PowerCLI. PowerCLI is the SDK software library for managing vSphere hosts.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="94" xml:space="preserve">Software written in PowerCLI. PowerCLI is the SDK software library for managing vSphere hosts.</text>
    <sha1>396dec5dda73a090907e6d02269edf5801018541</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:Python</title>
  <ns>14</ns>
  <id>455</id>
  <revision>
    <id>898</id>
    <timestamp>2009-05-15T10:39:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Software written in Python. Python is a general-purpose high-level programming language. Its design philosophy emphasizes code readability.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="139" xml:space="preserve">Software written in Python. Python is a general-purpose high-level programming language. Its design philosophy emphasizes code readability.</text>
    <sha1>a9f1b175aee4c7ce3faf659a3705033f1770470b</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Category:VI-Toolkit</title>
  <ns>14</ns>
  <id>456</id>
  <revision>
    <id>899</id>
    <timestamp>2009-05-15T10:42:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Software utilizing [[VI Toolkit]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="33" xml:space="preserve">Software utilizing [[VI Toolkit]]</text>
    <sha1>a2a9e3756390185bbe24f8df4fdd6b332f5e3fb9</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>900</id>
    <parentid>702</parentid>
    <timestamp>2009-05-15T10:47:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2735" xml:space="preserve">== VI Toolkit ==
'' December 11, 2008 ''
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since Januari 3rd, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

==== Contribute / help out ====
This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>59b9dc3b9ada1a4a41ff15212cbb6bc703ba55bb</sha1>
  </revision>
  <revision>
    <id>903</id>
    <parentid>900</parentid>
    <timestamp>2009-05-15T11:03:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2716" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since Januari 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

==== Contribute / help out ====
This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>1c93d0e8cf3a799258067db3698f01d1f1ac55bd</sha1>
  </revision>
</page>
<page arvcontinue="20090401082112|854">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>901</id>
    <parentid>704</parentid>
    <timestamp>2009-05-15T10:55:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1800" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages. Partly done
* Add "what's new" to the main page
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* &lt;s&gt;Find a better way to present what's available on the site, improve ways to restructure the data. &lt;s&gt; The support for category tree at the main page now gives a much easier way to navigate the site. But it never hurts to find better ways as this doesn't scale too well (look at the vimsh category for example)
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?

[[Category: website]]</text>
    <sha1>21f19869f744cd0adcb767a4cd235d4f707260ee</sha1>
  </revision>
  <revision>
    <id>902</id>
    <parentid>901</parentid>
    <timestamp>2009-05-15T10:55:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1801" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages. Partly done
* Add "what's new" to the main page
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* &lt;s&gt;Find a better way to present what's available on the site, improve ways to restructure the data. &lt;/s&gt; The support for category tree at the main page now gives a much easier way to navigate the site. But it never hurts to find better ways as this doesn't scale too well (look at the vimsh category for example)
* Improve main page
* Add example code

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?

[[Category: website]]</text>
    <sha1>d2a5dbe4691ebb6216b3217fa5c980078ecf3864</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>904</id>
    <parentid>833</parentid>
    <timestamp>2009-05-19T08:57:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2809" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

[[APC/APCUPSD ESX/ESXi Host shutdown script]]

==== Perl scripts ====
[[Recover vmx from log file]]

==== AppleScript ====

[http://communities.vmware.com/thread/122793 AppleScript to Run Virtual Machine and switch to Full Screen View or Unity View at Login]</text>
    <sha1>dc65c00c0e8a70d1d12568c01828f6c491bb6175</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>905</id>
    <parentid>880</parentid>
    <timestamp>2009-05-19T09:00:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1874" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>8593c10411f26bb9d44e6af61cad6ca1c5015f08</sha1>
  </revision>
  <revision>
    <id>907</id>
    <parentid>905</parentid>
    <timestamp>2009-05-19T09:04:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1918" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>b680adb635bcccf3c370a92be37e96ca4226fbab</sha1>
  </revision>
  <revision>
    <id>909</id>
    <parentid>907</parentid>
    <timestamp>2009-05-19T09:07:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2014" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>726f122df3d7849f7ea5518b7327cf7162843211</sha1>
  </revision>
  <revision>
    <id>914</id>
    <parentid>909</parentid>
    <timestamp>2009-05-19T15:37:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2046" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>98e90ff644b7395ad265395efda5b6632489de81</sha1>
  </revision>
  <revision>
    <id>916</id>
    <parentid>914</parentid>
    <timestamp>2009-05-19T15:46:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2099" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>745fe5e036535466e1dc04acf751bfc3446520a1</sha1>
  </revision>
  <revision>
    <id>918</id>
    <parentid>916</parentid>
    <timestamp>2009-05-23T09:37:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added link to Primalforms (Thanks Stu!)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2283" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>35c257c69ae5e451a0f842ed159ad2556dd276ed</sha1>
  </revision>
  <revision>
    <id>919</id>
    <parentid>918</parentid>
    <timestamp>2009-05-23T09:39:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2320" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>491f5af507a2d2ba6da7f3fc76b7bf02c1af7885</sha1>
  </revision>
  <revision>
    <id>921</id>
    <parentid>919</parentid>
    <timestamp>2009-05-26T11:42:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2347" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>483dc19341443eda4d7bfde43ad23c8fdfa913d7</sha1>
  </revision>
  <revision>
    <id>946</id>
    <parentid>921</parentid>
    <timestamp>2009-06-02T09:10:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Thanks to the person who mentioned this little nugget on twitter (sorry forgot who it was)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2519" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [[http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>10579a5d10f0833a87573dd04127b6814cdb8cb0</sha1>
  </revision>
  <revision>
    <id>947</id>
    <parentid>946</parentid>
    <timestamp>2009-06-02T09:11:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2517" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>d04925d6b1f9ccb42cb45fe84eddc888d9300cde</sha1>
  </revision>
  <revision>
    <id>948</id>
    <parentid>947</parentid>
    <timestamp>2009-06-04T06:57:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to MS Script center (thank you Hal)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2605" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>4807fad52c924618347f10e956b55301058150c1</sha1>
  </revision>
  <revision>
    <id>950</id>
    <parentid>948</parentid>
    <timestamp>2009-06-05T09:34:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to toolkit FAQ (thanks William Lam)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2716" xml:space="preserve">If you are not running windows 2008 and don't have PowerShell installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>98e49d8bf8ce8e5eaa28b6cea7663379ae0fc541</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Restart VMware Tools on all Windows VM's</title>
  <ns>0</ns>
  <id>457</id>
  <revision>
    <id>906</id>
    <timestamp>2009-05-19T09:02:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: After reading the post on http://www.virtualvcp.com/content/view/82/1/ about the VMware Tools status \u201cnot running\u201d and in particular the part about the preferred work around:    ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="989" xml:space="preserve">After reading the post on http://www.virtualvcp.com/content/view/82/1/ about the VMware Tools status \u201cnot running\u201d and in particular the part about the preferred work around:

    I find that restarting the VMware Tools Service in the guest OS always gets by the problem, but loggin into every single VM that reports the wrong status for it\u2019s VMware Tools could be a bit of a drag. So I choose to do this remotely rather that logging on to each VM.

    From any Windows workstation/server, open a command pompt and run:

        sc \\{vm-name-or-ip-address} stop "VMTools"
        sc \\{vm-name-or-ip-address} start "VMTools"

I thought that can be done via Powershell and the VI Toolkit. So I created the following script that will restart the VMware Tools service on every running Windows VM. 

[http://ict-freak.nl/2009/05/05/restart-vmware-tools-on-all-windows-vms/ ICT-Freak: Restart VMware Tools on all Windows VM's]

[[Category: VI-Toolkit]] [[Category: Powershell]]</text>
    <sha1>7bbfba4d8aa47ff09985156a8c3852519b7ffa1b</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Manage VMware Server with PowerShell</title>
  <ns>0</ns>
  <id>458</id>
  <revision>
    <id>908</id>
    <timestamp>2009-05-19T09:06:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>New page: Blogger John Tuffin has made an entry about his experiments managing VMware Server 2.0 Beta with PowerShell. To summarize, you can manage VMware Server with PowerShell, in much the same wa...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="838" xml:space="preserve">Blogger John Tuffin has made an entry about his experiments managing VMware Server 2.0 Beta with PowerShell. To summarize, you can manage VMware Server with PowerShell, in much the same way you manage VMware ESX.

Thngs that will work include:

    * Listing, creating and deleting VMs.
    * Starting, stopping and resetting VMs.
    * Creating snapshot of VMs.

Things that won't work include things that VMware ESX supports but VMware Server doesn't. This is a pretty long list, but some highlight include:

    * You can't create resource pools in VMware Server.
    * You can't utilize advanced networking options such as virtual switches in VMware Server.
    * You can't VMotion VMs between VMware Server instances.

http://blogs.vmware.com/vipowershell/2008/04/you-can-manage.html

[[Category: VI-Toolkit]][[Category: Powershell]]</text>
    <sha1>e5bbe190a0fe32a71ea6d5b30ba50ba79a5f6296</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>910</id>
    <parentid>903</parentid>
    <timestamp>2009-05-19T11:25:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3061" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since Januari 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

==== Contribute / help out ====
This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics, search and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you. 

Search tip:
For searching your search term MUST be at least 4 characters long so searching for "VT" or "ESX" will return nothing while there's still content describing this. Instead try another longer related search term like "BIOS" or "backup" for what you are trying to find.

As extra help, the categories are listed below as well.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>1190425abe4c3386da7767602ddf81ed21922796</sha1>
  </revision>
  <revision>
    <id>940</id>
    <parentid>910</parentid>
    <timestamp>2009-05-26T20:57:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3126" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since Januari 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

==== Contribute / help out ====
This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics, search and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you. 

Search tip:
For searching your search term MUST be at least 4 characters long so searching for "VT" or "ESX" will return nothing while there's still content describing this. Instead try another longer related search term like "BIOS" or "backup" for what you are trying to find.

As extra help, the categories are listed below as well.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware Artwork&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>2c22f511fe81ea52f7332cc646f9f88b903e878c</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>ESX CLI Commands</title>
  <ns>0</ns>
  <id>416</id>
  <revision>
    <id>911</id>
    <parentid>869</parentid>
    <timestamp>2009-05-19T11:28:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2724" xml:space="preserve">==== ESX CLI Commands ====

Virtual Infrastructure ESX has a service console which can be used to management purposes.
This is a light weight linux based (RHEL3) Virtual Machine which has special privileges that can be used in order to manage your host and Virtual Machines.
Down here we will be trying to document the available commands that you can use on this service console from the so called Command Line Interface (CLI).

In ESXi (3.x) the service console has been removed from the host and there's only a remote alternative available, which is called the [[RCLI]].
The chapter here only contains the documentation for the full blown version not the RCLI.

Any changes made to the configuration of the host will not be seen by vCenter Server or the host itself until you restart the vmware-hostd daemon. By restarting this daemon, the configuration file /etc/vmware/esx.conf will be re-read.

 service mgmt-vmware restart

will restart this daemon.


==== The available commands ====

 [[dmidecode]]
 [[esxcfg-advcfg]]      
 [[esxcfg-auth]]        
 [[esxcfg-boot]]        
 [[esxcfg-configcheck]]
 [[esxcfg-dumppart]]   
 [[esxcfg-firewall]]   
 [[esxcfg-hwiscsi]]    
 [[esxcfg-info]]     
 [[esxcfg-init]]
 [[esxcfg-linuxnet]]
 [[esxcfg-module]]
 [[esxcfg-mpath]]
 [[esxcfg-nas]]
 [[esxcfg-nics]]
 [[esxcfg-pciid]]
 [[esxcfg-rescan]]
 [[esxcfg-resgrp]]
 [[esxcfg-route]]
 [[esxcfg-swiscsi]]
 [[esxcfg-upgrade]]
 [[esxcfg-vmhbadevs]]
 [[esxcfg-vmknic]]
 [[esxcfg-vswif]]
 [[esxcfg-vswitch]]
 [[esxupdate]]
 [[vcbExport]]
 [[vcbMounter]]
 [[vcbResAll]]
 [[vcbRestore]]
 [[vcbSnapAll]]
 [[vcbSnapshot]]
 [[vcbUtil]]
 [[vcbVmName]]
 [[vdf]]
 [[vimsh]]
 [[vmfsqhtool]]
 [[vmfsqueuetool]]
 [[vmkchdev]]
 [[vmkdump]]
 [[vmkerrcode]]
 [[vmkfstools]]
 [[vmkiscsid]]
 [[vmkiscsi-device]]
 [[vmkiscsi-ls]]
 [[vmkiscsi-tool]]
 [[vmkiscsi-util]]
 [[vmkloader]]
 [[vmkload_mod]]
 [[vmklogger]]
 [[vmkpcidivy]]
 [[vmkping]]
 [[vmkuptime.pl]]
 [[vmres.pl]]
 [[vmsnap_all]]
 [[vmsnap.pl]]
 [[vmstat]]
 [[vm-support]]
 [[vmware]]
 [[vmware-authd]]
 [[vmware-autopoweron.sh]]
 [[vmware-cmd]]
 [[vmware-configcheck]]
 [[vmware-config.pl]]
 [[vmware-hostd]]
 [[vmware-hostd-support]]
 [[vmware-mkinitrd]]
 [[vmware-vim-cmd]]         
 [[vmware-vimdump]]         
 [[vmware-vimsh]]
 [[vmware-watchdog]]
 [[vmware-webAccess]]

==== External Links ====

* [http://download3.vmware.com/vmworld/2006/tac9685.pdf VMworld 2006: Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

* [http://www.rtfm-ed.co.uk/docs/vmwdocs/ESX3.x-VC2.x-ServiceConsole-Guide.pdf RTFM Education: ESX3.x Service Console Guide]

* [http://www.b2v.co.uk/b2vguide2vmware.htm B2V Guide to VMware ESX Server 2.x]

[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>a27f533d51e8569434eb585c192ce947fb0102a9</sha1>
  </revision>
  <revision>
    <id>952</id>
    <parentid>911</parentid>
    <timestamp>2009-06-08T14:55:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to ESX 4 CLI man page by Bouke Groenescheij</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2832" xml:space="preserve">==== ESX CLI Commands ====

Virtual Infrastructure ESX has a service console which can be used to management purposes.
This is a light weight linux based (RHEL3) Virtual Machine which has special privileges that can be used in order to manage your host and Virtual Machines.
Down here we will be trying to document the available commands that you can use on this service console from the so called Command Line Interface (CLI).

In ESXi (3.x) the service console has been removed from the host and there's only a remote alternative available, which is called the [[RCLI]].
The chapter here only contains the documentation for the full blown version not the RCLI.

Any changes made to the configuration of the host will not be seen by vCenter Server or the host itself until you restart the vmware-hostd daemon. By restarting this daemon, the configuration file /etc/vmware/esx.conf will be re-read.

 service mgmt-vmware restart

will restart this daemon.


==== The available commands ====

 [[dmidecode]]
 [[esxcfg-advcfg]]      
 [[esxcfg-auth]]        
 [[esxcfg-boot]]        
 [[esxcfg-configcheck]]
 [[esxcfg-dumppart]]   
 [[esxcfg-firewall]]   
 [[esxcfg-hwiscsi]]    
 [[esxcfg-info]]     
 [[esxcfg-init]]
 [[esxcfg-linuxnet]]
 [[esxcfg-module]]
 [[esxcfg-mpath]]
 [[esxcfg-nas]]
 [[esxcfg-nics]]
 [[esxcfg-pciid]]
 [[esxcfg-rescan]]
 [[esxcfg-resgrp]]
 [[esxcfg-route]]
 [[esxcfg-swiscsi]]
 [[esxcfg-upgrade]]
 [[esxcfg-vmhbadevs]]
 [[esxcfg-vmknic]]
 [[esxcfg-vswif]]
 [[esxcfg-vswitch]]
 [[esxupdate]]
 [[vcbExport]]
 [[vcbMounter]]
 [[vcbResAll]]
 [[vcbRestore]]
 [[vcbSnapAll]]
 [[vcbSnapshot]]
 [[vcbUtil]]
 [[vcbVmName]]
 [[vdf]]
 [[vimsh]]
 [[vmfsqhtool]]
 [[vmfsqueuetool]]
 [[vmkchdev]]
 [[vmkdump]]
 [[vmkerrcode]]
 [[vmkfstools]]
 [[vmkiscsid]]
 [[vmkiscsi-device]]
 [[vmkiscsi-ls]]
 [[vmkiscsi-tool]]
 [[vmkiscsi-util]]
 [[vmkloader]]
 [[vmkload_mod]]
 [[vmklogger]]
 [[vmkpcidivy]]
 [[vmkping]]
 [[vmkuptime.pl]]
 [[vmres.pl]]
 [[vmsnap_all]]
 [[vmsnap.pl]]
 [[vmstat]]
 [[vm-support]]
 [[vmware]]
 [[vmware-authd]]
 [[vmware-autopoweron.sh]]
 [[vmware-cmd]]
 [[vmware-configcheck]]
 [[vmware-config.pl]]
 [[vmware-hostd]]
 [[vmware-hostd-support]]
 [[vmware-mkinitrd]]
 [[vmware-vim-cmd]]         
 [[vmware-vimdump]]         
 [[vmware-vimsh]]
 [[vmware-watchdog]]
 [[vmware-webAccess]]

==== External Links ====

* [http://download3.vmware.com/vmworld/2006/tac9685.pdf VMworld 2006: Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

* [http://www.rtfm-ed.co.uk/docs/vmwdocs/ESX3.x-VC2.x-ServiceConsole-Guide.pdf RTFM Education: ESX3.x Service Console Guide]

* [http://www.b2v.co.uk/b2vguide2vmware.htm B2V Guide to VMware ESX Server 2.x]

* [http://www.jume.nl/index.php?option=com_content&amp;task=view&amp;id=115&amp;Itemid=1 Jume: ESX vSphere Man pages]


[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>c6b21ff508b7633fa4985f0d913f0a201aa770c8</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Dmidecode</title>
  <ns>0</ns>
  <id>459</id>
  <revision>
    <id>912</id>
    <timestamp>2009-05-19T11:39:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'from the man command:   Reformatting dmidecode(8), please wait... DMIDECODE(8)                                                      DMIDECODE(8)  ==== NAME ====        dmidecode ...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8806" xml:space="preserve">from the man command: 

Reformatting dmidecode(8), please wait...
DMIDECODE(8)                                                      DMIDECODE(8)

==== NAME ====
       dmidecode - DMI table decoder

==== SYNOPSIS ====
       dmidecode [OPTIONS]

==== DESCRIPTION ====
dmidecode  is a tool for dumping a computerâs DMI (some say SMBIOS) table contents in a human-readable format. This table contains a description  of  the  systemâs  hardware  components,  as well as other useful pieces of information such as serial numbers and BIOS revision.  Thanks to  this  table,  you  can  retrieve this information without having to probe for the actual hardware.  While this is a good point in terms  of report  speed  and  safeness, this also makes the presented information possibly unreliable.

The DMI table doesnât only describe what the system is  currently  made of,  it  also  can  report the possible evolutions (such as the fastest supported CPU or the maximal amount of memory supported).

SMBIOS stands for System Management BIOS, while DMI stands for  Desktop Management  Interface. Both standards are tightly related and developed by the DMTF (Desktop Management Task Force).

As you run it, dmidecode will try to locate the DMI table. If  it  succeeds, it will then parse this table and display a list of records like
this one:

       Handle 0x0002
           DMI type 2, 8 bytes.
           Base Board Information
               Manufacturer: Intel
               Product Name: C440GX+
               Version: 727281-001
               Serial Number: INCY92700942


Each record has:

 * A handle. This is a unique identifier, which allows records to reference  each  other.  For  example, processor records usually reference cache memory records using their handles.

 * A type. The SMBIOS specification defines different types of  elements a  computer  can  be  made  of. In this example, the type is 2, which means that the record contains "Base Board Information".

 * A size. Each record has a 4-byte header (2 for the handle, 1 for  the type,  1  for  the  size),  the rest is used by the record data. This value doesn't take text strings into account (these are placed at the end of the record), so the actual length of the record may be (and is often) greater than the displayed value.

* Decoded values. The information presented of course  depends  on  the type of record. Here, we learn about the boardâs manufacturer, model, version and serial number.

OPTIONS
       -d, --dev-mem FILE
              Read memory from device FILE (default: /dev/mem)

       -q, --quiet
              Be less verbose. Unknown, inactive and OEM-specific entries  are
              not displayed. Meta-data and handle references are hidden. Mutuâ
              ally exclusive with --dump.

       -s, --string KEYWORD
              Only display the value of the DMI string identified by  KEYWORD.
              KEYWORD  must be a keyword from the following list: bios-vendor,
              bios-version,  bios-release-date,  system-manufacturer,  system-
              product-name,  system-version,  system-serial-number, baseboard-
              manufacturer, baseboard-product-name,  baseboard-version,  baseâ
              board-serial-number,  baseboard-asset-tag, chassis-manufacturer,
              chassis-version, chassis-serial-number, chassis-asset-tag,  proâ
              cessor-manufacturer,  processor-version.   Each  keyword  correâ
              sponds to a given DMI type and a given offset within this  entry
              type.   Not all strings may be meaningful or even defined on all
              systems. Some keywords may return more than one result  on  some
              systems  (e.g.   processor-version on a multi-processor system).
              If KEYWORD is not provided or not valid, a  list  of  all  valid
              keywords  is  printed  and  dmidecode exits with an error.  This
              option cannot be used  more  than  once,  and  implies  --quiet.
              Mutually exclusive with --type and --dump.

       -t, --type TYPE
              Only  display the entries of type TYPE. TYPE can be either a DMI
              type number, or a comma-separated list of  type  numbers,  or  a
              keyword  from the following list: bios, system, baseboard, chasâ
              sis, processor, memory, cache, connector, slot. Refer to the DMI
              TYPES  section  below  for details.  If this option is used more
              than once, the set of displayed entries will be the union of all
              the  given  types.  If TYPE is not provided or not valid, a list
              of all valid keywords is printed and  dmidecode  exits  with  an
              error.  Mutually exclusive with --string.

       -u, --dump
              Do  not  decode  the entries, dump their contents as hexadecimal
              instead.  Note that this is still a text output, no binary  data
              will  be thrown upon you. The strings attached to each entry are
              displayed as both hexadecimal and ASCII. This option  is  mainly
              useful  for  debugging.   Mutually  exclusive  with  --quiet and
              --string.

       -h, --help
              Display usage information and exit

       -V, --version
              Display the version and exit

DMI TYPES
       The SMBIOS specification defines the following DMI types:

       Type   Information
       ----------------------------------------
          0   BIOS
          1   System
          2   Base Board
          3   Chassis
          4   Processor
          5   Memory Controller
          6   Memory Module
          7   Cache
          8   Port Connector
          9   System Slots
         10   On Board Devices
         11   OEM Strings
         12   System Configuration Options
         13   BIOS Language
         14   Group Associations
         15   System Event Log
         16   Physical Memory Array
         17   Memory Device
         18   32-bit Memory Error
         19   Memory Array Mapped Address
         20   Memory Device Mapped Address
         21   Built-in Pointing Device
         22   Portable Battery
         23   System Reset
         24   Hardware Security
         25   System Power Controls
         26   Voltage Probe
         27   Cooling Device
         28   Temperature Probe
         29   Electrical Current Probe
         30   Out-of-band Remote Access
         31   Boot Integrity Services
         32   System Boot
         33   64-bit Memory Error
         34   Management Device
         35   Management Device Component
         36   Management Device Threshold Data
         37   Memory Channel
         38   IPMI Device
         39   Power Supply

       Additionally, type 126 is used for disabled entries,  type  127  is  an
       end-of-table  marker,  and  types 128 to 255 are for OEM-specific data.
       dmidecode will display these entries  by  default,  but  cannot  decode
       them.

       Keywords can be used instead of type numbers with --type.  Each keyword
       is equivalent to a list of type numbers:

       Keyword     Types
       ------------------------------
       bios        0, 13
       system      1, 12, 15, 23, 32
       baseboard   2, 10
       chassis     3
       processor   4
       memory      5, 6, 16, 17
       cache       7
       connector   8
       slot        9

       Keywords are matched case-insensitively. The  following  command  lines
       are equivalent:

 * dmidecode --type 0 --type 13

 * dmidecode --type 0,13

 * dmidecode --type 0 --type 13

 * dmidecode --type 0,13

 * dmidecode --type bios

 * dmidecode --type BIOS

FILES
       /dev/mem

BUGS
       More often than not, information contained in the DMI tables is inaccuâ
       rate, incomplete or simply wrong.

AUTHORS
       Alan Cox, Jean Delvare

SEE ALSO
       biosdecode(8), mem(4), ownership(8), vpddecode(8)

dmidecode                         August 2005                     DMIDECODE(8)


==== Example output ====

Here's a snippet of output on an ESX host when displaying memory info:

 Handle 0x0028
        DMI type 17, 27 bytes.
        Memory Device
                Array Handle: 0x0025
                Error Information Handle: No Error
                Total Width: 76 bits
                Data Width: 72 bits
                Size: 1024 MB
                Form Factor: DIMM
                Set: 1
                Locator: DIMM 2A
                Bank Locator: Bank0 Bank1
                Type: DDR
                Type Detail: Synchronous
                Speed: 266 MHz (3.8 ns)
                Manufacturer: Not Specified
                Serial Number: Not Specified
                Asset Tag: Not Specified
                Part Number: Not Specified</text>
    <sha1>4f17a237f420660fb578c75795136dc3e8a293ea</sha1>
  </revision>
  <revision>
    <id>913</id>
    <parentid>912</parentid>
    <timestamp>2009-05-19T11:40:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8797" xml:space="preserve">from the man command: 

Reformatting dmidecode(8), please wait...
DMIDECODE(8)                                                      DMIDECODE(8)

==== NAME ====
       dmidecode - DMI table decoder

==== SYNOPSIS ====
       dmidecode [OPTIONS]

==== DESCRIPTION ====
dmidecode  is a tool for dumping a computerâs DMI (some say SMBIOS) table contents in a human-readable format. This table contains a description  of  the  systemâs  hardware  components,  as well as other useful pieces of information such as serial numbers and BIOS revision.  Thanks to  this  table,  you  can  retrieve this information without having to probe for the actual hardware.  While this is a good point in terms  of report  speed  and  safeness, this also makes the presented information possibly unreliable.

The DMI table doesnât only describe what the system is  currently  made of,  it  also  can  report the possible evolutions (such as the fastest supported CPU or the maximal amount of memory supported).

SMBIOS stands for System Management BIOS, while DMI stands for  Desktop Management  Interface. Both standards are tightly related and developed by the DMTF (Desktop Management Task Force).

As you run it, dmidecode will try to locate the DMI table. If  it  succeeds, it will then parse this table and display a list of records like
this one:

       Handle 0x0002
           DMI type 2, 8 bytes.
           Base Board Information
               Manufacturer: Intel
               Product Name: C440GX+
               Version: 727281-001
               Serial Number: INCY92700942


Each record has:

* A handle. This is a unique identifier, which allows records to reference  each  other.  For  example, processor records usually reference cache memory records using their handles.

* A type. The SMBIOS specification defines different types of  elements a  computer  can  be  made  of. In this example, the type is 2, which means that the record contains "Base Board Information".

* A size. Each record has a 4-byte header (2 for the handle, 1 for  the type,  1  for  the  size),  the rest is used by the record data. This value doesn't take text strings into account (these are placed at the end of the record), so the actual length of the record may be (and is often) greater than the displayed value.

* Decoded values. The information presented of course  depends  on  the type of record. Here, we learn about the boardâs manufacturer, model, version and serial number.

OPTIONS
       -d, --dev-mem FILE
              Read memory from device FILE (default: /dev/mem)

       -q, --quiet
              Be less verbose. Unknown, inactive and OEM-specific entries  are
              not displayed. Meta-data and handle references are hidden. Mutuâ
              ally exclusive with --dump.

       -s, --string KEYWORD
              Only display the value of the DMI string identified by  KEYWORD.
              KEYWORD  must be a keyword from the following list: bios-vendor,
              bios-version,  bios-release-date,  system-manufacturer,  system-
              product-name,  system-version,  system-serial-number, baseboard-
              manufacturer, baseboard-product-name,  baseboard-version,  baseâ
              board-serial-number,  baseboard-asset-tag, chassis-manufacturer,
              chassis-version, chassis-serial-number, chassis-asset-tag,  proâ
              cessor-manufacturer,  processor-version.   Each  keyword  correâ
              sponds to a given DMI type and a given offset within this  entry
              type.   Not all strings may be meaningful or even defined on all
              systems. Some keywords may return more than one result  on  some
              systems  (e.g.   processor-version on a multi-processor system).
              If KEYWORD is not provided or not valid, a  list  of  all  valid
              keywords  is  printed  and  dmidecode exits with an error.  This
              option cannot be used  more  than  once,  and  implies  --quiet.
              Mutually exclusive with --type and --dump.

       -t, --type TYPE
              Only  display the entries of type TYPE. TYPE can be either a DMI
              type number, or a comma-separated list of  type  numbers,  or  a
              keyword  from the following list: bios, system, baseboard, chasâ
              sis, processor, memory, cache, connector, slot. Refer to the DMI
              TYPES  section  below  for details.  If this option is used more
              than once, the set of displayed entries will be the union of all
              the  given  types.  If TYPE is not provided or not valid, a list
              of all valid keywords is printed and  dmidecode  exits  with  an
              error.  Mutually exclusive with --string.

       -u, --dump
              Do  not  decode  the entries, dump their contents as hexadecimal
              instead.  Note that this is still a text output, no binary  data
              will  be thrown upon you. The strings attached to each entry are
              displayed as both hexadecimal and ASCII. This option  is  mainly
              useful  for  debugging.   Mutually  exclusive  with  --quiet and
              --string.

       -h, --help
              Display usage information and exit

       -V, --version
              Display the version and exit

DMI TYPES
       The SMBIOS specification defines the following DMI types:

       Type   Information
       ----------------------------------------
          0   BIOS
          1   System
          2   Base Board
          3   Chassis
          4   Processor
          5   Memory Controller
          6   Memory Module
          7   Cache
          8   Port Connector
          9   System Slots
         10   On Board Devices
         11   OEM Strings
         12   System Configuration Options
         13   BIOS Language
         14   Group Associations
         15   System Event Log
         16   Physical Memory Array
         17   Memory Device
         18   32-bit Memory Error
         19   Memory Array Mapped Address
         20   Memory Device Mapped Address
         21   Built-in Pointing Device
         22   Portable Battery
         23   System Reset
         24   Hardware Security
         25   System Power Controls
         26   Voltage Probe
         27   Cooling Device
         28   Temperature Probe
         29   Electrical Current Probe
         30   Out-of-band Remote Access
         31   Boot Integrity Services
         32   System Boot
         33   64-bit Memory Error
         34   Management Device
         35   Management Device Component
         36   Management Device Threshold Data
         37   Memory Channel
         38   IPMI Device
         39   Power Supply

       Additionally, type 126 is used for disabled entries,  type  127  is  an
       end-of-table  marker,  and  types 128 to 255 are for OEM-specific data.
       dmidecode will display these entries  by  default,  but  cannot  decode
       them.

       Keywords can be used instead of type numbers with --type.  Each keyword
       is equivalent to a list of type numbers:

       Keyword     Types
       ------------------------------
       bios        0, 13
       system      1, 12, 15, 23, 32
       baseboard   2, 10
       chassis     3
       processor   4
       memory      5, 6, 16, 17
       cache       7
       connector   8
       slot        9

       Keywords are matched case-insensitively. The  following  command  lines
       are equivalent:

* dmidecode --type 0 --type 13

* dmidecode --type 0,13

* dmidecode --type 0 --type 13

* dmidecode --type 0,13

* dmidecode --type bios

* dmidecode --type BIOS

FILES
       /dev/mem

BUGS
       More often than not, information contained in the DMI tables is inaccuâ
       rate, incomplete or simply wrong.

AUTHORS
       Alan Cox, Jean Delvare

SEE ALSO
       biosdecode(8), mem(4), ownership(8), vpddecode(8)

dmidecode                         August 2005                     DMIDECODE(8)


==== Example output ====

Here's a snippet of output on an ESX host when displaying memory info:

 Handle 0x0028
        DMI type 17, 27 bytes.
        Memory Device
                Array Handle: 0x0025
                Error Information Handle: No Error
                Total Width: 76 bits
                Data Width: 72 bits
                Size: 1024 MB
                Form Factor: DIMM
                Set: 1
                Locator: DIMM 2A
                Bank Locator: Bank0 Bank1
                Type: DDR
                Type Detail: Synchronous
                Speed: 266 MHz (3.8 ns)
                Manufacturer: Not Specified
                Serial Number: Not Specified
                Asset Tag: Not Specified
                Part Number: Not Specified</text>
    <sha1>b6c8feb67b53cad28ec63684508bc041f01ecaa6</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Remote WMI defrag script</title>
  <ns>0</ns>
  <id>460</id>
  <revision>
    <id>915</id>
    <timestamp>2009-05-19T15:40:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '==== First version of my PowerPack uploaded ==== I really wanted to see how complicated it would be to write a very basic PowerPack for PowerGUI.  I had recently updated my WMI d...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="575" xml:space="preserve">==== First version of my PowerPack uploaded ====
I really wanted to see how complicated it would be to write a very basic PowerPack for PowerGUI.

I had recently updated my WMI defrag script to report to HTML, so I thought this would be an excellent candidate for a PowerPack. I must admit that, at first it is not very straight forward, but the more time you spend on it the easier it becomes.

[http://powershellneedfulthings.blogspot.com/2009/05/first-version-of-my-powerpack-uploaded.html Powershell Needful Things: Powershell Remote WMI defrag]

[[Category: Powershell]]</text>
    <sha1>955d1a9bdfc201efb0e052d37913f5b9a82b9237</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>PowerCLI: Update VMwaretools without a reboot</title>
  <ns>0</ns>
  <id>461</id>
  <revision>
    <id>917</id>
    <timestamp>2009-05-19T15:47:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'There appears to be a bug in the VMwareToolsUpgrader.exe that will cause the system to reboot no matter what. This behavior is especially bothersome because the VI API simply cal...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="589" xml:space="preserve">There appears to be a bug in the VMwareToolsUpgrader.exe that will cause the system to reboot no matter what. This behavior is especially bothersome because the VI API simply calls that executable to perform any non-interactive upgrade.

This morning I was updating a smaller farm to update 4. 15 minuets into the tools upgrade process I had enough… Enter PowerShell, I whipped up a quick script that will update All Windows VM’s to the latest version of VMware Tools.

[http://get-admin.com/blog/?p=714 Get-Admin: PowerCLI Update VMware Tools without a reboot]

[[Category: PowerCLI]]</text>
    <sha1>d5a249d8fbef3362baf1b43c4c2d785460690e51</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Virtu-Al: Lesson 4 Portgroups</title>
  <ns>0</ns>
  <id>462</id>
  <revision>
    <id>920</id>
    <timestamp>2009-05-23T09:41:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'So, we now have our host added to virtual center, we have it syncing the time with our central time server, we have the firewall adjusted to meet our needs and we have some virtu...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="452" xml:space="preserve">So, we now have our host added to virtual center, we have it syncing the time with our central time server, we have the firewall adjusted to meet our needs and we have some virtual switches created, our vmotion vswitch and portgroup created and associated with some nics.  Now what ?

PortGroups !

[http://www.virtu-al.net/2009/05/20/customisation-lesson-4-portgroups/ Virtu-Al: Lesson 4 Portgroups]


[[Category: Powershell]] [[Category: VI-Toolkit]]</text>
    <sha1>76898004267ec47707129c254bb148ae17f71b1c</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>PowerCLI: Oneliners</title>
  <ns>0</ns>
  <id>463</id>
  <revision>
    <id>922</id>
    <timestamp>2009-05-26T12:12:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'This page can be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell onelines for a while.  ...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1660" xml:space="preserve">This page can be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell onelines for a while.

* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]


[[Category: PowerCLI]]</text>
    <sha1>574e1efd569b0d3c7ddd88691e22ec46cf24da11</sha1>
  </revision>
  <revision>
    <id>923</id>
    <parentid>922</parentid>
    <timestamp>2009-05-26T12:26:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1915" xml:space="preserve">This page can be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell onelines for a while.

* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Statistics: Hosts whose CPU reached red Load level]


[[Category: PowerCLI]]</text>
    <sha1>3a9bb7cd6c53c08c473673ff68ccf78dddb193f1</sha1>
  </revision>
  <revision>
    <id>953</id>
    <parentid>923</parentid>
    <timestamp>2009-06-25T16:33:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added one liners from Alan Renouf</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2173" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added.


* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Statistics: Hosts whose CPU reached red Load level]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VMs per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VMs per Host]

[[Category: PowerCLI]]</text>
    <sha1>ef92cb6cb18cfacf7549b1db9e4fa2b8d3de345f</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>924</id>
    <parentid>886</parentid>
    <timestamp>2009-05-26T17:00:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="233" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]</text>
    <sha1>3d308b60b0aa9e9bc5e4b19ba33dfe66721df05e</sha1>
  </revision>
  <revision>
    <id>929</id>
    <parentid>924</parentid>
    <timestamp>2009-05-26T17:34:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="277" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]</text>
    <sha1>643c1cae8c21fad6cee6a0e53439442d5f3c0483</sha1>
  </revision>
  <revision>
    <id>933</id>
    <parentid>929</parentid>
    <timestamp>2009-05-26T20:41:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="310" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[Veeam VMware visio stencils]]</text>
    <sha1>66877c0d19a103c138eeab6ee14ae8eaca1f24db</sha1>
  </revision>
  <revision>
    <id>935</id>
    <parentid>933</parentid>
    <timestamp>2009-05-26T20:46:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="337" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]</text>
    <sha1>5b1c6fb9d647a934e8860736384e9825bd3746f6</sha1>
  </revision>
  <revision>
    <id>937</id>
    <parentid>935</parentid>
    <timestamp>2009-05-26T20:52:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="374" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]</text>
    <sha1>a91513efb037eb20a36120253bb3d00a72d3c271</sha1>
  </revision>
  <revision>
    <id>942</id>
    <parentid>937</parentid>
    <timestamp>2009-05-28T18:06:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="393" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]</text>
    <sha1>7466c317d2aa50d3b568ad71d71f6997c2997074</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>VMware View Open Client</title>
  <ns>0</ns>
  <id>464</id>
  <revision>
    <id>925</id>
    <timestamp>2009-05-26T17:01:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'VMware View Open Client lets you connect from a Linux desktop to remote Windows desktops managed by [http://www.vmware.com/products/view/ VMware View]  VMware View Open Client is...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="804" xml:space="preserve">VMware View Open Client lets you connect from a Linux desktop to remote Windows desktops managed by [http://www.vmware.com/products/view/ VMware View]

VMware View Open Client is available under the GNU Lesser General Public License version 2.1 (LGPL v 2.1) and is accessible from  http://code.google.com/p/vmware-view-open-client/

==== Articles ====
Features included in this release support secure tunneling using SSL, two factor authentication with RSA SecurID

* [http://www.thehostingnews.com/news-dedicated-server-virtualization-firm-vmware-gains-open-source-desktop-client-5119.html News: Dedicated Server Virtualization Firm, VMware, Gains Open Source Desktop Client]

* [http://www.thatsmyview.net/2009/05/25/how-to-use-view-without-vcenter-and-esxi/ How to use View without vCenter and ESX(i)]</text>
    <sha1>dba58b4577bfe3fa1569712984b75ace5379c3c6</sha1>
  </revision>
  <revision>
    <id>926</id>
    <parentid>925</parentid>
    <timestamp>2009-05-26T17:02:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="830" xml:space="preserve">VMware View Open Client lets you connect from a Linux desktop to remote Windows desktops managed by [http://www.vmware.com/products/view/ VMware View]

VMware View Open Client is available under the GNU Lesser General Public License version 2.1 (LGPL v 2.1) and is accessible from  http://code.google.com/p/vmware-view-open-client/

==== Articles ====
Features included in this release support secure tunneling using SSL, two factor authentication with RSA SecurID

* [http://www.thehostingnews.com/news-dedicated-server-virtualization-firm-vmware-gains-open-source-desktop-client-5119.html News: Dedicated Server Virtualization Firm, VMware, Gains Open Source Desktop Client]

* [http://www.thatsmyview.net/2009/05/25/how-to-use-view-without-vcenter-and-esxi/ How to use View without vCenter and ESX(i)]

[[Category: VMware OSS]]</text>
    <sha1>27e4975670177f5ccf83da7efd2abc905acf1653</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>927</id>
    <parentid>860</parentid>
    <timestamp>2009-05-26T17:12:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1650" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://www.vmware.com/communities/content/developer/samplecode/ VMware sample code]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>fe3c135390087b9b27dfcf4ce686b385c589eb5c</sha1>
  </revision>
  <revision>
    <id>928</id>
    <parentid>927</parentid>
    <timestamp>2009-05-26T17:14:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Codecentral is just the new link for VMware Community Sample Code so removed the old one</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1562" xml:space="preserve">==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>7eb93aab722ce7733a182c0c7cbbcdbb69c08fb3</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Parasite, debug your GTK+ applications</title>
  <ns>0</ns>
  <id>465</id>
  <revision>
    <id>930</id>
    <timestamp>2009-05-26T17:37:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Not really that much VMware related may be, but written by some VMware guys and we can all use some GUI front ends sometimes so... check out Parasite.  http://chipx86.github.com/...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="215" xml:space="preserve">Not really that much VMware related may be, but written by some VMware guys and we can all use some GUI front ends sometimes so... check out Parasite.

http://chipx86.github.com/gtkparasite

[[Category: VMware OSS]]</text>
    <sha1>21ef8a8fe06a0c70dd588e02bbea5c13903c7326</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>VMware Icons</title>
  <ns>0</ns>
  <id>423</id>
  <revision>
    <id>931</id>
    <parentid>827</parentid>
    <timestamp>2009-05-26T20:38:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="364" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints disappeared while I posted this... hmm... they might come back :)

[[Category:VMware OSS]] [[Category: VMware Artwork]]</text>
    <sha1>a7f692456e758f0fe6724d953f0168071072e12b</sha1>
  </revision>
  <revision>
    <id>939</id>
    <parentid>931</parentid>
    <timestamp>2009-05-26T20:56:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="364" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints seem to have moved to:
http://viops.vmware.com/home/docs/DOC-1338

[[Category:VMware OSS]] [[Category: VMware Artwork]]</text>
    <sha1>1cad43be567c3c0d7d0e33d274065efddbd96934</sha1>
  </revision>
  <revision>
    <id>941</id>
    <parentid>939</parentid>
    <timestamp>2009-05-26T20:58:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Removed OSS category as artwork seems to be more appropriate</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="340" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints seem to have moved to:
http://viops.vmware.com/home/docs/DOC-1338

[[Category: VMware Artwork]]</text>
    <sha1>7e583fd8792ceda70d9ab7e79d905ebbdf0aeeb7</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Category:VMware Artwork</title>
  <ns>14</ns>
  <id>466</id>
  <revision>
    <id>932</id>
    <timestamp>2009-05-26T20:39:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Artwork such as Icons, Visio Stencils, powerpoint sheets that can be used in presentations and applications. Please respect the licenses that come with the artwork.'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="164" xml:space="preserve">Artwork such as Icons, Visio Stencils, powerpoint sheets that can be used in presentations and applications.
Please respect the licenses that come with the artwork.</text>
    <sha1>bc995d9e401e3d07cc5a8b78342e1749a5d748a9</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Veeam VMware visio stencils</title>
  <ns>0</ns>
  <id>467</id>
  <revision>
    <id>934</id>
    <timestamp>2009-05-26T20:43:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Veeam Stencils is a free collection of VMware Visio stencils that can be used by ESX administrators, system integrators and datacenter managers to create their own diagrams in Mi...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="343" xml:space="preserve">Veeam Stencils is a free collection of VMware Visio stencils that can be used by ESX administrators, system integrators and datacenter managers to create their own diagrams in Microsoft Visio 2003 or higher.

These stencils are used by their Veeam Reporter product.


http://www.veeam.com/vmware-esx-stencils.html

[[Category: VMware Artwork]]</text>
    <sha1>2b89916a0ee101b4f0459a60e8a0c05595f50d44</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>VMguru Visio stencils</title>
  <ns>0</ns>
  <id>468</id>
  <revision>
    <id>936</id>
    <timestamp>2009-05-26T20:49:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Visio 2003/2007 Stencils from VMguru Scott Herold can be found here:  http://www.vmguru.com/index.php/articles-mainmenu-62/general-mainmenu-63/33-visio-stencils  [[Category: VMwa...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="190" xml:space="preserve">Visio 2003/2007 Stencils from VMguru Scott Herold can be found here:

http://www.vmguru.com/index.php/articles-mainmenu-62/general-mainmenu-63/33-visio-stencils

[[Category: VMware Artwork]]</text>
    <sha1>db07bf4b5012f729cf5aff44205e7e111a459b36</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>VIOPS VMware Icons and diagrams</title>
  <ns>0</ns>
  <id>469</id>
  <revision>
    <id>938</id>
    <timestamp>2009-05-26T20:54:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Visio stencils made from the artwork as released by the official VMware branding team. Can be used for documentation.  http://viops.vmware.com/home/docs/DOC-1346  [[Category: VMw...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="191" xml:space="preserve">Visio stencils made from the artwork as released by the official VMware branding team.
Can be used for documentation.

http://viops.vmware.com/home/docs/DOC-1346

[[Category: VMware Artwork]]</text>
    <sha1>564f2edf9218848401990b4ba5ef71be2b2a3305</sha1>
  </revision>
  <revision>
    <id>943</id>
    <parentid>938</parentid>
    <timestamp>2009-05-28T18:07:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="273" xml:space="preserve">Visio stencils made from the artwork as released by the official VMware branding team.
Can be used for documentation, now also includes vSphere artwork.

http://viops.vmware.com/home/docs/DOC-1346
and
http://viops.vmware.com/home/docs/DOC-1338

[[Category: VMware Artwork]]</text>
    <sha1>bea7ae69684c687fac8568cff35d3cd73a6a2926</sha1>
  </revision>
  <revision>
    <id>949</id>
    <parentid>943</parentid>
    <timestamp>2009-06-05T07:47:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Maishsk updated the hyperlink and added icons for vSphere to the vision stencils</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="311" xml:space="preserve">Visio stencils made from the artwork as released by the official VMware branding team.
Can be used for documentation, now also includes vSphere artwork.


[http://viops.vmware.com/home/docs/DOC-1514  VIOPS: Visio Stencils for vSphere]
and
http://viops.vmware.com/home/docs/DOC-1338

[[Category: VMware Artwork]]</text>
    <sha1>0444e3d1c250e38bfe1d2b320f02c35015156605</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Hostsvc/runtimeinfo</title>
  <ns>0</ns>
  <id>92</id>
  <revision>
    <id>944</id>
    <parentid>523</parentid>
    <timestamp>2009-05-29T07:53:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4152" xml:space="preserve">==== Vimsh hostsvc/runtimeinfo====
Usage: runtimeinfo

Retrieves the host runtime information.

====example output====
Example output when accessing an ESX3.5i host:
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/runtimeinfo
 (vim.host.RuntimeInfo) {
   dynamicType = &lt;unset&gt;,
   connectionState = "connected",
   powerState = "poweredOn",
   inMaintenanceMode = false,
   bootTime = "2008-11-24T23:10:41.665567Z",
   healthSystemRuntime = (vim.host.HealthStatusSystem.Runtime) {
      dynamicType = &lt;unset&gt;,
      systemHealthInfo = (vim.host.SystemHealthInfo) {
         dynamicType = &lt;unset&gt;,
         numericSensorInfo = (vim.host.NumericSensorInfo) [
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "VMware Rollup Health State",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "system",
            },
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "Phoenix Technologies LTD System BIOS 6.00 2008-07-29 00:00:00.000",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "Software Components",
            },
            (vim.host.NumericSensorInfo) {
               dynamicType = &lt;unset&gt;,
               name = "VMware Inc. Hypervisor VMware ESX Server 3i 3.5.0 build-123629 2008-10-15 21:03:57.000",
               healthState = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Green",
                  key = "Green",
               },
               currentReading = 0,
               unitModifier = 0,
               baseUnits = "",
               rateUnits = &lt;unset&gt;,
               sensorType = "Software Components",
            }
         ],
      },
      hardwareStatusInfo = (vim.host.HardwareStatusInfo) {
         dynamicType = &lt;unset&gt;,
         memoryStatusInfo = (vim.host.HardwareStatusInfo.HardwareElementInfo) [
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "Memory",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            }
         ],
         cpuStatusInfo = (vim.host.HardwareStatusInfo.HardwareElementInfo) [
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "CPU socket #0",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            },
            (vim.host.HardwareStatusInfo.HardwareElementInfo) {
               dynamicType = &lt;unset&gt;,
               name = "CPU socket #1",
               status = (vim.ElementDescription) {
                  dynamicType = &lt;unset&gt;,
                  label = "Green",
                  summary = "Physical element is functioning as expected",
                  key = "Green",
               },
            }
         ],
      },
   },
 }

==== example usage ====

#Checking Maintenance Mode
 vimsh -n -e /hostsvc/runtimeinfo | grep inMaintenanceMode | awk ‘{print $3}’
(see http://communities.vmware.com/thread/212398 )

[[Category: Vimsh]]</text>
    <sha1>93bdd471b9c29a41128252dbb8b9cde0ed5df4b4</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Hostsvc/memoryinfo</title>
  <ns>0</ns>
  <id>85</id>
  <revision>
    <id>945</id>
    <parentid>756</parentid>
    <timestamp>2009-05-29T19:28:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1239" xml:space="preserve">==== Vimsh hostsvc/memoryinfo ====
Usage: memoryinfo [memoryCfg]

Get the memory information.  If memoryCfg is specified, sets configured memory.

==== Example output ====

 [root@himalaya scripts]# vmware-vim-cmd hostsvc/memoryinfo
 (vim.host.MemoryManagerSystem.ServiceConsoleReservationInfo) {
   dynamicType = &lt;unset&gt;,
   serviceConsoleReservedCfg = 838860800,
   serviceConsoleReserved = 838860800,
   unreserved = 12045254656,
 }

==== Set or Get console memory ====
The service console memory should be increased if you are running apps other than the default install. This includes management agents, backups, etc. 
The changes require a reboot to take effect. You can incorporate this in your kickstart script. 
Don't forget to also set your swap partition to be 2x the Service Console memory, where the maximum used is 1600MB as you cannot set the console memory to over 800MB

To see the current Setting:
The setting shown is in bytes (MB * 1024 * 1024)
 vimsh -n -e "/hostsvc/memoryinfo"
 serviceConsoleReserved - Current setting
 serviceConsoleReservedCfg - Setting after next reboot

Set to 800MB:
 vimsh -n -e "/hostsvc/memoryinfo 838860800"

from: http://communities.vmware.com/blogs/froboy/tags/vimsh


[[Category: Vimsh]]</text>
    <sha1>5fa2b5d71de82b0ed0f932012166e4223171afee</sha1>
  </revision>
</page>
<page arvcontinue="20090519085720|904">
  <title>Vmware-vim-cmd</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>951</id>
    <parentid>502</parentid>
    <timestamp>2009-06-07T14:45:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added vimsh category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="826" xml:space="preserve">==== Vmware-vim-cmd ====

The command line version of the [[vimsh]] command.
This can be used in your scripts and replaces the alternative 
 vimsh -n -e &lt;command&gt;

so now you can use:
 vmware-vim-cmd &lt;command&gt;

 Usage: /usr/lib/vmware/hostd/vmware-vim-cmd [options]... command [cmd_arg1] [cmd_arg2] ...
 
 Options:
   -h           Display this help message and exit
   -v           Display version information and exit
   -H &lt;host&gt;    Host name to connect
   -O &lt;port&gt;    Port number to connect
   -U &lt;user&gt;    User name to use for login
   -P &lt;pass&gt;    Password to use for login
   -d &lt;level&gt;   Show verbose debug output. (info, verbose, trivia)

Use the help command to get information on the commands available.

   /usr/lib/vmware/hostd/vmware-vim-cmd help [command]


[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>6d25f814e60d57a1c27da339fd7507b4bc6bbcec</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Vimsh</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>954</id>
    <parentid>792</parentid>
    <timestamp>2009-06-30T13:06:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added William's article about vimsh</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3801" xml:space="preserve">==== The VI metashell ====

The Virtual Infrastructure metashell is an undocumented and unsupported shell accessible from within the console on an ESX server.
It can be invoked from the shell when logged in as root user as an interactive shell.
You can do almost anything from it what you can do from the Virtual Infrastructure client and is more powerful as the normal [[RCLI]] console commands.

Below is some output of the shell that you get to see and the output of the "?" command:

 [/]$ ?
 hostsvc/      vmsvc/        csinfo        help          puload
 internalsvc/  ?             csls          pinfo         puse
 proxysvc/     argtype       csuimport     pload         quit
 solo/         cls           echo          ploadpath     sleep
 vimsvc/       csimport      exit          pls           source


There's a separation between plugins and direct commands. The items from the list above that end in a "/" are plugins. (is this true or are they just idicating that there's a submenu?) You can use tab-completion in order to find the available parameters for any of the commands.

An advantage of vimsh over normal esx-cfg commands is that the changes are immediate, so you do not need to restart the vmware management services.

In recent versions of ESX (ESX3.5+), there's also a non interactive command line version of vimsh that can be used from within a script which is called [[vmware-vim-cmd]] and is much easier to read in your scripts as the alternative: vimsh -n -e "command"

'''ESX 3.0.x+'''
  /usr/bin/vimsh -n -e "command"

'''ESX 3.5+''' 
 /usr/bin/vimsh -n -e "command"
 /usr/bin/vmware-vim-cmd "command"

'''ESXi 3.5+'''
 /bin/vim-cmd "command"

/usr/bin/vimsh is a symbolic link to the file [[vmware-vimsh]] in the same folder.

==== List of commands ====

Following is a list of the available commands (the vimsh: prefix is only included as a namespace, so that it won't clash with other parts in the wiki)

Over time I will try to add the info found about this in here (help would be EXTREMELY appreciated) right now it just lists what is available in the online help and in many cases some example output of the commands.

 [[vimsh: hostsvc/]]
 [[vimsh: internalsvc/]]
 [[vimsh: proxysvc/]]
 [[vimsh: solo/]]
 [[vimsh: vimsvc/]]
 [[vimsh: vmsvc/]]        
 [[vimsh: ?]]
 [[vimsh: argtype]]
 [[vimsh: cls]]
 [[vimsh: csimport]]
 [[vimsh: csinfo]]
 [[vimsh: csls]]
 [[vimsh: csuimport]]
 [[vimsh: echo]]
 [[vimsh: exit]]
 [[vimsh: help]]
 [[vimsh: puload]]
 [[vimsh: pinfo]]
 [[vimsh: pload]]
 [[vimsh: ploadpath]]
 [[vimsh: pls]]
 [[vimsh: puse]]          
 [[vimsh: quit]]          
 [[vimsh: sleep]]         
 [[vimsh: source]]

==== Background info ====

This command has its origin as a support shell only. 
It is rumored about that vimsh will be supported in one of the upcoming versions of ESX 

==== External links ====

As there's no official documentation, here's the link to the current authorative documentation:
* [http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

Example usage (article in dutch)
* [http://www.l4l.be/docs/virt/vimsh.php Voorbeelden gebruik VIMSH]

Other articles with examples:
* [http://www.rtfm-ed.co.uk/?p=372 Updated: Enabling VMotion from the CLI/Kickstart Script]

* [http://effectief.blogspot.com/2007/09/vimsh-handy-vmware-esx-command-line.html Koen Warsons blog: handy Vmware ESX Command line tool]

* [http://vmwaretips.com/wp/2008/09/12/netapp-snapshots-in-esx/#more-20 NetApp Snapshots in ESX]

* [http://malaysiavm.com/blog/how-to-update-vmware-esx-patch-using-cli/ How-to update vmware ESX using CLI]

* [http://engineering.ucsb.edu/~duonglt/vmware/#vmware_vimsh William Lam's "VMware's undocumented vimsh"]

[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>0aceb237e69c9e5519d49a7931d6ac44c99f4490</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Category:VIX</title>
  <ns>14</ns>
  <id>275</id>
  <revision>
    <id>955</id>
    <parentid>499</parentid>
    <timestamp>2009-07-07T09:34:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="99" xml:space="preserve">Virtual Machine Automation API category.

[[vmrun]] is one of the most popular parts of the VIX API</text>
    <sha1>a07a1ee35f503ac85f22fbc4586e8d98701f7b57</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Vmrun</title>
  <ns>0</ns>
  <id>470</id>
  <revision>
    <id>956</id>
    <timestamp>2009-07-07T09:41:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>thanks http://communities.vmware.com/people/mattrich for mentioning the GUI limitations</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="997" xml:space="preserve">vmrun is a command line utility that can be used to run certain automation tasks easily.
It is easy to make it part of a script and do things like start a particular VM, create a snapshot, run a program in the guest, etcetera.


==== Limitations while running the VM in the GUI ====
There are some things you can't do things while the VM is open in the UI, but other things should work.

Things you can do:
* Power off the VM
* Suspend the VM
* Create a snapshot 
* Revert to a snapshot (need to verify)
* Pause and unpause the VM
* Power on the VM using the 'gui' option
* Perform guest operations (runProgramInGuest, listDirectoryInGuest, etc.)
* Start and stop recording
* Mount the Tools installer
* Run any vProbes commands
* Change the shared folder settings (add, remove, enable) of a running VM.

Things you cannot do:
* Upgrade the VM's virtual hardware
* Power on the VM using the 'nogui' option 
* Change the shared folder settings (add, remove, enable) of a powered off or suspended VM</text>
    <sha1>06ee209a39c733f0dd5bd4ca4973ff81a38d4035</sha1>
  </revision>
  <revision>
    <id>957</id>
    <parentid>956</parentid>
    <timestamp>2009-07-07T09:43:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1016" xml:space="preserve">vmrun is a command line utility that can be used to run certain automation tasks easily.
It is easy to make it part of a script and do things like start a particular VM, create a snapshot, run a program in the guest, etcetera.


==== Limitations while running the VM in the GUI ====
There are some things you can't do things while the VM is open in the UI, but other things should work.

Things you can do:
* Power off the VM
* Suspend the VM
* Create a snapshot 
* Revert to a snapshot (need to verify)
* Pause and unpause the VM
* Power on the VM using the 'gui' option
* Perform guest operations (runProgramInGuest, listDirectoryInGuest, etc.)
* Start and stop recording
* Mount the Tools installer
* Run any vProbes commands
* Change the shared folder settings (add, remove, enable) of a running VM.

Things you cannot do:
* Upgrade the VM's virtual hardware
* Power on the VM using the 'nogui' option 
* Change the shared folder settings (add, remove, enable) of a powered off or suspended VM

[[Category: VIX]]</text>
    <sha1>ac18c07732f33eed9f28355af149fbbe015343eb</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Vmplayer</title>
  <ns>0</ns>
  <id>471</id>
  <revision>
    <id>958</id>
    <timestamp>2009-07-07T09:54:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '==== VMware Player ====  Vmplayer is the executable that runs the VMware Player program on the hosted Windows and Linux platforms.   === Command line options ==== You can start t...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="821" xml:space="preserve">==== VMware Player ====

Vmplayer is the executable that runs the VMware Player program on the hosted Windows and Linux platforms.


=== Command line options ====
You can start the player with command line options so that it starts with a certain feature that you want to use. 

Syntax:
 vmplayer [options] /path/to/vmx

Options:
 --unity              : Start with unity enabled
 -h                     : hostname or IP on another machine (can be running ESX or VMware Server!)
 -u &lt;name&gt;       : username to login at the host
 -p  &lt;pass&gt;       : password to login at the host

Examples:
Connect to a remote ESX/ESXi host using player on IP address 10.10.10.10 and select a windows 2003 VM on the datastore1 storage.
 vmplayer  -h 10.10.10.10 -u "root" -p "password" "[datastore1] W2k3en/W2k3en.vmx" 


[[Category: ToDo]]</text>
    <sha1>23c2608df69e14a0fb7c274062f9287cd05f8fe7</sha1>
  </revision>
  <revision>
    <id>959</id>
    <parentid>958</parentid>
    <timestamp>2009-07-07T09:56:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>align text a bit for readability</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="829" xml:space="preserve">==== VMware Player ====

Vmplayer is the executable that runs the VMware Player program on the hosted Windows and Linux platforms.


=== Command line options ====
You can start the player with command line options so that it starts with a certain feature that you want to use. 

Syntax:
 vmplayer [options] /path/to/vmx

Options:
 --unity              : Start with unity enabled
 -h                   : hostname or IP on another machine (can be running ESX or VMware Server!)
 -u &lt;name&gt;            : username to login at the host
 -p  &lt;pass&gt;           : password to login at the host

Examples:

Connect to a remote ESX/ESXi host using player on IP address 10.10.10.10 and select a windows 2003 VM on the datastore1 storage.
 vmplayer  -h 10.10.10.10 -u "root" -p "password" "[datastore1] W2k3en/W2k3en.vmx" 


[[Category: ToDo]]</text>
    <sha1>9e8bb14cc23118c1b03b2312adeb298bd0a5ad0c</sha1>
  </revision>
  <revision>
    <id>960</id>
    <parentid>959</parentid>
    <timestamp>2009-07-07T09:56:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="847" xml:space="preserve">==== VMware Player ====

Vmplayer is the executable that runs the VMware Player program on the hosted Windows and Linux platforms.


=== Command line options ====
You can start the player with command line options so that it starts with a certain feature that you want to use. 

Syntax:
 vmplayer [options] /path/to/vmx

Options:
 --unity              : Start with unity enabled
 -h                   : hostname or IP on another machine (can be running ESX or VMware Server!)
 -u &lt;name&gt;            : username to login at the host
 -p  &lt;pass&gt;           : password to login at the host

Examples:

Connect to a remote ESX/ESXi host using player on IP address 10.10.10.10 and select a windows 2003 VM on the datastore1 storage.
 vmplayer  -h 10.10.10.10 -u "root" -p "password" "[datastore1] W2k3en/W2k3en.vmx" 


[[Category: CLI]] [[Category: ToDo]]</text>
    <sha1>170a80d3fd22f59362b465843ae084d7b62578ab</sha1>
  </revision>
  <revision>
    <id>963</id>
    <parentid>960</parentid>
    <timestamp>2009-07-07T15:57:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added supported list of options</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1529" xml:space="preserve">==== VMware Player ====

Vmplayer is the executable that runs the VMware Player program on the hosted Windows and Linux platforms.


=== Command line options ====
You can start the player with command line options so that it starts with a certain feature that you want to use. 

Syntax:
 vmplayer [options] /path/to/vmx

Options:
 -?, --help              : display supported options
 -v, --version           : display the version of vmware player used
 -L, --list-stock-ids    :  display the list of registered VMs
 -X, --fullscreen        : Start player with the supplied VM in full screen  mode
 -U, --unity             : Start with unity enabled
 -k, --no-kiosk-warning  : Start an ACE VM without warning
 -K, --no-kiosk-mode     : Start a kiosk mode ACE VM outside of kiosk mode
 -h                      : (unsupported) hostname or IP on an remote machine (can be running ESX or VMware Server!) This works best on  the linux vmware player, when using  windows you MUST also supply the VM  to run.  On linux if you do not supply a VM,   it will present you a dialog to select the virtual machine from.
 -u &lt;name&gt;               : (unsupported) username to login at the remote host
 -p  &lt;pass&gt;              : (unsupported) password to login with at the remote host

Examples:

Connect to a remote ESX/ESXi host using player on IP address 10.10.10.10 and select a windows 2003 VM on the datastore1 storage.
 vmplayer  -h 10.10.10.10 -u "root" -p "password" "[datastore1] W2k3en/W2k3en.vmx" 


[[Category: CLI]] [[Category: ToDo]]</text>
    <sha1>435a96f2e9a6dd3fe9f1d17cb17cee4220404012</sha1>
  </revision>
  <revision>
    <id>964</id>
    <parentid>963</parentid>
    <timestamp>2009-07-07T16:00:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1668" xml:space="preserve">==== VMware Player ====

Vmplayer is the executable that runs the VMware Player program on the hosted Windows and Linux platforms.


=== Command line options ===
You can start the player with command line options so that it starts with a certain feature that you want to use. 

Syntax:
 vmplayer [options] /path/to/vmx

Options:
 -?, --help              : display supported options
 -v, --version           : display the version of vmware player used
 -L, --list-stock-ids    : display the list of registered VMs
 -X, --fullscreen        : Start player with the supplied VM in full screen  mode
 -U, --unity             : Start with unity enabled
 -k, --no-kiosk-warning  : Start an ACE VM without warning
 -K, --no-kiosk-mode     : Start a kiosk mode ACE VM outside of kiosk mode
 -h &lt;host&gt;               : (unsupported) hostname or IP on an remote machine (can be running ESX or VMware Server!) 
 -u &lt;name&gt;               : (unsupported) username to login at the remote host
 -p &lt;pass&gt;               : (unsupported) password to login with at the remote host

The unsupported -h option works best on  the linux vmware player, when using  windows you MUST also supply the VM  to run.  On linux if you do not supply a VM,   it will present you with a dialog to select the virtual machine from. When trying to access a VM hosted at a VMware Server host, you have to add the :8333 port to the ip or hostname.

Examples:

Connect to a remote ESX/ESXi host using player on IP address 10.10.10.10 and select a windows 2003 VM on the datastore1 storage.
 vmplayer  -h 10.10.10.10 -u "root" -p "password" "[datastore1] W2k3en/W2k3en.vmx" 


[[Category: CLI]] [[Category: ToDo]]</text>
    <sha1>0c4b6cf2ddcf7c570a3c869a4e562aff1686a6fe</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Category:ToDo</title>
  <ns>14</ns>
  <id>472</id>
  <revision>
    <id>961</id>
    <timestamp>2009-07-07T10:51:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'List pages which need more work before they are acceptable as a full article.'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">List pages which need more work before they are acceptable as a full article.</text>
    <sha1>514435a21b8d00bff7df68274575121f9a66ad82</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>VMware Infrastructure Java API</title>
  <ns>0</ns>
  <id>15</id>
  <revision>
    <id>962</id>
    <parentid>94</parentid>
    <timestamp>2009-07-07T10:55:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="542" xml:space="preserve">==== VMware Infrastructure Java API ====

The VMware Virtual Infrastructure Java API provides a set of libraries with full support of managed object model and utilities to manage and control VMware virtual machines and servers using the VMware Virtual Infrastructure Web service interface. 

vSphere Java is now GA release 2.0

http://sourceforge.net/projects/vijava/

http://vijava.sourceforge.net/ 

[http://communities.vmware.com/thread/183407 Preview: VI Java Plug-in for Eclipse (open source project)]

[[Category:SDK]] [[Category:Java]]</text>
    <sha1>9c6eeebc807fafaf0d526b82c7b29f45e74eefcc</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>965</id>
    <parentid>928</parentid>
    <timestamp>2009-07-08T08:18:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>tidied it up a bit and added link to new VMware developer blog</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1709" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]


==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>35356e5d0d2de7e441947cfbc6db3193f2b3d9ec</sha1>
  </revision>
  <revision>
    <id>967</id>
    <parentid>965</parentid>
    <timestamp>2009-07-08T13:07:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added ICT Freak web site, moved ntpro.nl down to powershell must read blogs</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1747" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>2105a27532e9958c3a012201a085439e386dbffe</sha1>
  </revision>
  <revision>
    <id>977</id>
    <parentid>967</parentid>
    <timestamp>2009-07-09T17:51:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Arnim van Lieshout's blog to the list</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1799" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>288d7a9cfa84db43464e8429187614661bced856</sha1>
  </revision>
  <revision>
    <id>985</id>
    <parentid>977</parentid>
    <timestamp>2009-07-13T21:07:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to vmwarescripting.com forum</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1862" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>64d4723a3e99a4b871a0e129c916deff807411ac</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>966</id>
    <parentid>950</parentid>
    <timestamp>2009-07-08T08:47:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2803" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>f9fd01260eaa10af59542059b65f2e6fd4d2ab57</sha1>
  </revision>
  <revision>
    <id>971</id>
    <parentid>966</parentid>
    <timestamp>2009-07-09T00:39:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2853" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>4bfd1efeccf7eff2a4d49651af1c1a4d78f3116f</sha1>
  </revision>
  <revision>
    <id>973</id>
    <parentid>971</parentid>
    <timestamp>2009-07-09T17:31:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2901" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>4235f97328f1998ddb84dcc7aa9c02c703b385ad</sha1>
  </revision>
  <revision>
    <id>978</id>
    <parentid>973</parentid>
    <timestamp>2009-07-09T17:53:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2959" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>fad534afe50164e47cd06ba17eae0c02ca15b829</sha1>
  </revision>
  <revision>
    <id>980</id>
    <parentid>978</parentid>
    <timestamp>2009-07-09T20:01:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added LucD's script on VMTN about getting task and eventlogs (Thanks Hall Rottenberg for pointing it out)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3037" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>bc7d3c1551d47fdf400f82b73090899598438ad3</sha1>
  </revision>
  <revision>
    <id>982</id>
    <parentid>980</parentid>
    <timestamp>2009-07-13T18:21:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to Alan Renoufs snap reminder, send an email to those offenders ;)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3068" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>daa4c75b7099c42a5e99f0d375ca82de0a13556b</sha1>
  </revision>
  <revision>
    <id>984</id>
    <parentid>982</parentid>
    <timestamp>2009-07-13T19:05:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Alan's description of how-to run a PowerCLI script as a scheduled task under windows</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3188" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]


==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>15cb9ab9b0b171e349bf8a941db8af9d7795ce62</sha1>
  </revision>
  <revision>
    <id>986</id>
    <parentid>984</parentid>
    <timestamp>2009-07-15T15:37:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added links to GUI confirmation from Hugo Peeters, Autopowershell tip from Hal Rottenberg, @powerguiOrg twitter feed</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3513" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]


==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>8ad6b51ad31b93ef2dea91ed55064b68398dc32d</sha1>
  </revision>
  <revision>
    <id>990</id>
    <parentid>986</parentid>
    <timestamp>2009-07-16T09:59:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Adding  Alan Renouf's fantastic daily report script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3543" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]


==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>effacfb4eff3fe4c0f5911fd43643a44d2a01bad</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerCLI: Oneliners</title>
  <ns>0</ns>
  <id>463</id>
  <revision>
    <id>968</id>
    <parentid>953</parentid>
    <timestamp>2009-07-08T13:16:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added links to 3 onliners from Alan Renouf</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2561" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added.


* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Statistics: Hosts whose CPU reached red Load level]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VMs per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VMs per Host]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

[[Category: PowerCLI]]</text>
    <sha1>6adeb1117634afd17e473cf4202caafa28e70465</sha1>
  </revision>
  <revision>
    <id>975</id>
    <parentid>968</parentid>
    <timestamp>2009-07-09T17:42:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added virtu-al's statistics one liner</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2711" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added.


* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Statistics: Hosts whose CPU reached red Load level]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VMs per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VMs per Host]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

[[Category: PowerCLI]]</text>
    <sha1>4cf69bce4bd652f1387180f44a75e0be5a4c2350</sha1>
  </revision>
  <revision>
    <id>987</id>
    <parentid>975</parentid>
    <timestamp>2009-07-15T15:50:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added several oneliners from Arne Fokkema</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3245" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added.


* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Statistics: Hosts whose CPU reached red Load level]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]
[[Category: PowerCLI]]</text>
    <sha1>aaecfcc0b3527de5268af80ddf864249c2f5f5b5</sha1>
  </revision>
  <revision>
    <id>988</id>
    <parentid>987</parentid>
    <timestamp>2009-07-15T15:54:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3375" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added.


* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Statistics: Hosts whose CPU reached red Load level]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]
[[Category: PowerCLI]]</text>
    <sha1>ce0b7b07816b6dc6b04ed394e6bf9e1ec9a857fd</sha1>
  </revision>
  <revision>
    <id>989</id>
    <parentid>988</parentid>
    <timestamp>2009-07-16T08:46:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Grouped the oneliners into categories</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3485" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added from other great powershell scripters.


==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]


==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

==== Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>c860a65151097889a240cb23b7507cce813b09fa</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>969</id>
    <parentid>904</parentid>
    <timestamp>2009-07-09T00:25:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2875" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

[[APC/APCUPSD ESX/ESXi Host shutdown script]]

==== Perl scripts ====
[[Recover vmx from log file]]

==== AppleScript ====

[http://communities.vmware.com/thread/122793 AppleScript to Run Virtual Machine and switch to Full Screen View or Unity View at Login]

==== Javascript ====
[[Ghetto vCenter 4.0 Unattended Installer]]</text>
    <sha1>39fde73c645e189c875f8a90a07367a064671090</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Ghetto vCenter 4.0 Unattended Installer</title>
  <ns>0</ns>
  <id>473</id>
  <revision>
    <id>970</id>
    <timestamp>2009-07-09T00:36:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'An unattended installer for vCenter 4.0 written in Javascript in the form of a hta script for 64 bits Windows server hosts. The installer will prompt you for the parameters and t...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="406" xml:space="preserve">An unattended installer for vCenter 4.0 written in Javascript in the form of a hta script for 64 bits Windows server hosts.
The installer will prompt you for the parameters and then run the install including setting up the 32 bits DSN for ODBC.
There's a video showing how it works.

read more:
http://vinternals.com/2009/07/ghetto-vcenter-4-0-unattended-installer/

[[Category: ESX]] [[Category: vCenter]]</text>
    <sha1>0549731949e7a1a2c21b1a97b780d866fdae4940</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerCLI: Add configuration details to VMX</title>
  <ns>0</ns>
  <id>474</id>
  <revision>
    <id>972</id>
    <timestamp>2009-07-09T00:44:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Arne Fokkema has created a PowerCLI script that makes it possible to add configuration details to your VM's VMX file read from a CSV file. This allows for automating your Virtual...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="384" xml:space="preserve">Arne Fokkema has created a PowerCLI script that makes it possible to add configuration details to your VM's VMX file read from a CSV file.
This allows for automating your Virtual Machines hardware configuration features and VM security profile.

read more:

http://ict-freak.nl/2009/07/08/powercli-add-multiple-values-to-a-vmx-file/

[[Category: VM Automation]] [[Category: PowerCLI]]</text>
    <sha1>42e289e473680b513499a42bdd9441a4db625f93</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerCLI: Get Virtual Machine disk usage</title>
  <ns>0</ns>
  <id>475</id>
  <revision>
    <id>974</id>
    <timestamp>2009-07-09T17:36:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'The following script calculates the used and free space of your Virtual Machines and datastores.  The end result is exported to a csv file for use in Excel.  read more:  http://w...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="277" xml:space="preserve">The following script calculates the used and free space of your Virtual Machines and datastores. 
The end result is exported to a csv file for use in Excel.

read more:

http://www.peetersonline.nl/index.php/vmware/get-vmware-disk-usage-with-powershell/

[[Category: PowerCLI]]</text>
    <sha1>76a50344b05a5dc46a80dfa0ffa68ed18fe747a1</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>BEGINNERS PAGE</title>
  <ns>0</ns>
  <id>433</id>
  <revision>
    <id>976</id>
    <parentid>888</parentid>
    <timestamp>2009-07-09T17:48:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to icomasoft powercli reference card (thanks to Alan for finding this http://www.virtu-al.net/2009/05/17/icomasoft-powercli-reference-card/ )</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="954" xml:space="preserve">Looking to Get-Started with the VI Toolkit ?

Check out the below links to find useful resources or add your own:

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell FAQ]
* [http://www.virtu-al.net/2009/02/23/vi-toolkit-quick-reference-guide/ VI Toolkit Quick Reference Guide]
* [http://www.icomasoft.com/products/vi-powerscripter/powercli-reference-card.html PowerCLI Quick Reference Card]
* [http://vinternals.com/powercli-mastery/ vinternals: PowerCLI mastery]
* [http://keithhill.spaces.live.com/blog Keith hill blog]
* [http://blogs.vmware.com/files/vi-toolkit-lab----vmworld-europe-2009.pdf VI Toolkit lab VMworld europe 2009]

Podcasts you should listen to:

* [http://get-scripting.blogspot.com/ Get-Scripting Podcast] by [[Alan Renouf]] and [[Jonathan Medd]]
* [http://powerscripting.wordpress.com/ PowerScripting Podcast] by [[Jonathan Walz]] and [[Hal Rottenberg]]

Add your own Tips here:

[[Category: Powershell]]</text>
    <sha1>8f3eff8f901daa570eca7aaa614cd03174cb2572</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerCLI: Export and import customization profiles</title>
  <ns>0</ns>
  <id>476</id>
  <revision>
    <id>979</id>
    <timestamp>2009-07-09T17:58:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Using customization profiles you can automate Virtual Machine deployments. These profiles are normally stored in the vCenter Server database. Arnim has written a few scripts so t...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="480" xml:space="preserve">Using customization profiles you can automate Virtual Machine deployments. These profiles are normally stored in the vCenter Server database. Arnim has written a few scripts so that you can export and import these profiles into xml files, hereby making the profiles much more portable and easier to backup (and restore).

read more:

http://www.van-lieshout.com/2009/07/export-and-import-customization-profiles-using-powershell/

[[Category: PowerCLI]] [[Category: VM Automation]]</text>
    <sha1>676179d894dcf31ac8f517fc827a3ad669dbda08</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector</title>
  <ns>0</ns>
  <id>477</id>
  <revision>
    <id>981</id>
    <timestamp>2009-07-09T20:06:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Great work Luc!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="326" xml:space="preserve">Luc Dekens has donated a script to VMTN where someone asks for a task and eventlog export file.
He shows how-to use Get-ViEvent for the eventlogs and TaskHistoryCollector for exporting tasks from the last 2 days.

read more:

[http://communities.vmware.com/message/1259677 VMTN: How to get log from VC]

[[Category: PowerCLI]]</text>
    <sha1>256a6b52b60fb3899a759f53c3617714675a1d6e</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerCLI: Snap reminder</title>
  <ns>0</ns>
  <id>478</id>
  <revision>
    <id>983</id>
    <timestamp>2009-07-13T18:28:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Snapshots are a great feature for virtual machines, but leaving them open for a long time is unwanted for a number of reasons.   Alan Renouf has written a script here that checks...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="529" xml:space="preserve">Snapshots are a great feature for virtual machines, but leaving them open for a long time is unwanted for a number of reasons. 

Alan Renouf has written a script here that checks your hosts for virtual machines which have open snapshots for more as 2 weeks. The scripts then finds out who created them and as extra bonus even automatically sends the offender an email based on the email address in their Active Directory subscription.

read more:

http://www.virtu-al.net/2009/06/22/powercli-snapreminder/

[[Category: PowerCLI]]</text>
    <sha1>024decea96205c54c9d13c78dc59b8babe26f9ac</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerCLI: Daily Report</title>
  <ns>0</ns>
  <id>479</id>
  <revision>
    <id>991</id>
    <timestamp>2009-07-16T10:08:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Alan has written a script that you can schedule to run each day and have it report to you by email the most vital information about your virtual infrastructure.  Items that are c...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="696" xml:space="preserve">Alan has written a script that you can schedule to run each day and have it report to you by email the most vital information about your virtual infrastructure.

Items that are currently part of the daily report are:
* Host statistics
* Open snapshots
* Data storage usage
* Virtual Machines create history
* Virtual Machines delete history
* Virtual Center events
* VMware Tools install details
* Any Windows events from the Virtual center server which are related to VMware
* Any VMs which have CD-Rom or Floppy Drive’s connected
* Any hosts in Maintenance Mode
* Any Hosts in a disconnected state

read more:

http://www.virtu-al.net/2009/07/14/powercli-daily-report/

[[Category: PowerCLI]]</text>
    <sha1>ffa2a866b979089e77fd5bf793bdc3c1d884a6f3</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Category:PowerCLI</title>
  <ns>14</ns>
  <id>454</id>
  <revision>
    <id>992</id>
    <parentid>897</parentid>
    <timestamp>2009-07-16T10:11:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added reference to the other VI-Toolkit scripts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="192" xml:space="preserve">Software written in PowerCLI. PowerCLI is the SDK software library for managing vSphere hosts.

There's more scripts on the [[Powershell]] page that have not been explicitly tagged as PowerCLI</text>
    <sha1>2ab48e2e8e533be638181e8f9c48cd01fb37b364</sha1>
  </revision>
  <revision>
    <id>993</id>
    <parentid>992</parentid>
    <timestamp>2009-07-16T10:12:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Oops case sensitive... typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="192" xml:space="preserve">Software written in PowerCLI. PowerCLI is the SDK software library for managing vSphere hosts.

There's more scripts on the [[PowerShell]] page that have not been explicitly tagged as PowerCLI</text>
    <sha1>abbbbe15e20c6d750206393bb12f3e871e58b742</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>994</id>
    <parentid>942</parentid>
    <timestamp>2009-07-16T16:48:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="440" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[VICL, A VMWare Interface Client for Linux]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]</text>
    <sha1>d296db84ba8ec15eab978faa5ce5616609d96bb9</sha1>
  </revision>
  <revision>
    <id>998</id>
    <parentid>994</parentid>
    <timestamp>2009-07-22T09:37:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="472" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[VICL, A VMWare Interface Client for Linux]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]

[[Xtravirt Visio action pack]]</text>
    <sha1>78a85a876ea45e7040c938dd257b427290b8ade6</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>VICL, A VMWare Interface Client for Linux</title>
  <ns>0</ns>
  <id>480</id>
  <revision>
    <id>995</id>
    <timestamp>2009-07-16T16:52:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>VICL a new management interface written in C</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="320" xml:space="preserve">A management interface written in C using the VIX API.

The idea is that this will provide Linux users a management interface to the popular VMWare Virtual Server 2 virtualization software as an alternative for the web interface.

read more:

http://code.google.com/p/vicl/

[[Category: VIX]] [[Category: VM Management]]</text>
    <sha1>87fbcd1d08573cad5d287aa05be8245fbb8db501</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Dmidecode</title>
  <ns>0</ns>
  <id>459</id>
  <revision>
    <id>996</id>
    <parentid>913</parentid>
    <timestamp>2009-07-16T16:54:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8816" xml:space="preserve">from the man command: 

Reformatting dmidecode(8), please wait...
DMIDECODE(8)                                                      DMIDECODE(8)

==== NAME ====
       dmidecode - DMI table decoder

==== SYNOPSIS ====
       dmidecode [OPTIONS]

==== DESCRIPTION ====
dmidecode  is a tool for dumping a computerâs DMI (some say SMBIOS) table contents in a human-readable format. This table contains a description  of  the  systemâs  hardware  components,  as well as other useful pieces of information such as serial numbers and BIOS revision.  Thanks to  this  table,  you  can  retrieve this information without having to probe for the actual hardware.  While this is a good point in terms  of report  speed  and  safeness, this also makes the presented information possibly unreliable.

The DMI table doesnât only describe what the system is  currently  made of,  it  also  can  report the possible evolutions (such as the fastest supported CPU or the maximal amount of memory supported).

SMBIOS stands for System Management BIOS, while DMI stands for  Desktop Management  Interface. Both standards are tightly related and developed by the DMTF (Desktop Management Task Force).

As you run it, dmidecode will try to locate the DMI table. If  it  succeeds, it will then parse this table and display a list of records like
this one:

       Handle 0x0002
           DMI type 2, 8 bytes.
           Base Board Information
               Manufacturer: Intel
               Product Name: C440GX+
               Version: 727281-001
               Serial Number: INCY92700942


Each record has:

* A handle. This is a unique identifier, which allows records to reference  each  other.  For  example, processor records usually reference cache memory records using their handles.

* A type. The SMBIOS specification defines different types of  elements a  computer  can  be  made  of. In this example, the type is 2, which means that the record contains "Base Board Information".

* A size. Each record has a 4-byte header (2 for the handle, 1 for  the type,  1  for  the  size),  the rest is used by the record data. This value doesn't take text strings into account (these are placed at the end of the record), so the actual length of the record may be (and is often) greater than the displayed value.

* Decoded values. The information presented of course  depends  on  the type of record. Here, we learn about the boardâs manufacturer, model, version and serial number.

OPTIONS
       -d, --dev-mem FILE
              Read memory from device FILE (default: /dev/mem)

       -q, --quiet
              Be less verbose. Unknown, inactive and OEM-specific entries  are
              not displayed. Meta-data and handle references are hidden. Mutuâ
              ally exclusive with --dump.

       -s, --string KEYWORD
              Only display the value of the DMI string identified by  KEYWORD.
              KEYWORD  must be a keyword from the following list: bios-vendor,
              bios-version,  bios-release-date,  system-manufacturer,  system-
              product-name,  system-version,  system-serial-number, baseboard-
              manufacturer, baseboard-product-name,  baseboard-version,  baseâ
              board-serial-number,  baseboard-asset-tag, chassis-manufacturer,
              chassis-version, chassis-serial-number, chassis-asset-tag,  proâ
              cessor-manufacturer,  processor-version.   Each  keyword  correâ
              sponds to a given DMI type and a given offset within this  entry
              type.   Not all strings may be meaningful or even defined on all
              systems. Some keywords may return more than one result  on  some
              systems  (e.g.   processor-version on a multi-processor system).
              If KEYWORD is not provided or not valid, a  list  of  all  valid
              keywords  is  printed  and  dmidecode exits with an error.  This
              option cannot be used  more  than  once,  and  implies  --quiet.
              Mutually exclusive with --type and --dump.

       -t, --type TYPE
              Only  display the entries of type TYPE. TYPE can be either a DMI
              type number, or a comma-separated list of  type  numbers,  or  a
              keyword  from the following list: bios, system, baseboard, chasâ
              sis, processor, memory, cache, connector, slot. Refer to the DMI
              TYPES  section  below  for details.  If this option is used more
              than once, the set of displayed entries will be the union of all
              the  given  types.  If TYPE is not provided or not valid, a list
              of all valid keywords is printed and  dmidecode  exits  with  an
              error.  Mutually exclusive with --string.

       -u, --dump
              Do  not  decode  the entries, dump their contents as hexadecimal
              instead.  Note that this is still a text output, no binary  data
              will  be thrown upon you. The strings attached to each entry are
              displayed as both hexadecimal and ASCII. This option  is  mainly
              useful  for  debugging.   Mutually  exclusive  with  --quiet and
              --string.

       -h, --help
              Display usage information and exit

       -V, --version
              Display the version and exit

DMI TYPES
       The SMBIOS specification defines the following DMI types:

       Type   Information
       ----------------------------------------
          0   BIOS
          1   System
          2   Base Board
          3   Chassis
          4   Processor
          5   Memory Controller
          6   Memory Module
          7   Cache
          8   Port Connector
          9   System Slots
         10   On Board Devices
         11   OEM Strings
         12   System Configuration Options
         13   BIOS Language
         14   Group Associations
         15   System Event Log
         16   Physical Memory Array
         17   Memory Device
         18   32-bit Memory Error
         19   Memory Array Mapped Address
         20   Memory Device Mapped Address
         21   Built-in Pointing Device
         22   Portable Battery
         23   System Reset
         24   Hardware Security
         25   System Power Controls
         26   Voltage Probe
         27   Cooling Device
         28   Temperature Probe
         29   Electrical Current Probe
         30   Out-of-band Remote Access
         31   Boot Integrity Services
         32   System Boot
         33   64-bit Memory Error
         34   Management Device
         35   Management Device Component
         36   Management Device Threshold Data
         37   Memory Channel
         38   IPMI Device
         39   Power Supply

       Additionally, type 126 is used for disabled entries,  type  127  is  an
       end-of-table  marker,  and  types 128 to 255 are for OEM-specific data.
       dmidecode will display these entries  by  default,  but  cannot  decode
       them.

       Keywords can be used instead of type numbers with --type.  Each keyword
       is equivalent to a list of type numbers:

       Keyword     Types
       ------------------------------
       bios        0, 13
       system      1, 12, 15, 23, 32
       baseboard   2, 10
       chassis     3
       processor   4
       memory      5, 6, 16, 17
       cache       7
       connector   8
       slot        9

       Keywords are matched case-insensitively. The  following  command  lines
       are equivalent:

* dmidecode --type 0 --type 13

* dmidecode --type 0,13

* dmidecode --type 0 --type 13

* dmidecode --type 0,13

* dmidecode --type bios

* dmidecode --type BIOS

FILES
       /dev/mem

BUGS
       More often than not, information contained in the DMI tables is inaccuâ
       rate, incomplete or simply wrong.

AUTHORS
       Alan Cox, Jean Delvare

SEE ALSO
       biosdecode(8), mem(4), ownership(8), vpddecode(8)

dmidecode                         August 2005                     DMIDECODE(8)


==== Example output ====

Here's a snippet of output on an ESX host when displaying memory info:

 Handle 0x0028
        DMI type 17, 27 bytes.
        Memory Device
                Array Handle: 0x0025
                Error Information Handle: No Error
                Total Width: 76 bits
                Data Width: 72 bits
                Size: 1024 MB
                Form Factor: DIMM
                Set: 1
                Locator: DIMM 2A
                Bank Locator: Bank0 Bank1
                Type: DDR
                Type Detail: Synchronous
                Speed: 266 MHz (3.8 ns)
                Manufacturer: Not Specified
                Serial Number: Not Specified
                Asset Tag: Not Specified
                Part Number: Not Specified

[[Category: CLI]]</text>
    <sha1>88fde4a3ed9bbc70cb2caebb23406a8d62ce67a6</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Build host vmware kernel modules</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>997</id>
    <parentid>799</parentid>
    <timestamp>2009-07-16T16:55:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2740" xml:space="preserve">====Integrated modules build script sometimes fails====
The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

====The solution====
You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm -f /etc/vmware/not_configured 

====Preconditions for the script to work====
You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>64b51639d6737c4c6f6bf94d53fec1129b24b141</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Xtravirt Visio action pack</title>
  <ns>0</ns>
  <id>481</id>
  <revision>
    <id>999</id>
    <timestamp>2009-07-22T09:40:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Xtravirt has rereleased their Visio action pack for VMware and virtualisation as a free download for members. It contains over 70 icons.  read more:  http://xtravirt.com/xd10110 ...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="207" xml:space="preserve">Xtravirt has rereleased their Visio action pack for VMware and virtualisation as a free download for members.
It contains over 70 icons.

read more:

http://xtravirt.com/xd10110

[[Category: VMware Artwork]]</text>
    <sha1>47749b2b9cd566705c704ecbbb799d6412ce3c5b</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>PowerCLI: Report every VM added to vCenter in the last 30 days</title>
  <ns>0</ns>
  <id>440</id>
  <revision>
    <id>1000</id>
    <parentid>876</parentid>
    <timestamp>2009-07-22T18:13:40Z</timestamp>
    <contributor>
      <username>Acsulli</username>
      <id>31</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="80" xml:space="preserve">http://get-admin.com/blog/?p=725

[[Category: Powershell]] [[Category:PowerCLI]]</text>
    <sha1>afd74f0ef827f844f330e331c8353e6967123d39</sha1>
  </revision>
  <revision>
    <id>1001</id>
    <parentid>1000</parentid>
    <timestamp>2009-07-22T18:15:34Z</timestamp>
    <contributor>
      <username>Acsulli</username>
      <id>31</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="126" xml:space="preserve">Please visit the original author's page here: http://get-admin.com/blog/?p=725

[[Category: Powershell]] [[Category:PowerCLI]]</text>
    <sha1>9eab0619f26c7b12fc52c71ac739dd8141c16e8a</sha1>
  </revision>
</page>
<page arvcontinue="20090630130611|954">
  <title>Esxcfg-dumppart</title>
  <ns>0</ns>
  <id>482</id>
  <revision>
    <id>1002</id>
    <timestamp>2009-07-23T09:26:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with ' NAME      esxcfg-dumppart - VMware ESX Server diagnostic partition configuration      tool   COPYRIGHT      VMware ESX Server is Copyright 2006-2007 VMware, Inc.  All rights res...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2651" xml:space="preserve"> NAME
     esxcfg-dumppart - VMware ESX Server diagnostic partition configuration
     tool

 COPYRIGHT
     VMware ESX Server is Copyright 2006-2007 VMware, Inc.  All rights reserved.
  
 SYNOPSIS
     esxcfg-dumppart  OPTIONS

 DESCRIPTION
     esxcfg-dumppart provides an interface to query, set, and scan for diagnostic partitions on an ESX Server.

==== Usage ====
 esxcfg-dumppart &lt;options&gt; [&lt;partition&gt;]

==== OPTIONS ====
     -l --list
             List all partitions on the system that have the appropriate partition type to act as an ESX Server 
             diagnostic partition.  
             WARNING: Listing will scan all LUNs on a system and may degrade system performance.
  
     -t --get-active
             Get the active diagnostic partition for this system.  This will return the internal name of the 
             partition (vmbhaX:X:X:X) or 'none' if no partition is set.
  
     -c --get-config
             Get the configured diagnostic partition for the system.  This partition may or many not be the 
             active partition, and in a SAN situation this partition may have disappeared.
 
     -s --set vmbhaX:X:X:X
             Set the active and configured diagnostic partition for this system using the vmhba name of the 
             partition to use.
 
     -f --find
             Using the same method as the list option, find all the diagnostic partitions on this ESX Server.  
             Based on the type of storage, print the partitions in order of their desirability to be used as a 
             diagnostic partition.  The order of priority for diagnostic partitions is Parallel adapter, 
             block adapter, Fibre Channel, Hardware iSCSI, software iSCSI.
 
     -S --smart-activate
             Activate the diagnostic partition if one is set and available.
             Otherwise, scan the system and choose an appropriate partition using the same criteria 
             as is used in the "find" option.
 
     -a --activate
             Activate the configured diagnostic partition.
 
     -d --deactivate
             Deactivate the current active diagnostic partition. WARNING: this will leave your system without 
             any means of reporting errors until another partition is activated.
 
     -h --help
             Print the help message.


==== Examples ====
Set the dump partition

  #esxcfg-dumppart --set vmhba0:0:0:6 
Will set the partition for LUN on adapter vmhba0 target 0, LUN 0, partition 6

Find the dump partition

 #esxcfg-dumppart -l
 
 VMKernel Name Console Name Is Active Is Configured
 
 
 mpx.vmhba1:C0:T0:L0:2 /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:2 yes yes</text>
    <sha1>f3e467f5bde3ee5bb78b59aed4738adb5c560033</sha1>
  </revision>
  <revision>
    <id>1003</id>
    <parentid>1002</parentid>
    <timestamp>2009-07-23T09:28:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>minor formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2657" xml:space="preserve"> NAME
     esxcfg-dumppart - VMware ESX Server diagnostic partition configuration
     tool
 
 COPYRIGHT
     VMware ESX Server is Copyright 2006-2007 VMware, Inc.  All rights reserved.
  
 SYNOPSIS
     esxcfg-dumppart  OPTIONS
 
 DESCRIPTION
     esxcfg-dumppart provides an interface to query, set, and scan for diagnostic partitions on an ESX Server.

==== Usage ====
 esxcfg-dumppart &lt;options&gt; [&lt;partition&gt;]

==== OPTIONS ====
     -l --list
             List all partitions on the system that have the appropriate partition type to act as an ESX Server 
             diagnostic partition.  
             WARNING: Listing will scan all LUNs on a system and may degrade system performance.
  
     -t --get-active
             Get the active diagnostic partition for this system.  This will return the internal name of the 
             partition (vmbhaX:X:X:X) or 'none' if no partition is set.
  
     -c --get-config
             Get the configured diagnostic partition for the system.  This partition may or many not be the 
             active partition, and in a SAN situation this partition may have disappeared.
 
     -s --set vmbhaX:X:X:X
             Set the active and configured diagnostic partition for this system using the vmhba name of the 
             partition to use.
 
     -f --find
             Using the same method as the list option, find all the diagnostic partitions on this ESX Server.  
             Based on the type of storage, print the partitions in order of their desirability to be used as a 
             diagnostic partition.  The order of priority for diagnostic partitions is Parallel adapter, 
             block adapter, Fibre Channel, Hardware iSCSI, software iSCSI.
 
     -S --smart-activate
             Activate the diagnostic partition if one is set and available.
             Otherwise, scan the system and choose an appropriate partition using the same criteria 
             as is used in the "find" option.
 
     -a --activate
             Activate the configured diagnostic partition.
 
     -d --deactivate
             Deactivate the current active diagnostic partition. WARNING: this will leave your system without 
             any means of reporting errors until another partition is activated.
 
     -h --help
             Print the help message.


==== Examples ====
* Set the dump partition

  #esxcfg-dumppart --set vmhba0:0:0:6 
Will set the partition for LUN on adapter vmhba0 target 0, LUN 0, partition 6

* Find the dump partition

 #esxcfg-dumppart -l
 
 VMKernel Name Console Name Is Active Is Configured
 
 
 mpx.vmhba1:C0:T0:L0:2 /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:2 yes yes</text>
    <sha1>df5d68ded8c9ed2f8148840abdb1b86e3e5bded0</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Vmkdump</title>
  <ns>0</ns>
  <id>483</id>
  <revision>
    <id>1004</id>
    <timestamp>2009-07-23T09:41:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with ' NAME       vmkdump - VMkernel dumper    SYNOPSIS       vmkdump OPTIONS    COPYRIGHT      VMware ESX Server is Copyright 2004-2007 VMware, Inc.  All rights reserved.    DESCRIPTI...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2789" xml:space="preserve"> NAME
      vmkdump - VMkernel dumper
 
 SYNOPSIS
      vmkdump OPTIONS
 
 COPYRIGHT
     VMware ESX Server is Copyright 2004-2007 VMware, Inc.  All rights reserved.
 
 DESCRIPTION
      vmkdump manages the VMkernel dump partition.

==== Usage ====
      vmkdump -d --devname /dev/&lt;Linux device name&gt;
              -z --zdumpname outputName (optional)
              -n --newonly (optional)
              -s --slot slotnum (optional)
   Extract the log from a compressed dump:
      vmkdump -l --log zdumpname


==== OPTIONS ====
     -d, --devname deviceName
         Specify the Linux console device that should be used to read the  VMkernel dump.  
         Note: This option should not be used after the dump  partition has been set with the -p option.  
         If the partition has been set, you need to stop and reset the VMkernel before using this option.
 
     -n, --newonly
         For each VMkernel dump that is produced, a count is kept of the number of times the compressed 
         dump file has been read off the dump partition.  When this option is specified, the compressed 
         dump will only be read off the dump partition if the read count is zero.

     -z, --zdumpname compressedFileName
         When reading from the dump partition, this option specifies the name of the file to create with 
         the compressed dump.  By default the name is vmkernel-zdump.#, where # is a unique number.

     -s, --slot slotnum
         On dump partitions that reside on shared storage, multiple machines  can share the dump partition.  
         Because of this, the dump partition is split up into multiple slots.  Generally, when retrieving a 
         core dump, the physical machine's UUID is hashed into a slot number based on the total number 
         of slots, and the compressed dump is automatically read from that slot.  
 
         However, there may be situations where the machine that dumped core is no longer able to retrieve 
         core  dumps.  In those cases, this option can be used to override the normal UUID hash algorithm 
         for determining a slot.  Note that the slot used during a core dump will be displayed on the PSOD.
  
     -l, --log compressedFileName
        Extracts the vmkernel log from the specified compressed dump file.


==== Examples ====
* Specify linux device to read the dump
 #vmkdump -d /dev/sda5

Creates a file name vmkernel-zdump. # contained a compressed dump. # is 1 if no other compressed dumps are in the current directory, otherwise # is the lowest unused integer (ie, if up to vmkernel-zdump.5 exist, then it would create vmkernel-zdump.6).


* Extract the zdump from the dump partition
 
 #vmkdump -d /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:2
 
 singleslot coredump
 
 
 created file vmkernel-zdump.1</text>
    <sha1>e825913ec3e35d66c6e8e838d5d53cadcff1e6c1</sha1>
  </revision>
  <revision>
    <id>1011</id>
    <parentid>1004</parentid>
    <timestamp>2009-07-23T10:26:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2808" xml:space="preserve"> NAME
      vmkdump - VMkernel dumper
 
 SYNOPSIS
      vmkdump OPTIONS
 
 COPYRIGHT
     VMware ESX Server is Copyright 2004-2007 VMware, Inc.  All rights reserved.
 
 DESCRIPTION
      vmkdump manages the VMkernel dump partition.

==== Usage ====
      vmkdump -d --devname /dev/&lt;Linux device name&gt;
              -z --zdumpname outputName (optional)
              -n --newonly (optional)
              -s --slot slotnum (optional)
   Extract the log from a compressed dump:
      vmkdump -l --log zdumpname


==== OPTIONS ====
     -d, --devname deviceName
         Specify the Linux console device that should be used to read the  VMkernel dump.  
         Note: This option should not be used after the dump  partition has been set with the -p option.  
         If the partition has been set, you need to stop and reset the VMkernel before using this option.
 
     -n, --newonly
         For each VMkernel dump that is produced, a count is kept of the number of times the compressed 
         dump file has been read off the dump partition.  When this option is specified, the compressed 
         dump will only be read off the dump partition if the read count is zero.

     -z, --zdumpname compressedFileName
         When reading from the dump partition, this option specifies the name of the file to create with 
         the compressed dump.  By default the name is vmkernel-zdump.#, where # is a unique number.

     -s, --slot slotnum
         On dump partitions that reside on shared storage, multiple machines  can share the dump partition.  
         Because of this, the dump partition is split up into multiple slots.  Generally, when retrieving a 
         core dump, the physical machine's UUID is hashed into a slot number based on the total number 
         of slots, and the compressed dump is automatically read from that slot.  
 
         However, there may be situations where the machine that dumped core is no longer able to retrieve 
         core  dumps.  In those cases, this option can be used to override the normal UUID hash algorithm 
         for determining a slot.  Note that the slot used during a core dump will be displayed on the PSOD.
  
     -l, --log compressedFileName
        Extracts the vmkernel log from the specified compressed dump file.


==== Examples ====
* Specify linux device to read the dump
 #vmkdump -d /dev/sda5

Creates a file name vmkernel-zdump. # contained a compressed dump. # is 1 if no other compressed dumps are in the current directory, otherwise # is the lowest unused integer (ie, if up to vmkernel-zdump.5 exist, then it would create vmkernel-zdump.6).


* Extract the zdump from the dump partition
 
 #vmkdump -d /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:2
 
 singleslot coredump
 
 
 created file vmkernel-zdump.1

[[Category: CLI]]</text>
    <sha1>522253760b0df29fe51b013c4969ec2d24e8b4e5</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>VI-Toolkit:Community Portal</title>
  <ns>4</ns>
  <id>6</id>
  <revision>
    <id>1005</id>
    <parentid>772</parentid>
    <timestamp>2009-07-23T09:51:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1214" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and VMware [[VI Perl Toolkit]] to aide in managing your VI infrastructure.

In vSphere we now use the [vMA] appliance, documentation is here http://www.vmware.com/support/developer/vcli/</text>
    <sha1>39645e8f2f8e09e6b3f120a04d9d49228a181ed5</sha1>
  </revision>
  <revision>
    <id>1006</id>
    <parentid>1005</parentid>
    <timestamp>2009-07-23T09:52:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1216" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and VMware [[VI Perl Toolkit]] to aide in managing your VI infrastructure.

In vSphere we now use the [[vMA]] appliance, documentation is here http://www.vmware.com/support/developer/vcli/</text>
    <sha1>85523654a3c62d2d013d14510cb21235cbbb28c3</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>1007</id>
    <parentid>998</parentid>
    <timestamp>2009-07-23T09:55:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="527" xml:space="preserve">[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[VICL, A VMWare Interface Client for Linux]]

[[psVIC, a powershell Virtual Infrastructure Client]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]

[[Xtravirt Visio action pack]]</text>
    <sha1>8365d874fc81ee477c5a85f3b814f70a0ecb85a8</sha1>
  </revision>
  <revision>
    <id>1013</id>
    <parentid>1007</parentid>
    <timestamp>2009-07-23T13:23:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="627" xml:space="preserve">Below are links to VMware related open source projects, which I've found particularly interesting.

[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[VICL, A VMWare Interface Client for Linux]]

[[psVIC, a powershell Virtual Infrastructure Client]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]

[[Xtravirt Visio action pack]]</text>
    <sha1>e93f8a4568e785b22e7ef2fa1b0149acb1d98a3c</sha1>
  </revision>
  <revision>
    <id>1022</id>
    <parentid>1013</parentid>
    <timestamp>2009-08-04T23:09:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>adding vinternals unattended ESXi install</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="661" xml:space="preserve">Below are links to VMware related open source projects, which I've found particularly interesting.

[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[VICL, A VMWare Interface Client for Linux]]

[[psVIC, a powershell Virtual Infrastructure Client]]

[[Unattended ESXi installation]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]

[[Xtravirt Visio action pack]]</text>
    <sha1>38345c45e6979810c9b3b5064d8ca5edd08aeedb</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PsVIC, a powershell Virtual Infrastructure Client</title>
  <ns>0</ns>
  <id>484</id>
  <revision>
    <id>1008</id>
    <timestamp>2009-07-23T09:59:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'A small Powershell based VI Client for VMware Administrators which uses Powershell 2 CTP3, the VI Toolkit and optionally the VMware VMRC browser plugin.  It is able to perform ta...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="403" xml:space="preserve">A small Powershell based VI Client for VMware Administrators which uses Powershell 2 CTP3, the VI Toolkit and optionally the VMware VMRC browser plugin.

It is able to perform tasks like:
 * moving a vm to a host/folder/resource pool/datastore
 * connect via remote console to a VM 
 * gather VM Information

read more:

http://code.google.com/p/psvic/

[[Category: Powershell]] [[Category: VI-Toolkit]]</text>
    <sha1>ad27dd36522e76cfb1c5efa2b9ba47bdda59371f</sha1>
  </revision>
  <revision>
    <id>1009</id>
    <parentid>1008</parentid>
    <timestamp>2009-07-23T10:00:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>formatting again, when will i learn to use the preview function? Sigh ;)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="400" xml:space="preserve">A small Powershell based VI Client for VMware Administrators which uses Powershell 2 CTP3, the VI Toolkit and optionally the VMware VMRC browser plugin.

It is able to perform tasks like:
* moving a vm to a host/folder/resource pool/datastore
* connect via remote console to a VM 
* gather VM Information

read more:

http://code.google.com/p/psvic/

[[Category: Powershell]] [[Category: VI-Toolkit]]</text>
    <sha1>94b281ae29c88e4305bb1ee2449960d2c7d8ea8e</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Esxcfg-dumppart</title>
  <ns>0</ns>
  <id>482</id>
  <revision>
    <id>1010</id>
    <parentid>1003</parentid>
    <timestamp>2009-07-23T10:25:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2676" xml:space="preserve"> NAME
     esxcfg-dumppart - VMware ESX Server diagnostic partition configuration
     tool
 
 COPYRIGHT
     VMware ESX Server is Copyright 2006-2007 VMware, Inc.  All rights reserved.
  
 SYNOPSIS
     esxcfg-dumppart  OPTIONS
 
 DESCRIPTION
     esxcfg-dumppart provides an interface to query, set, and scan for diagnostic partitions on an ESX Server.

==== Usage ====
 esxcfg-dumppart &lt;options&gt; [&lt;partition&gt;]

==== OPTIONS ====
     -l --list
             List all partitions on the system that have the appropriate partition type to act as an ESX Server 
             diagnostic partition.  
             WARNING: Listing will scan all LUNs on a system and may degrade system performance.
  
     -t --get-active
             Get the active diagnostic partition for this system.  This will return the internal name of the 
             partition (vmbhaX:X:X:X) or 'none' if no partition is set.
  
     -c --get-config
             Get the configured diagnostic partition for the system.  This partition may or many not be the 
             active partition, and in a SAN situation this partition may have disappeared.
 
     -s --set vmbhaX:X:X:X
             Set the active and configured diagnostic partition for this system using the vmhba name of the 
             partition to use.
 
     -f --find
             Using the same method as the list option, find all the diagnostic partitions on this ESX Server.  
             Based on the type of storage, print the partitions in order of their desirability to be used as a 
             diagnostic partition.  The order of priority for diagnostic partitions is Parallel adapter, 
             block adapter, Fibre Channel, Hardware iSCSI, software iSCSI.
 
     -S --smart-activate
             Activate the diagnostic partition if one is set and available.
             Otherwise, scan the system and choose an appropriate partition using the same criteria 
             as is used in the "find" option.
 
     -a --activate
             Activate the configured diagnostic partition.
 
     -d --deactivate
             Deactivate the current active diagnostic partition. WARNING: this will leave your system without 
             any means of reporting errors until another partition is activated.
 
     -h --help
             Print the help message.


==== Examples ====
* Set the dump partition

  #esxcfg-dumppart --set vmhba0:0:0:6 
Will set the partition for LUN on adapter vmhba0 target 0, LUN 0, partition 6

* Find the dump partition

 #esxcfg-dumppart -l
 
 VMKernel Name Console Name Is Active Is Configured
 
 
 mpx.vmhba1:C0:T0:L0:2 /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:2 yes yes

[[Category: CLI]]</text>
    <sha1>dde5eb38cbdae37fd9f13279127604d834026bfd</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>1012</id>
    <parentid>902</parentid>
    <timestamp>2009-07-23T12:22:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1870" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages. Partly done
* Add "what's new" to the main page
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* &lt;s&gt;Find a better way to present what's available on the site, improve ways to restructure the data. &lt;/s&gt; The support for category tree at the main page now gives a much easier way to navigate the site. But it never hurts to find better ways as this doesn't scale too well (look at the vimsh category for example)
* Improve main page
* Add example code
* Add a theme for mobile phones, so it is easier to read the content

==== Things to make our mind up about ====

* Does the site need a forum?
* Does the site need an instant messager type of control ?
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ?
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ?

[[Category: website]]</text>
    <sha1>b57fd0fd75ca672ba53af1dc0ceff49c41fc4545</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerCLI: Report every VM added to vCenter in the last 30 days</title>
  <ns>0</ns>
  <id>440</id>
  <revision>
    <id>1014</id>
    <parentid>1001</parentid>
    <timestamp>2009-07-23T14:50:16Z</timestamp>
    <contributor>
      <username>Acsulli</username>
      <id>31</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="359" xml:space="preserve">By using the PowerCLI and VMware's SDK it is entirely possible to query the history of tasks and events.  One of the data gems that can be garnered from the event history is when virtual machines have been created or deleted.

You can find how to query the event history [http://get-admin.com/blog/?p=725 here].

[[Category: Powershell]] [[Category:PowerCLI]]</text>
    <sha1>9a35b8de5f5c719822c62d8c36e0f3894364e0b0</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerCLI: Oneliners</title>
  <ns>0</ns>
  <id>463</id>
  <revision>
    <id>1015</id>
    <parentid>989</parentid>
    <timestamp>2009-07-23T15:00:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added the 'tell me when done' oneliner from get-admin site</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3558" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added from other great powershell scripters.


==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]


==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

==== Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>8bc57f2fb38a1b93634d65fcc0b08c000b6a85ec</sha1>
  </revision>
  <revision>
    <id>1026</id>
    <parentid>1015</parentid>
    <timestamp>2009-08-17T11:44:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Alan's Check processor types oneliner</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3646" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added from other great powershell scripters.


==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]


==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

==== Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check processor types]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>58725e557a22c89160a6a9f938a09e4bce0dfd96</sha1>
  </revision>
  <revision>
    <id>1027</id>
    <parentid>1026</parentid>
    <timestamp>2009-08-17T11:45:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3651" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added from other great powershell scripters.


==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]


==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

==== Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>3a0c3e35e6681160cecbb617c30a9197704f8b19</sha1>
  </revision>
  <revision>
    <id>1028</id>
    <parentid>1027</parentid>
    <timestamp>2009-08-17T12:21:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Split up configuration paragraph into Host Config and VM Config, Added automated notes/description oneliners for VMs from Arne Fokkema</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4131" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added from other great powershell scripters. This page now contains oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]


==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>3cc7dd12e7417febb30eb002b13bbeb37f2db0c9</sha1>
  </revision>
  <revision>
    <id>1029</id>
    <parentid>1028</parentid>
    <timestamp>2009-08-17T12:22:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>improved wording a bit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4140" xml:space="preserve">This page could be dedicated to [http://www.peetersonline.nl/index.php/about/ Hugo Peeters] as he's been supplying the community with very useful powershell oneliners for a while. But he's not the only supplier anymore as more links are getting added from other great powershell scripters. This page now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]


==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>d85d7e4a8a1b12437f87ca45ac0f3c577b7a5489</sha1>
  </revision>
  <revision>
    <id>1041</id>
    <parentid>1029</parentid>
    <timestamp>2009-08-19T20:06:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3626" xml:space="preserve">
==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]


==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>0356d679b06145ff026b794d7fecd7cffab43064</sha1>
  </revision>
  <revision>
    <id>1043</id>
    <parentid>1041</parentid>
    <timestamp>2009-08-19T20:10:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2781" xml:space="preserve">

==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>c6be443e5174b6f601fcf8a745982981df4e1452</sha1>
  </revision>
  <revision>
    <id>1045</id>
    <parentid>1043</parentid>
    <timestamp>2009-08-19T20:11:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2131" xml:space="preserve">
==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>25f21517126977513ca1ef5264a63804304ebea1</sha1>
  </revision>
  <revision>
    <id>1047</id>
    <parentid>1045</parentid>
    <timestamp>2009-08-19T20:11:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1195" xml:space="preserve">
==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>20ead6b46465461d4894d7bdf5374b67168ed6ce</sha1>
  </revision>
  <revision>
    <id>1049</id>
    <parentid>1047</parentid>
    <timestamp>2009-08-19T20:12:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="278" xml:space="preserve">
==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>3bd2eec7547ede351bd00108258a57fb4524e8f7</sha1>
  </revision>
  <revision>
    <id>1051</id>
    <parentid>1049</parentid>
    <timestamp>2009-08-19T20:13:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Blanked the page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>ESX CLI Commands</title>
  <ns>0</ns>
  <id>416</id>
  <revision>
    <id>1016</id>
    <parentid>952</parentid>
    <timestamp>2009-07-26T08:46:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Changes to the ESX Service Console for ESX 4.0 (Thanks Jason Boche for finding the VMTN post with the PDF)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2929" xml:space="preserve">==== ESX CLI Commands ====

Virtual Infrastructure ESX has a service console which can be used to management purposes.
This is a light weight linux based (RHEL3) Virtual Machine which has special privileges that can be used in order to manage your host and Virtual Machines.
Down here we will be trying to document the available commands that you can use on this service console from the so called Command Line Interface (CLI).

In ESXi (3.x) the service console has been removed from the host and there's only a remote alternative available, which is called the [[RCLI]].
The chapter here only contains the documentation for the full blown version not the RCLI.

Any changes made to the configuration of the host will not be seen by vCenter Server or the host itself until you restart the vmware-hostd daemon. By restarting this daemon, the configuration file /etc/vmware/esx.conf will be re-read.

 service mgmt-vmware restart

will restart this daemon.


==== The available commands ====

 [[dmidecode]]
 [[esxcfg-advcfg]]      
 [[esxcfg-auth]]        
 [[esxcfg-boot]]        
 [[esxcfg-configcheck]]
 [[esxcfg-dumppart]]   
 [[esxcfg-firewall]]   
 [[esxcfg-hwiscsi]]    
 [[esxcfg-info]]     
 [[esxcfg-init]]
 [[esxcfg-linuxnet]]
 [[esxcfg-module]]
 [[esxcfg-mpath]]
 [[esxcfg-nas]]
 [[esxcfg-nics]]
 [[esxcfg-pciid]]
 [[esxcfg-rescan]]
 [[esxcfg-resgrp]]
 [[esxcfg-route]]
 [[esxcfg-swiscsi]]
 [[esxcfg-upgrade]]
 [[esxcfg-vmhbadevs]]
 [[esxcfg-vmknic]]
 [[esxcfg-vswif]]
 [[esxcfg-vswitch]]
 [[esxupdate]]
 [[vcbExport]]
 [[vcbMounter]]
 [[vcbResAll]]
 [[vcbRestore]]
 [[vcbSnapAll]]
 [[vcbSnapshot]]
 [[vcbUtil]]
 [[vcbVmName]]
 [[vdf]]
 [[vimsh]]
 [[vmfsqhtool]]
 [[vmfsqueuetool]]
 [[vmkchdev]]
 [[vmkdump]]
 [[vmkerrcode]]
 [[vmkfstools]]
 [[vmkiscsid]]
 [[vmkiscsi-device]]
 [[vmkiscsi-ls]]
 [[vmkiscsi-tool]]
 [[vmkiscsi-util]]
 [[vmkloader]]
 [[vmkload_mod]]
 [[vmklogger]]
 [[vmkpcidivy]]
 [[vmkping]]
 [[vmkuptime.pl]]
 [[vmres.pl]]
 [[vmsnap_all]]
 [[vmsnap.pl]]
 [[vmstat]]
 [[vm-support]]
 [[vmware]]
 [[vmware-authd]]
 [[vmware-autopoweron.sh]]
 [[vmware-cmd]]
 [[vmware-configcheck]]
 [[vmware-config.pl]]
 [[vmware-hostd]]
 [[vmware-hostd-support]]
 [[vmware-mkinitrd]]
 [[vmware-vim-cmd]]         
 [[vmware-vimdump]]         
 [[vmware-vimsh]]
 [[vmware-watchdog]]
 [[vmware-webAccess]]

==== External Links ====

* [http://download3.vmware.com/vmworld/2006/tac9685.pdf VMworld 2006: Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

* [http://www.rtfm-ed.co.uk/docs/vmwdocs/ESX3.x-VC2.x-ServiceConsole-Guide.pdf RTFM Education: ESX3.x Service Console Guide]

* [http://www.b2v.co.uk/b2vguide2vmware.htm B2V Guide to VMware ESX Server 2.x]

* [http://www.jume.nl/index.php?option=com_content&amp;task=view&amp;id=115&amp;Itemid=1 Jume: ESX vSphere Man pages]

* [http://communities.vmware.com/message/1320276 Changes to the ESX Service Console for ESX 4.0]

[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>079bdc518f6a9e46a7456fd95f2b1fcdc962814d</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>1017</id>
    <parentid>990</parentid>
    <timestamp>2009-08-01T13:19:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3898" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>b06e84bcfcf9c331b45eff0917b2ca8fd8500263</sha1>
  </revision>
  <revision>
    <id>1020</id>
    <parentid>1017</parentid>
    <timestamp>2009-08-04T20:55:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3946" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>716aedf622e4f1114d7ae42cab9042af177ac783</sha1>
  </revision>
  <revision>
    <id>1024</id>
    <parentid>1020</parentid>
    <timestamp>2009-08-05T10:26:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>general powershell, added link to Geekpoet: Report on all scheduled tasks in your domain</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4079" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>f8346135e26d816e43156a3f975c3e5e8cbefe4c</sha1>
  </revision>
  <revision>
    <id>1040</id>
    <parentid>1024</parentid>
    <timestamp>2009-08-19T20:05:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4303" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>59e78a992f4598ba798855440355ef53a93b6593</sha1>
  </revision>
  <revision>
    <id>1042</id>
    <parentid>1040</parentid>
    <timestamp>2009-08-19T20:09:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Reorganizing our Powershell oneliner scripts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4866" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Restart VMware Tools on all Windows VM's]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Oneliners]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>7ae82475a783514412dd68c6593294ff6db4cc83</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>VMWareTasks</title>
  <ns>0</ns>
  <id>273</id>
  <revision>
    <id>1018</id>
    <parentid>587</parentid>
    <timestamp>2009-08-04T13:13:52Z</timestamp>
    <contributor>
      <username>Dblock</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="581" xml:space="preserve">====VMWareTasks====

VMWareTasks is a C# library on top of the VIX API. It exposes a better programming model for the 99% of those synchronous VMWare scenarios where you don't want to deal with jobs or other more complex constructs.

====Official Website===
* http://vmwaretasks.codeplex.com

====Project Links====
* http://www.codeproject.com/KB/library/VMWareTasks.aspx
* http://code.dblock.org/ShowPost.aspx?id=25
* [http://communities.vmware.com/thread/186164 VMWareTasks: A VIX API C# Library (let's reinvent less wheels)]

[[Category: VIX]][[Category: SDK]][[Category: .net]]</text>
    <sha1>0d1df6cde948b3d3c50d0274772d831031228a5b</sha1>
  </revision>
  <revision>
    <id>1019</id>
    <parentid>1018</parentid>
    <timestamp>2009-08-04T13:14:04Z</timestamp>
    <contributor>
      <username>Dblock</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="582" xml:space="preserve">====VMWareTasks====

VMWareTasks is a C# library on top of the VIX API. It exposes a better programming model for the 99% of those synchronous VMWare scenarios where you don't want to deal with jobs or other more complex constructs.

====Official Website====
* http://vmwaretasks.codeplex.com

====Project Links====
* http://www.codeproject.com/KB/library/VMWareTasks.aspx
* http://code.dblock.org/ShowPost.aspx?id=25
* [http://communities.vmware.com/thread/186164 VMWareTasks: A VIX API C# Library (let's reinvent less wheels)]

[[Category: VIX]][[Category: SDK]][[Category: .net]]</text>
    <sha1>2a46293d886d74bba4eac94a047d554fbde84a5e</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerCLI: Get Virtual Machine total size</title>
  <ns>0</ns>
  <id>485</id>
  <revision>
    <id>1021</id>
    <timestamp>2009-08-04T21:00:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Get total size of VM from Arnim van Lieshout</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="443" xml:space="preserve">Ever wondered how much disk space your Virtual Machine actually is using?
Arnim van Lieshout wrote a script that takes it all into account, including snapshots, swap files, log files and even the configuration files. No matter if these files are different LUNS or not. The script just takes the name of your VM as a parameter and does the math for you.

read more:

http://www.van-lieshout.com/2009/07/how-big-is-my-vm/

[[Category: PowerCLI]]</text>
    <sha1>2830b70c22cd8f72bb8bd9958112fabbaa9c2134</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Unattended ESXi installation</title>
  <ns>0</ns>
  <id>486</id>
  <revision>
    <id>1023</id>
    <timestamp>2009-08-04T23:15:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Stu has taken an alternative route to creating an unattended ESXi install.  While the conventional way is to use PXE boot installs, he has customized the python install routine t...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="411" xml:space="preserve">Stu has taken an alternative route to creating an unattended ESXi install.

While the conventional way is to use PXE boot installs, he has customized the python install routine to make it do what he needs.
He has setup an example of what you can do, but you do not have to stop there...

read more:

http://vinternals.com/2009/07/unattended-esxi-installation/

[[Category: Python]] [[Category: Host Management]]</text>
    <sha1>dabcf5c0af15a48105d9eb30ef5d3862986e2203</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Virtualisation technical articles</title>
  <ns>0</ns>
  <id>412</id>
  <revision>
    <id>1025</id>
    <parentid>768</parentid>
    <timestamp>2009-08-10T10:27:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added visophyte article on Using VMWare Record/Replay and VProbes for low time-distortion performance profiling</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1156" xml:space="preserve">This page contains links to technical articles about virtualisation technology.
It's a sort of fancy bookmark of what I consider interesting reading as a programmer... this is not likely to be interesting for everyone ;)

* [http://www.codeproject.com/KB/debug/cdbntsd6.aspx Navigating the kernel debugger]
This tutorial covers a few of the basic features of the kernel debugger and has some tips on getting used to using it. 

* [http://www.ddj.com/cpp/184402033 Sharing memory with the virtual machine]
Tricks on sharing data between guest OS instances and the host. 

* [http://www.codeplex.com/visa/Wiki/View.aspx?title=English%20version&amp;referringTitle=Home Virtualisation Instruction Set Architecture]
MIPS R3000 processor model, available at ArchC was extended to offer virtualisation support, adding instructions and structures inspired by Intel VT-x.

* [http://www.visophyte.org/blog/2009/08/03/using-vmware-recordreplay-and-vprobes-for-low-time-distortion-performance-profiling/ Using VMWare Record/Replay and VProbes for low time-distortion performance profiling]
Advanced article on how-to use VMware for your application performance profiling.</text>
    <sha1>584b70179c165ec81aeeb87ab669cb4bf37fecc6</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Xtravirt Visio action pack</title>
  <ns>0</ns>
  <id>481</id>
  <revision>
    <id>1030</id>
    <parentid>999</parentid>
    <timestamp>2009-08-19T07:51:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="246" xml:space="preserve">Xtravirt has rereleased their Visio action pack for VMware and virtualisation as a free download for members.
It contains over 70 icons.

read more:

http://xtravirt.com/xd10110

http://xtravirt.com/presentation-pack

[[Category: VMware Artwork]]</text>
    <sha1>c3ceb8327ea3c967aa1e4380bb8c72e59d5822dd</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Perl</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>1031</id>
    <parentid>63</parentid>
    <timestamp>2009-08-19T11:06:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>start of adding William Lam's perl scripts in down here</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="57" xml:space="preserve">[[Esx scripts]]

[[Adding/updating a custom field to VM]]</text>
    <sha1>ebd092b53b5be3659075e7ab81579cd9d12f55f3</sha1>
  </revision>
  <revision>
    <id>1033</id>
    <parentid>1031</parentid>
    <timestamp>2009-08-19T13:44:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="106" xml:space="preserve">[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Get status of VMware Tools on all your VM's]]</text>
    <sha1>06eab0bf7a720f2b14738cc7bdce97896f33dde0</sha1>
  </revision>
  <revision>
    <id>1035</id>
    <parentid>1033</parentid>
    <timestamp>2009-08-19T14:13:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="164" xml:space="preserve">[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]</text>
    <sha1>d87e5b5d237250b8d5aed671ecd3b361183cf9ea</sha1>
  </revision>
  <revision>
    <id>1037</id>
    <parentid>1035</parentid>
    <timestamp>2009-08-19T14:48:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="206" xml:space="preserve">[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]</text>
    <sha1>f991aae44347ba2f4d7ac4a2e0190f502a928e6e</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Adding/updating a custom field to VM</title>
  <ns>0</ns>
  <id>487</id>
  <revision>
    <id>1032</id>
    <timestamp>2009-08-19T11:16:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '=== addVMCustomField.pl === author: William Lam ==== Description ==== Allows you to create a custom field and value to the vmx configuration file of your VM.  ==== Usage: ==== Th...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="863" xml:space="preserve">=== addVMCustomField.pl ===
author: William Lam
==== Description ====
Allows you to create a custom field and value to the vmx configuration file of your VM.

==== Usage: ====
This will add a new custom field to all VMs called SERVER_TYPE and the operation is an add

 [vi-admin@scofield ~]$ ./addVMCountCustomField.pl --server reflex.primp-industries.com --username primp --key SERVER_TYPE --operation add
 Enter password:

Updates the VM named "Kate" with the value "PRODUCTION" to the custom field "SERVER_TYPE". For this, you'll use the operation update
 [vi-admin@scofield ~]$ ./addVMCountCustomField.pl --server reflex.primp-industries.com --username primp --key SERVER_TYPE --value PRODUCTION --operation update --vmname kate
 Enter password:

==== Location ====

http://communities.vmware.com/docs/DOC-10550

[[Category: Perl]] [[Category: VM Management]]</text>
    <sha1>f7987fb74204d0a0f8561b27edf8f6ab1ce85dd6</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Get status of VMware Tools on all your VM's</title>
  <ns>0</ns>
  <id>488</id>
  <revision>
    <id>1034</id>
    <timestamp>2009-08-19T13:48:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>William Lam's getVMToolsStatus.pl script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="633" xml:space="preserve">=== getVMToolsStatus.pl ===
author: William Lam
==== Description ====
Allows you to query the status of VMware Tools on all of your VMs within a cluster or host..

==== Usage: ====
 [vi-admin@scofield ~]$ ./getVMToolsStatus.pl --server reflex.primp-industries.com --username primp
 Enter password:
 
 Auroa   toolsNotInstalled
 Bitsy   toolsNotInstalled
 Certiorari      toolsNotRunning
 Clifford        toolsOk
 ESX-Kickstart   toolsNotInstalled
 ESX3.5u4        toolsNotInstalled
 ESX4-2  toolsNotInstalled
 .........

==== Location ====

http://communities.vmware.com/docs/DOC-10563

[[Category: Perl]] [[Category: VM Management]]</text>
    <sha1>69d5370ce5910c2151ba77c3076832719850643b</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Add/modify advanced parameter configuration for a VM</title>
  <ns>0</ns>
  <id>489</id>
  <revision>
    <id>1036</id>
    <timestamp>2009-08-19T14:17:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>William Lam's addVMAdvParamOption.pl script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="733" xml:space="preserve">=== addVMAdvParamOption.pl ===
author: William Lam
==== Description ====
Allows you to create a advanced parameter and change the value for the vmx configuration file of your VM.

==== Usage: ====
Adding a new param called vmx.allowNested with value true to a VM against ESX host:

 [vi-admin@scofield ~]$ ./addVMAdvParamOption.pl --server himalaya.primp-industries.com --username root --vmname ESX3.5u4 --key vmx.allowNested --value true
 Enter password:
 Reconfiguring "ESX3.5u4" with advanced parameter configuration: "vmx.allowNested=&gt;true" ...
 Sucessfully updated advanced parameter configuration for "ESX3.5u4"!


==== Location ====

http://communities.vmware.com/docs/DOC-10551

[[Category: Perl]] [[Category: VM Management]]</text>
    <sha1>5965cfb9e086d81cc13c40fb040ab755bcf1e9d4</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>Get number of vCPU's used in cluster</title>
  <ns>0</ns>
  <id>490</id>
  <revision>
    <id>1038</id>
    <timestamp>2009-08-19T14:54:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>William Lam's getNumofvCPUInCluster.pl script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="855" xml:space="preserve">=== getNumofvCPUInCluster.pl ===
author: William Lam
==== Description ====
Allows you to retrieve the number of vCPU's used in the cluster you provide as a parameter.

==== Usage: ====
 [vi-admin@scofield]$ ./getNumofvCPUInCluster.pl --server reflex.primp-industries.com --username primp --cluster primp-cluster
 This could take a few minutes depending on the size of the cluster ...
 
 Cluster: primp-cluster
 	Host: primp-esx01 
 		Misc.RunningVCpuLimit: 128
 		# of vCPU on host: 12
	Host: primp-esx02
		Misc.RunningVCpuLimit: 128
		# of vCPU on host: 13
	Host: primp-esx03
		Misc.RunningVCpuLimit: 128
		# of vCPU on host: 16
	Host: primp-esx04
		Misc.RunningVCpuLimit: 128
		# of vCPU on host: 16
      ..........
      # of vCPU: 463

==== Location ====

http://communities.vmware.com/docs/DOC-10556

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>c3b3a23279e0483d97885457f0d4e536d162b3f1</sha1>
  </revision>
  <revision>
    <id>1039</id>
    <parentid>1038</parentid>
    <timestamp>2009-08-19T14:55:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>fixed formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="866" xml:space="preserve">=== getNumofvCPUInCluster.pl ===
author: William Lam
==== Description ====
Allows you to retrieve the number of vCPU's used in the cluster you provide as a parameter.

==== Usage: ====
 [vi-admin@scofield]$ ./getNumofvCPUInCluster.pl --server reflex.primp-industries.com --username primp --cluster primp-cluster
 This could take a few minutes depending on the size of the cluster ...
 
 Cluster: primp-cluster
 	Host: primp-esx01 
 		Misc.RunningVCpuLimit: 128
 		# of vCPU on host: 12
 	Host: primp-esx02
 		Misc.RunningVCpuLimit: 128
 		# of vCPU on host: 13
 	Host: primp-esx03 
 		Misc.RunningVCpuLimit: 128
 		# of vCPU on host: 16
 	Host: primp-esx04
 		Misc.RunningVCpuLimit: 128 
 		# of vCPU on host: 16
      ..........
      # of vCPU: 463

==== Location ====

http://communities.vmware.com/docs/DOC-10556

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>4115695cd7d830d4f7d644f56b26b97a0b675e16</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerCLI Oneliners: Statistics</title>
  <ns>0</ns>
  <id>491</id>
  <revision>
    <id>1044</id>
    <timestamp>2009-08-19T20:10:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '==== Statistics ====  * [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]  * [http://www.virtu-al.net/2009/07/01/powe...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="843" xml:space="preserve">==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]</text>
    <sha1>0b2234c36dc48e03a424fdc0375166d67d0615af</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerCLI Oneliners: Events</title>
  <ns>0</ns>
  <id>492</id>
  <revision>
    <id>1046</id>
    <timestamp>2009-08-19T20:11:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with ' ==== Events ====  * [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]  * [http://www.peetersonline.nl/index.php/vmware/quick-vi-t...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="648" xml:space="preserve">
==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]</text>
    <sha1>63bdece9759b5ecd58f2395e1fc192f4679139b2</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerCLI Oneliners: Host Configuration</title>
  <ns>0</ns>
  <id>493</id>
  <revision>
    <id>1048</id>
    <timestamp>2009-08-19T20:12:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '==== Host Configuration ==== * [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]  * [http://www...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="934" xml:space="preserve">==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]</text>
    <sha1>7de20f8b0d57fbb2805cddf68c7ebf1dbdce4ae1</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerCLI Oneliners: VM Configuration</title>
  <ns>0</ns>
  <id>494</id>
  <revision>
    <id>1050</id>
    <timestamp>2009-08-19T20:12:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '==== VM Configuration ====  * [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]  * [http://www.virtu-al.net/2009/07...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="915" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]</text>
    <sha1>f7ece6fa2474ff8f6eec08b1f16724b49d76393a</sha1>
  </revision>
</page>
<page arvcontinue="20090723094128|1004">
  <title>PowerCLI Oneliners: Storage</title>
  <ns>0</ns>
  <id>495</id>
  <revision>
    <id>1052</id>
    <timestamp>2009-08-19T20:13:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '==== Storage ==== * [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]  * [http://www.peetersonline.nl...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="277" xml:space="preserve">==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]]</text>
    <sha1>652e2a12f8adff66c359c2bd635e1daa2c9bc402</sha1>
  </revision>
  <revision>
    <id>1053</id>
    <parentid>1052</parentid>
    <timestamp>2009-08-19T20:14:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="306" xml:space="preserve">==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>dee16f6afcc589bd17342ea896cbf2c97218cf6b</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI Oneliners: VM Configuration</title>
  <ns>0</ns>
  <id>494</id>
  <revision>
    <id>1054</id>
    <parentid>1050</parentid>
    <timestamp>2009-08-19T20:14:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="966" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>b0247ce6dc9cc225c8af6db8676e0d80b89bc5a7</sha1>
  </revision>
  <revision>
    <id>1074</id>
    <parentid>1054</parentid>
    <timestamp>2009-08-24T18:14:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to Get VMware tools version oneliner from Luc Dekens in the vmtn forum</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1053" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

* [http://communities.vmware.com/thread/227705 Get VMware Tools version for all VM's]

[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>b32c9ae4236b725562fa912c27d19dee499ea3a1</sha1>
  </revision>
  <revision>
    <id>1080</id>
    <parentid>1074</parentid>
    <timestamp>2009-08-24T23:21:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Maish Saidel-Keesing his oneliner for using storage VMotion to move a VM</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1163" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

* [http://communities.vmware.com/thread/227705 Get VMware Tools version for all VM's]

* [http://technodrone.blogspot.com/2009/08/powercli-storage-vmotion.html Relocate VM using storage VMoition]

[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>e5bf47acb55d194921265537b030ad4f3b0ec6ad</sha1>
  </revision>
  <revision>
    <id>1081</id>
    <parentid>1080</parentid>
    <timestamp>2009-08-24T23:22:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>fixed typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1162" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

* [http://communities.vmware.com/thread/227705 Get VMware Tools version for all VM's]

* [http://technodrone.blogspot.com/2009/08/powercli-storage-vmotion.html Relocate VM using storage VMotion]

[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>3e1d4c01f2e731ea566e6483b9a3990f62abb647</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI Oneliners: Host Configuration</title>
  <ns>0</ns>
  <id>493</id>
  <revision>
    <id>1055</id>
    <parentid>1048</parentid>
    <timestamp>2009-08-19T20:15:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="987" xml:space="preserve">==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>a9bb06b7bb34dc1ca97779937d24ba6cecde7c38</sha1>
  </revision>
  <revision>
    <id>1063</id>
    <parentid>1055</parentid>
    <timestamp>2009-08-19T20:50:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Alan's Do you have the time oneliner</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1137" xml:space="preserve">==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.virtu-al.net/2009/08/14/powercli-do-you-have-the-time/ Check that Hosts are using the same NTP Server and that the service is started]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>bba9384193e7a7839d03152300adf8bf50eb595d</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI Oneliners: Events</title>
  <ns>0</ns>
  <id>492</id>
  <revision>
    <id>1056</id>
    <parentid>1046</parentid>
    <timestamp>2009-08-19T20:15:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="700" xml:space="preserve">==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>383fe6e486808fde3b9386a8853c575e6ea78b09</sha1>
  </revision>
  <revision>
    <id>1069</id>
    <parentid>1056</parentid>
    <timestamp>2009-08-21T14:39:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Arne Fokkema's Reading VMkernel Logfiles or warnings with Powershell v2 script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="843" xml:space="preserve">==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

* [http://ict-freak.nl/2009/08/20/powercli-reading-the-vmkernel-logfiles-with-powershell-v2 Reading the VMKERNEL logfiles with Powershell v2]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>57fd58c2bc54c64c39abf2a01f1aeccd81929f50</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI Oneliners: Statistics</title>
  <ns>0</ns>
  <id>491</id>
  <revision>
    <id>1057</id>
    <parentid>1044</parentid>
    <timestamp>2009-08-19T20:16:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="896" xml:space="preserve">==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>1d44f8fc6e0aa20bbd01160ac5327b0d5ec6fb25</sha1>
  </revision>
  <revision>
    <id>1084</id>
    <parentid>1057</parentid>
    <timestamp>2009-08-28T17:24:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Alan Renouf's last 10 VMs created and removed one liner</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1021" xml:space="preserve">==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]

* [http://www.virtu-al.net/2009/08/27/powercli-one-liners-last-10-vms-created-and-removed/ Last 10 VMs created and removed]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>32dc8914a7f7fd8f7ed68091ba8a53c115e6ffe3</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Oneliners</title>
  <ns>0</ns>
  <id>463</id>
  <revision>
    <id>1058</id>
    <parentid>1051</parentid>
    <timestamp>2009-08-19T20:22:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Oneliners have been split up leave these links here for easy reference</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="808" xml:space="preserve">==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]

[[Category: PowerCLI]]</text>
    <sha1>ab9c88f46de936160f6d3760a95e837339f30a94</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>1059</id>
    <parentid>1042</parentid>
    <timestamp>2009-08-19T20:26:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Reshuffle links in order</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4923" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>322e4242078574cb8ab87c8bd66867c28fb10cf7</sha1>
  </revision>
  <revision>
    <id>1060</id>
    <parentid>1059</parentid>
    <timestamp>2009-08-19T20:32:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4968" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>19ef9b034928ff42d7b2f0154c220c4431498b61</sha1>
  </revision>
  <revision>
    <id>1062</id>
    <parentid>1060</parentid>
    <timestamp>2009-08-19T20:42:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Link to nivot configurable Script logger module, thanks Hal for pointing it out</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5130" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>0fe3b8fcd485b86dff04240e0c76d5712dfe7239</sha1>
  </revision>
  <revision>
    <id>1067</id>
    <parentid>1062</parentid>
    <timestamp>2009-08-21T14:28:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5184" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>e368938556cab427c3b042c8632e8d85046e7f31</sha1>
  </revision>
  <revision>
    <id>1070</id>
    <parentid>1067</parentid>
    <timestamp>2009-08-21T14:42:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Link to idera free SQL Server powershell scripts, thanks to Hal Rottenberg for mentioning them</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5285" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>6926d5023d95046a6d0e6dfda4f5f54060512e48</sha1>
  </revision>
  <revision>
    <id>1071</id>
    <parentid>1070</parentid>
    <timestamp>2009-08-22T12:46:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added link to Blue Gears: Power Shell-ism's Tales from a Linux Developer</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5385" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>757ed3df5414f11009d37f1244e9835d0d53a07a</sha1>
  </revision>
  <revision>
    <id>1082</id>
    <parentid>1071</parentid>
    <timestamp>2009-08-28T17:08:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5446" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>08e5c4e04e0ae651a06f54852bc3be06c7d8d461</sha1>
  </revision>
  <revision>
    <id>1087</id>
    <parentid>1082</parentid>
    <timestamp>2009-08-28T18:01:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5488" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>196034d5671a2b9d28b9fa349b337789e5365e40</sha1>
  </revision>
  <revision>
    <id>1089</id>
    <parentid>1087</parentid>
    <timestamp>2009-08-28T18:28:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5563" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>b2a9202ba9c6d4986dd652ef4b586e9994b13df5</sha1>
  </revision>
  <revision>
    <id>1091</id>
    <parentid>1089</parentid>
    <timestamp>2009-08-29T19:32:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5602" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>a8fc354a84804267e2e75e9f291b5c7a449c8e3f</sha1>
  </revision>
  <revision>
    <id>1095</id>
    <parentid>1091</parentid>
    <timestamp>2009-09-08T12:40:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5647" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>592eced41bff8141221665c56795c5ccd6119de7</sha1>
  </revision>
  <revision>
    <id>1097</id>
    <parentid>1095</parentid>
    <timestamp>2009-09-15T18:51:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to Parsing powershell scripts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5779" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== Scripts on other locations ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>d400ce322bbfa7acc4cf9dc9e83372099816d3a6</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Set CPU Identification Mask</title>
  <ns>0</ns>
  <id>496</id>
  <revision>
    <id>1061</id>
    <timestamp>2009-08-19T20:38:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Arne Fokkema's Set CPU Identification mask script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="503" xml:space="preserve">=== Mask-Extensions ===
author: Arne Fokkema
==== Description ====
Allows you to set the CPU Identification Mask on Multiple VM’s. 

==== Usage: ====
If you want to run this function for VM called "My VM", then you can run the following command:
 Mask-Extensions (get-vm "My VM")
or to change all your VM's, use the pipeline:
 get-vm | % {Mask-Extensions ($_)}

==== Location ====
http://ict-freak.nl/2009/08/19/powercli-set-cpu-identification-mask/

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>ce9cc7fd09cb452e6c60ff94c878fd184f739a02</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Perl</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>1064</id>
    <parentid>1037</parentid>
    <timestamp>2009-08-19T22:13:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="261" xml:space="preserve">[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]

[[Listing all VM's in a cluster]]

[[Category: Perl]]</text>
    <sha1>750800075c98752f9ae2a1a554473fbd0eb7c563</sha1>
  </revision>
  <revision>
    <id>1076</id>
    <parentid>1064</parentid>
    <timestamp>2009-08-24T18:47:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="297" xml:space="preserve">[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]

[[Listing all VM's in a cluster]]

[[Rename local storage datastore]]

[[Category: Perl]]</text>
    <sha1>d721ac2ed156ef314b65014f5ce985f332eab78e</sha1>
  </revision>
  <revision>
    <id>1093</id>
    <parentid>1076</parentid>
    <timestamp>2009-08-29T19:41:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="324" xml:space="preserve">[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]

[[Listing all VM's in a cluster]]

[[Rename local storage datastore]]

[[Factory Reset of ESXi]]

[[Category: Perl]]</text>
    <sha1>f6c29c7a6357861b6981d4408019995ee11b866f</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Listing all VM's in a cluster</title>
  <ns>0</ns>
  <id>497</id>
  <revision>
    <id>1065</id>
    <timestamp>2009-08-19T22:20:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Listing all VM's in a cluster from Richard Garsthagen's web site</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="591" xml:space="preserve">=== vms_list_cluster.pl ===
author: Jeremy van Doorn
==== Description ====
Allows you to retrieve the names of the hosts, number and name of virtual machines in cluster.

==== Usage: ====
Change the following login information in the script to match your environment.
 my $username = "vmware";
 
 my $password = "vi3demo";

 my $service_url = "https://172.28.1.250/sdk/vimService";


 my $cluster_name = "ESX Cluster";

Then run it like this:
 [vi-admin@]$ ./vms_list_cluster.pl

==== Location ====

http://www.run-virtual.com/?page_id=182

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>ebd91f986496712fc45f2b68f6453fee6a831069</sha1>
  </revision>
  <revision>
    <id>1066</id>
    <parentid>1065</parentid>
    <timestamp>2009-08-19T22:20:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="588" xml:space="preserve">=== vms_list_cluster.pl ===
author: Jeremy van Doorn
==== Description ====
Allows you to retrieve the names of the hosts, number and name of virtual machines in cluster.

==== Usage: ====
Change the following login information in the script to match your environment.
  my $username = "vmware";
  my $password = "vi3demo";
  my $service_url = "https://172.28.1.250/sdk/vimService";
  my $cluster_name = "ESX Cluster";

Then run it like this:
 [vi-admin@]$ ./vms_list_cluster.pl

==== Location ====

http://www.run-virtual.com/?page_id=182

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>06ef1a6a5a9336af03de2b58f65a1ab27c95031c</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Get number of vCPU's used in cluster</title>
  <ns>0</ns>
  <id>498</id>
  <revision>
    <id>1068</id>
    <timestamp>2009-08-21T14:36:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Alan's version of William's getNumofvCPUInCluster.pl script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="888" xml:space="preserve">===  Get number of vCPU's used in a cluster ===
author: Alan Renouf
==== Description ====
Based on the [[Get_number_of_vCPU%27s_used_in_cluster| getNumofvCPUInCluster.pl script from William Lam]], Alan wrote the Powershell variant.

Allows you to retrieve the number of vCPU's used in the cluster you provide as a parameter.

==== Output: ====
 Cluster: Production
 Host: vmgesx01.vmguru.com
 Misc.RunningVCpuLimit: 128
 Number of vCPU on host: 4
 Host: vmgesx02.vmguru.com
 Misc.RunningVCpuLimit: 128
 Number of vCPU on host: 3
 Host: vmgesx03.vmguru.com
 Misc.RunningVCpuLimit: 128
 Number of vCPU on host: 2
 Host: vmgesx04.vmguru.com
 Misc.RunningVCpuLimit: 128
 Number of vCPU on host: 5 
 ———-
 Number of vCPU in Production: 14

==== Location ====

http://www.virtu-al.net/2009/08/20/powercli-number-of-vcpus-in-a-cluster/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>a27b67dfa81397b9e556fc27eb4965c2b93eccf6</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>1072</id>
    <parentid>969</parentid>
    <timestamp>2009-08-22T12:49:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2926" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]

[[Performing emergency shut down of VM's on ESX]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

[[APC/APCUPSD ESX/ESXi Host shutdown script]]

==== Perl scripts ====
[[Recover vmx from log file]]

==== AppleScript ====

[http://communities.vmware.com/thread/122793 AppleScript to Run Virtual Machine and switch to Full Screen View or Unity View at Login]

==== Javascript ====
[[Ghetto vCenter 4.0 Unattended Installer]]</text>
    <sha1>85c76bbd65f11c62808b0622386c51fdb8adefa3</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Performing emergency shut down of VM's on ESX</title>
  <ns>0</ns>
  <id>499</id>
  <revision>
    <id>1073</id>
    <timestamp>2009-08-22T12:54:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added VMware kb 1007934 Performing an emergency shutdown of all powered-on virtual machines on an ESX host</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="554" xml:space="preserve">=== Emergency shut down of all VM's on a host ===
author: VMware
==== Description ====
Gives you the possibility to quickly and cleanly shut down all the VMs on your host with only console access.

==== Script: ====
Run the following with root privileges:
 cat /proc/vmware/vm/*/names | awk -F= '{a=substr($4,$1,length($4)-6); b="vmware-cmd "a" getstate"; print b; system(b); c="vmware-cmd "a" stop"; system(c); } END { print "Number of Machines: "NR;}'

==== Location ====

http://kb.vmware.com/kb/1007934

[[Category: Bash]] [[Category: VM Management]]</text>
    <sha1>6d1065c7a5222689f341650fe37f5c778021c8c1</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Daily Report</title>
  <ns>0</ns>
  <id>479</id>
  <revision>
    <id>1075</id>
    <parentid>991</parentid>
    <timestamp>2009-08-24T18:42:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added Alan's updates to the daily reports, have a look over at his site for what has changed</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="906" xml:space="preserve">Alan has written a script that you can schedule to run each day and have it report to you by email the most vital information about your virtual infrastructure.

Items that are currently part of the daily report are:
* Host statistics
* Open snapshots
* Data storage usage
* Virtual Machines create history
* Virtual Machines delete history
* Virtual Center events
* VMware Tools install details
* Any Windows events from the Virtual center server which are related to VMware
* Any VMs which have CD-Rom or Floppy Drive’s connected
* Any hosts in Maintenance Mode
* Any Hosts in a disconnected state

read more:

http://www.virtu-al.net/2009/07/14/powercli-daily-report/

[http://www.virtu-al.net/2009/08/20/daily-report-iphone-version/ Virtu-al.net: Daily Report iPhone Version]

[http://www.virtu-al.net/2009/08/18/powercli-daily-report-v2/ Virtu-al.net: Daily Report Version 2]

[[Category: PowerCLI]]</text>
    <sha1>829ca4e6204770840e7d76000cdd296a9b7c73fb</sha1>
  </revision>
  <revision>
    <id>1098</id>
    <parentid>1075</parentid>
    <timestamp>2009-09-21T08:47:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to Daily Report in Tiddlywiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1025" xml:space="preserve">Alan has written a script that you can schedule to run each day and have it report to you by email the most vital information about your virtual infrastructure.

Items that are currently part of the daily report are:
* Host statistics
* Open snapshots
* Data storage usage
* Virtual Machines create history
* Virtual Machines delete history
* Virtual Center events
* VMware Tools install details
* Any Windows events from the Virtual center server which are related to VMware
* Any VMs which have CD-Rom or Floppy Drive’s connected
* Any hosts in Maintenance Mode
* Any Hosts in a disconnected state

read more:

http://www.virtu-al.net/2009/07/14/powercli-daily-report/

[http://www.virtu-al.net/2009/08/20/daily-report-iphone-version/ Virtu-al.net: Daily Report iPhone Version]

[http://www.virtu-al.net/2009/08/18/powercli-daily-report-v2/ Virtu-al.net: Daily Report Version 2]

[http://blog.unclephil.net/post/2009/09/20/Quick-win-combination Daily Report and Healthcheck embedded in Tiddlywiki]

[[Category: PowerCLI]]</text>
    <sha1>cffa28461260a1689a31970b4d2743e249289bc9</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Rename local storage datastore</title>
  <ns>0</ns>
  <id>500</id>
  <revision>
    <id>1077</id>
    <timestamp>2009-08-24T18:58:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added William Lam's rename local storage datastore perl script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1065" xml:space="preserve">=== renameLocalStorageDatastore.pl ===
author: William Lam
==== Description ====
Allows you to rename the name of the local storage datastore in your vCenter so that it has a unique name.
The script comes with a test mode so that you can see how the output looks like before you run the actual renaming action.

==== Usage: ====
 [vi-admin@optimus]$ ./renameLocalStorageDatastore.pl --server teletron1.primp-industries.com --username primp --cluster autobots --jk_mode 0
 This could take a few minutes depending on the size of the cluster ...
 
 Cluster: autobots
 
 	Host: sideswipe.primp-industries.com
 		Localstorage: local-storage (2)
  		Rename to: [sideswipe-local-storage-1]
 	Total # of local datastores on host: 1

 	Host: jetfire.primp-industries.com
 		Localstorage: local-storage
 		Rename to: [jetfire-local-storage-1]
 		Localstorage: local-storage (1)
 		Rename to: [jetfire-local-storage-2]
 	Total # of local datastores on host: 2
 
==== Location ====

http://communities.vmware.com/docs/DOC-10571

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>501c2b9ffb189d8f31a6a20e626a8efbd9b76ab6</sha1>
  </revision>
  <revision>
    <id>1078</id>
    <parentid>1077</parentid>
    <timestamp>2009-08-24T18:59:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1066" xml:space="preserve">=== renameLocalStorageDatastore.pl ===
author: William Lam
==== Description ====
Allows you to rename the name of the local storage datastore in your vCenter so that it has a unique name.
The script comes with a test mode so that you can see how the output looks like before you run the actual renaming action.

==== Usage: ====
 [vi-admin@optimus]$ ./renameLocalStorageDatastore.pl --server teletron1.primp-industries.com --username primp --cluster autobots --jk_mode 0
 This could take a few minutes depending on the size of the cluster ...
 
 Cluster: autobots
 
 	Host: sideswipe.primp-industries.com
 		Localstorage: local-storage (2)
  		Rename to: [sideswipe-local-storage-1]
 	Total # of local datastores on host: 1
 
 	Host: jetfire.primp-industries.com
 		Localstorage: local-storage
 		Rename to: [jetfire-local-storage-1]
 		Localstorage: local-storage (1)
 		Rename to: [jetfire-local-storage-2]
 	Total # of local datastores on host: 2
 
==== Location ====

http://communities.vmware.com/docs/DOC-10571

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>ad2a2d3b1715e578e57f969c50b6c8a984d98f0c</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>1079</id>
    <parentid>1012</parentid>
    <timestamp>2009-08-24T19:07:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2348" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* Add daily backup to another machine
* Add proper category pages. Partly done
* Add "what's new" to the main page
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* Fix theme template / settings so that we can edit per paragraph as well
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* &lt;s&gt;Find a better way to present what's available on the site, improve ways to restructure the data. &lt;/s&gt; The support for category tree at the main page now gives a much easier way to navigate the site. But it never hurts to find better ways as this doesn't scale too well (look at the vimsh category for example)
* Improve main page
* Add example code
* &lt;s&gt;Add a theme for mobile phones, so it is easier to read the content&lt;/s&gt; Still needs to be spruced up a bit with a custom CSS file.

==== Things to make our mind up about ====

* Does the site need a forum? &lt;- No, you can use the talk page if you have a comment or contact me directly. Maybe in a later incarnation.
* Does the site need an instant messager type of control ? &lt;- No, use twitter @wilva for contacting me or use email wila under the site's domain name.
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ? &lt;- No, we don't host much code on the site right now. Pretty much all of the code snippets are located elsewhere and copying those over to this site makes no sense as it will only complicate things.
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ? Probably ;)

[[Category: website]]</text>
    <sha1>350f550464dcf44b809b3aad3aae464f71eb6cb5</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Force a VM to enter BIOS setup on next boot</title>
  <ns>0</ns>
  <id>501</id>
  <revision>
    <id>1083</id>
    <timestamp>2009-08-28T17:14:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added force VM to reboot into BIOS setup PowerCLI filter from Shay Levy</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="718" xml:space="preserve">=== Set-VMBIOSSetup ===
author: Shay Levy
==== Description ====
A filter to programmatically set the vmx-configuration property so that the VM will boot into the BIOS setup screen on the next reboot. 

==== Usage: ====
 ## Get all VMs which name starts with XP, force the VM to enter into bios
 ## mode on next boot and write VM objects back to pipeline
 Get-VM XP* | Set-VMBIOSSetup -PassThru
 
 # Get all VMs which name starts with XP and disable (uncheck) bios mode on next boot
 Get-VM XP* | Set-VMBIOSSetup -Disable

==== Location ====
http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/08/27/force-a-vm-to-enter-bios-setup-screen-on-next-reboot.aspx

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>ca24cb28f3e3239ad48bba354829b17da0eec7c1</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Virtualisation technical articles</title>
  <ns>0</ns>
  <id>412</id>
  <revision>
    <id>1085</id>
    <parentid>1025</parentid>
    <timestamp>2009-08-28T17:55:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added Eric Sloof's eavesdrop article and Carter Shanklin's link to Onyx on youtube</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1488" xml:space="preserve">This page contains links to technical articles about virtualisation technology.
It's a sort of fancy bookmark of what I consider interesting reading as a programmer... this is not likely to be interesting for everyone ;)

* [http://www.codeproject.com/KB/debug/cdbntsd6.aspx Navigating the kernel debugger]
This tutorial covers a few of the basic features of the kernel debugger and has some tips on getting used to using it. 

* [http://www.ddj.com/cpp/184402033 Sharing memory with the virtual machine]
Tricks on sharing data between guest OS instances and the host. 

* [http://www.codeplex.com/visa/Wiki/View.aspx?title=English%20version&amp;referringTitle=Home Virtualisation Instruction Set Architecture]
MIPS R3000 processor model, available at ArchC was extended to offer virtualisation support, adding instructions and structures inspired by Intel VT-x.

* [http://www.visophyte.org/blog/2009/08/03/using-vmware-recordreplay-and-vprobes-for-low-time-distortion-performance-profiling/ Using VMWare Record/Replay and VProbes for low time-distortion performance profiling]
Advanced article on how-to use VMware for your application performance profiling.

* [http://www.ntpro.nl/blog/archives/918-Eavesdrop-your-VI-Client-traffic.html NTPRO.nl Eavesdrop your VI Client traffic] 
Eric Sloof shows you a trick here on how-to display the soap trafffic send over the wire by the VI-Client. See also [http://www.youtube.com/watch?v=6ab_tMI2a8Y project Onyx from VMware] for another approach.</text>
    <sha1>74d295454af176a415c3ad1582e146c839c78d30</sha1>
  </revision>
  <revision>
    <id>1086</id>
    <parentid>1085</parentid>
    <timestamp>2009-08-28T17:56:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1487" xml:space="preserve">This page contains links to technical articles about virtualisation technology.
It's a sort of fancy bookmark of what I consider interesting reading as a programmer... this is not likely to be interesting for everyone ;)

* [http://www.codeproject.com/KB/debug/cdbntsd6.aspx Navigating the kernel debugger]
This tutorial covers a few of the basic features of the kernel debugger and has some tips on getting used to using it. 

* [http://www.ddj.com/cpp/184402033 Sharing memory with the virtual machine]
Tricks on sharing data between guest OS instances and the host. 

* [http://www.codeplex.com/visa/Wiki/View.aspx?title=English%20version&amp;referringTitle=Home Virtualisation Instruction Set Architecture]
MIPS R3000 processor model, available at ArchC was extended to offer virtualisation support, adding instructions and structures inspired by Intel VT-x.

* [http://www.visophyte.org/blog/2009/08/03/using-vmware-recordreplay-and-vprobes-for-low-time-distortion-performance-profiling/ Using VMWare Record/Replay and VProbes for low time-distortion performance profiling]
Advanced article on how-to use VMware for your application performance profiling.

* [http://www.ntpro.nl/blog/archives/918-Eavesdrop-your-VI-Client-traffic.html NTPRO.nl Eavesdrop your VI Client traffic] 
Eric Sloof shows you a trick here on how-to display the soap traffic send over the wire by the VI-Client. See also [http://www.youtube.com/watch?v=6ab_tMI2a8Y project Onyx from VMware] for another approach.</text>
    <sha1>84a3511765be24cd2f203f9910c0f1cfbc9f301d</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Set VM Snapshot location</title>
  <ns>0</ns>
  <id>502</id>
  <revision>
    <id>1088</id>
    <timestamp>2009-08-28T18:07:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added the script to set the Snapshot location by Hugo Peeters</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="978" xml:space="preserve">=== Set-VMSnapshotLocation ===
author: Hugo Peeters
==== Description ====
This powershell function allows you to setup an alternative location for storing the snapshots of your VM's. 
It will help you to protect your production LUN to run out of storage without having to oversize it for massive snapshots.

==== Usage: ====
First, connect to a virtual server server (Connect-VIServer)

Set snapshot location for one vm (folder must already exist on datastore):
 Set-VMSnapshotLocation -vm VM001 -Location "[BigAssDatastore] Snapshots"

For all vms at once (no folder specified will put all in the root of the datastore):
 Get-VM | ForEach-Object {Set-VMSnapshotLocation -vm $_ -Location "[BigAssDatastore]"}

Reset the location to the original location (with the vmx file):
 Set-VMSnapshotLocation -vm VM001 -Reset

==== Location ====
http://www.peetersonline.nl/index.php/vmware/set-vmware-snapshot-location-with-powershell/

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>40a599fc869fb3f041cd4dfc80e0f5f0d78c9c66</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Resolving improper memory limits on your virtual machines</title>
  <ns>0</ns>
  <id>503</id>
  <revision>
    <id>1090</id>
    <timestamp>2009-08-28T18:36:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added memory limit resolve problem script from Scott Herold</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="835" xml:space="preserve">=== QueryMem.ps1 ===
author: Scott Herold
==== Description ====
An interactive scripts that allows you to query VM's for possible memory limit configuration errors and helps you to resolve these problems.
==== Usage: ====
Query Resource Allocations:
 QueryMem.ps1 -VMHost server1.domain.com -User administrator -Password passw0rd -Action query

Idenfity Potential Misconfigurations:
 QueryMem.ps1 -VMHost server1.domain.com -User administrator -Password passw0rd -Action id

Modify Misconfigured VMs:
 QueryMem.ps1 -VMHost server1.domain.com -User administrator -Password passw0rd -Action resolve `
                        -vm vm1, vm2, vm3
==== Location ====
http://www.vmguru.com/index.php/articles-mainmenu-62/scripting/98-resolving-improper-memory-limits-on-your-virtual-machines

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>871178d8f34262a9f3a770ae50d88e5da80e5255</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Factory reset of ESXi</title>
  <ns>0</ns>
  <id>504</id>
  <revision>
    <id>1092</id>
    <timestamp>2009-08-29T19:38:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Mike Laverick's Reset ESXi host script from his PowersHell series</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="437" xml:space="preserve">===  RTFM: Factory reset of ESXi ===
author: Mike Laverick
==== Description ====
Mike wrote a little script so you can reset your host to the factory defaults by running the script.
This is very convenient for test hosts so you can focus on the problem at hand.

==== Usage ====
Adjust the host details in the script on his page.

==== Location ====

http://www.rtfm-ed.co.uk/?p=1671

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>d494c317eeea14534db56ead9ae9c68a09731253</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Factory Reset of ESXi</title>
  <ns>0</ns>
  <id>505</id>
  <revision>
    <id>1094</id>
    <timestamp>2009-08-29T19:47:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>William Lam's version of the Reset to factory settings script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="854" xml:space="preserve">===  factoryResetESXi.pl ===
author: William Lam
==== Description ====
Based on Mike's [[PowerCLI: Factory reset of ESXi]], William wrote a perl version of the script so you can reset your host to the factory defaults by running it.

==== Usage ====
 [vi-admin@scofield ~]$ ./factoryResetESXi.pl --server reflex.primp-industries.com --username primp --vihost kang.primp-industries.com
 Enter password:
 "kang.primp-industries.com" is entering maintenance mode ...
         "kang.primp-industries.com" has successfully entered maintenance mode!
 Removing "kang.primp-industries.com" from vCenter ...
         "kang.primp-industries.com" has successfully been remove from vCenter!
 Resetting factory settings on "kang.primp-industries.com"!

==== Location ====

http://communities.vmware.com/docs/DOC-10651

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>2ee4514c53ab91dba155a7266ef65b114a266078</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>PowerCLI: Scripted edit of a VMX file</title>
  <ns>0</ns>
  <id>506</id>
  <revision>
    <id>1096</id>
    <timestamp>2009-09-08T12:46:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Scripted edit of VMX file by Craig Baltzer</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="949" xml:space="preserve">===  Scripted edit of a VMX file ===
author: Craig Baltzer
==== Description ====
Craig shows here how you can adjust keys and values in a scripted manner for the hardware configuration of your virtual machine.

==== Code ====
  $vm = Get-View (Get-VM +NameofVMtoUpdate+).ID
  $vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec
  $vmConfigSpec.extraconfig += New-Object VMware.Vim.optionvalue
  $vmConfigSpec.extraconfig[0].Key="lefthandsideofentry"
  $vmConfigSpec.extraconfig[0].Value="rigthhandsideofentry"
  $vm.ReconfigVM($vmConfigSpec)

Where

* NameofVMtoUpdate is the name of the VM you want to update (from the vCenter inventory)
* lefthandsideofentry is the advanced configuration entry you want to set
* rigthhandsideofentry is the value for the advanced configuration entry

==== Location ====

[http://communities.vmware.com/thread/189302 VMTN: Scripted edit of a VMX file]

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>3513fb7cae68c9b3b1a0c1bc9fe46a9d137164f6</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Vmkdump</title>
  <ns>0</ns>
  <id>483</id>
  <revision>
    <id>1099</id>
    <parentid>1011</parentid>
    <timestamp>2009-09-23T06:58:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to PSOD KB article</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2942" xml:space="preserve"> NAME
      vmkdump - VMkernel dumper
 
 SYNOPSIS
      vmkdump OPTIONS
 
 COPYRIGHT
     VMware ESX Server is Copyright 2004-2007 VMware, Inc.  All rights reserved.
 
 DESCRIPTION
      vmkdump manages the VMkernel dump partition.

==== Usage ====
      vmkdump -d --devname /dev/&lt;Linux device name&gt;
              -z --zdumpname outputName (optional)
              -n --newonly (optional)
              -s --slot slotnum (optional)
   Extract the log from a compressed dump:
      vmkdump -l --log zdumpname


==== OPTIONS ====
     -d, --devname deviceName
         Specify the Linux console device that should be used to read the  VMkernel dump.  
         Note: This option should not be used after the dump  partition has been set with the -p option.  
         If the partition has been set, you need to stop and reset the VMkernel before using this option.
 
     -n, --newonly
         For each VMkernel dump that is produced, a count is kept of the number of times the compressed 
         dump file has been read off the dump partition.  When this option is specified, the compressed 
         dump will only be read off the dump partition if the read count is zero.
 
     -z, --zdumpname compressedFileName
         When reading from the dump partition, this option specifies the name of the file to create with 
         the compressed dump.  By default the name is vmkernel-zdump.#, where # is a unique number.
 
     -s, --slot slotnum
         On dump partitions that reside on shared storage, multiple machines  can share the dump partition.  
         Because of this, the dump partition is split up into multiple slots.  Generally, when retrieving a 
         core dump, the physical machine's UUID is hashed into a slot number based on the total number 
         of slots, and the compressed dump is automatically read from that slot.  
 
         However, there may be situations where the machine that dumped core is no longer able to retrieve 
         core  dumps.  In those cases, this option can be used to override the normal UUID hash algorithm 
         for determining a slot.  Note that the slot used during a core dump will be displayed on the PSOD.
  
     -l, --log compressedFileName
        Extracts the vmkernel log from the specified compressed dump file.


==== Examples ====
* Specify linux device to read the dump
 #vmkdump -d /dev/sda5

Creates a file name vmkernel-zdump. # contained a compressed dump. # is 1 if no other compressed dumps are in the current directory, otherwise # is the lowest unused integer (ie, if up to vmkernel-zdump.5 exist, then it would create vmkernel-zdump.6).


* Extract the zdump from the dump partition
 
 #vmkdump -d /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:2
 
 singleslot coredump
 
 
 created file vmkernel-zdump.1

==== Links ====
[http://kb.vmware.com/kb/1005184 Decoding Machine Check Exception (MCE) output after a purple screen (PSOD) error]

[[Category: CLI]]</text>
    <sha1>0b1b057fa9fe8f296af89a8ea4bb82844b215823</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Vmkerrcode</title>
  <ns>0</ns>
  <id>417</id>
  <revision>
    <id>1100</id>
    <parentid>870</parentid>
    <timestamp>2009-09-23T07:00:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to PSOD KB article</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25086" xml:space="preserve">==== vmkerrcode ====
Usage: 
 vmkerrcode [-l] [error code (hex or decimal)]
    -l list all error codes

This can be used in order to decode the error

==== Example output ====
 # vmkerrcode -l
 
 VMK_ReturnStatus table for VMware ESX Server, Build #130756
 Name                             Dec         Hex          errno equiv    Description                                                 
 -------------------------------------------------------------------------------
 VMK_OK                           0           0            OK            Success
 VMK_FAILURE                      195887105   0xbad0001    EINVAL        Failure
 VMK_WOULD_BLOCK                  195887106   0xbad0002    EAGAIN        Would block
 VMK_NOT_FOUND                    195887107   0xbad0003    ENOENT        Not found
 VMK_BUSY                         195887108   0xbad0004    EBUSY         Busy
 VMK_EXISTS                       195887109   0xbad0005    EEXIST        Already exists
 VMK_LIMIT_EXCEEDED               195887110   0xbad0006    EFBIG         Limit exceeded
 VMK_BAD_PARAM                    195887111   0xbad0007    EINVAL        Bad parameter
 VMK_METADATA_READ_ERROR          195887112   0xbad0008    EIO           Metadata read error
 VMK_METADATA_WRITE_ERROR         195887113   0xbad0009    EIO           Metadata write error
 VMK_IO_ERROR                     195887114   0xbad000a    EIO           I/O error
 VMK_READ_ERROR                   195887115   0xbad000b    EIO           Read error
 VMK_WRITE_ERROR                  195887116   0xbad000c    EIO           Write error
 VMK_INVALID_NAME                 195887117   0xbad000d    ENAMETOOLONG  Invalid name
 VMK_INVALID_HANDLE               195887118   0xbad000e    EBADF         Invalid handle
 VMK_INVALID_ADAPTER              195887119   0xbad000f    ENODEV        No such SCSI adapter
 VMK_INVALID_TARGET               195887120   0xbad0010    ENODEV        No such target on adapter
 VMK_INVALID_PARTITION            195887121   0xbad0011    ENXIO         No such partition on target
 VMK_INVALID_FS                   195887122   0xbad0012    ENXIO         No filesystem on the device
 VMK_INVALID_MEMMAP               195887123   0xbad0013    EFAULT        Memory map mismatch
 VMK_NO_MEMORY                    195887124   0xbad0014    ENOMEM        Out of memory
 VMK_NO_MEMORY_RETRY              195887125   0xbad0015    ENOMEM        Out of memory (ok to retry)
 VMK_NO_RESOURCES                 195887126   0xbad0016    ENOMEM        Out of resources
 VMK_NO_FREE_HANDLES              195887127   0xbad0017    EMFILE        No free handles
 VMK_NUM_HANDLES_EXCEEDED         195887128   0xbad0018    ENFILE        Exceeded maximum number of allowed handles
 VMK_DEPRECATED_NO_FREE_PTR_BLOCKS195887129   0xbad0019    ENOSPC        No free pointer blocks (deprecated)
 VMK_DEPRECATED_NO_FREE_DATA_BLOCKS195887130   0xbad001a    ENOSPC        No free data blocks (deprecated)
 VMK_CORRUPT_REDOLOG              195887131   0xbad001b    EBADF         Corrupt RedoLog
 VMK_STATUS_PENDING               195887132   0xbad001c    EAGAIN        Status pending
 VMK_STATUS_FREE                  195887133   0xbad001d    EAGAIN        Status free
 VMK_UNSUPPORTED_CPU              195887134   0xbad001e    ENODEV        Unsupported CPU
 VMK_NOT_SUPPORTED                195887135   0xbad001f    ENOSYS        Not supported
 VMK_TIMEOUT                      195887136   0xbad0020    ETIMEDOUT     Timeout
 VMK_READ_ONLY                    195887137   0xbad0021    EROFS         Read only
 VMK_RESERVATION_CONFLICT         195887138   0xbad0022    EAGAIN        SCSI reservation conflict
 VMK_FS_LOCKED                    195887139   0xbad0023    EADDRINUSE    File system locked
 VMK_NOT_ENOUGH_SLOTS             195887140   0xbad0024    ENFILE        Out of slots
 VMK_INVALID_ADDRESS              195887141   0xbad0025    EFAULT        Invalid address
 VMK_NOT_SHARED                   195887142   0xbad0026    ENOMEM        Not shared
 VMK_SHARED                       195887143   0xbad0027    ENOMEM        Page is shared
 VMK_KSEG_PAIR_FLUSHED            195887144   0xbad0028    ENOMEM        Kseg pair flushed
 VMK_MAX_ASYNCIO_PENDING          195887145   0xbad0029    ENOMEM        Max async I/O requests pending
 VMK_VERSION_MISMATCH_MINOR       195887146   0xbad002a    ENOSYS        Minor version mismatch
 VMK_VERSION_MISMATCH_MAJOR       195887147   0xbad002b    ENOSYS        Major version mismatch
 VMK_IS_CONNECTED                 195887148   0xbad002c    EINVAL        Already connected
 VMK_IS_DISCONNECTED              195887149   0xbad002d    ENOTCONN      Already disconnected
 VMK_IS_ENABLED                   195887150   0xbad002e    EINVAL        Already enabled
 VMK_IS_DISABLED                  195887151   0xbad002f    EINVAL        Already disabled
 VMK_NOT_INITIALIZED              195887152   0xbad0030    EINVAL        Not initialized
 VMK_WAIT_INTERRUPTED             195887153   0xbad0031    EINTR         Wait interrupted
 VMK_NAME_TOO_LONG                195887154   0xbad0032    ENAMETOOLONG  Name too long
 VMK_MISSING_FS_PES               195887155   0xbad0033    ENOTDIR       VMFS volume missing physical extents
 VMK_NICTEAMING_VALID_MASTER      195887156   0xbad0034    EINVAL        NIC teaming master valid
 VMK_NICTEAMING_SLAVE             195887157   0xbad0035    EEXIST        NIC teaming slave
 VMK_NICTEAMING_REGULAR_VMNIC     195887158   0xbad0036    EINVAL        NIC teaming regular VMNIC
 VMK_ABORT_NOT_RUNNING            195887159   0xbad0037    ECANCELED     Abort not running
 VMK_NOT_READY                    195887160   0xbad0038    EIO           Not ready
 VMK_CHECKSUM_MISMATCH            195887161   0xbad0039    EIO           Checksum mismatch
 VMK_VLAN_NO_HW_ACCEL             195887162   0xbad003a    EINVAL        VLan HW Acceleration not supported
 VMK_NO_VLAN_SUPPORT              195887163   0xbad003b    EOPNOTSUPP    VLan is not supported in vmkernel
 VMK_NOT_VLAN_HANDLE              195887164   0xbad003c    EINVAL        Not a VLan handle
 VMK_BAD_VLANID                   195887165   0xbad003d    EBADF         Couldn't retrieve VLan id
 VMK_MIG_PROTO_ERROR              195887166   0xbad003e    EINVAL        Migration protocol error
 VMK_NO_CONNECT                   195887167   0xbad003f    EIO           No connection
 VMK_SEGMENT_OVERLAP              195887168   0xbad0040    EINVAL        Segment overlap
 VMK_BAD_MPS                      195887169   0xbad0041    EIO           Error parsing MPS Table
 VMK_BAD_ACPI                     195887170   0xbad0042    EIO           Error parsing ACPI Table
 VMK_RESUME_ERROR                 195887171   0xbad0043    EIO           Failed to resume VM
 VMK_NO_ADDRESS_SPACE             195887172   0xbad0044    ENOMEM        Insufficient address space for operation
 VMK_BAD_ADDR_RANGE               195887173   0xbad0045    EINVAL        Bad address range
 VMK_ENETDOWN                     195887174   0xbad0046    ENETDOWN      Network is down
 VMK_ENETUNREACH                  195887175   0xbad0047    ENETUNREACH   Network unreachable
 VMK_ENETRESET                    195887176   0xbad0048    ENETRESET     Network dropped connection on reset
 VMK_ECONNABORTED                 195887177   0xbad0049    ECONNABORTED  Software caused connection abort
 VMK_ECONNRESET                   195887178   0xbad004a    ECONNRESET    Connection reset by peer
 VMK_ENOTCONN                     195887179   0xbad004b    ENOTCONN      Socket is not connected
 VMK_ESHUTDOWN                    195887180   0xbad004c    ESHUTDOWN     Can't send after socket shutdown
 VMK_ETOOMANYREFS                 195887181   0xbad004d    ETOOMANYREFS  Too many references: can't splice
 VMK_ECONNREFUSED                 195887182   0xbad004e    ECONNREFUSED  Connection refused
 VMK_EHOSTDOWN                    195887183   0xbad004f    EHOSTDOWN     Host is down
 VMK_EHOSTUNREACH                 195887184   0xbad0050    EHOSTUNREACH  No route to host
 VMK_EADDRINUSE                   195887185   0xbad0051    EADDRINUSE    Address already in use
 VMK_BROKEN_PIPE                  195887186   0xbad0052    EPIPE         Broken pipe
 VMK_NOT_A_DIRECTORY              195887187   0xbad0053    ENOTDIR       Not a directory
 VMK_IS_A_DIRECTORY               195887188   0xbad0054    EISDIR        Is a directory
 VMK_NOT_EMPTY                    195887189   0xbad0055    ENOTEMPTY     Directory not empty
 VMK_NOT_IMPLEMENTED              195887190   0xbad0056    ENOSYS        Not implemented
 VMK_NO_SIGNAL_HANDLER            195887191   0xbad0057    EINVAL        No signal handler
 VMK_FATAL_SIGNAL_BLOCKED         195887192   0xbad0058    EINVAL        Fatal signal blocked
 VMK_NO_ACCESS                    195887193   0xbad0059    EACCES        Permission denied
 VMK_NO_PERMISSION                195887194   0xbad005a    EPERM         Operation not permitted
 VMK_UNDEFINED_SYSCALL            195887195   0xbad005b    ENOSYS        Undefined syscall
 VMK_RESULT_TOO_LARGE             195887196   0xbad005c    ERANGE        Result too large
 VMK_VLAN_FILTERED                195887197   0xbad005d    ERANGE        Pkts dropped because of VLAN (support)  mismatch
 VMK_BAD_EXCFRAME                 195887198   0xbad005e    EFAULT        Unsafe exception frame
 VMK_MODULE_NOT_LOADED            195887199   0xbad005f    ENODEV        Necessary module isn't loaded
 VMK_NO_SUCH_ZOMBIE               195887200   0xbad0060    ECHILD        No dead world by that name
 VMK_NO_SUCH_CARTEL               195887201   0xbad0061    ESRCH         No cartel by that name
 VMK_IS_A_SYMLINK                 195887202   0xbad0062    ELOOP         Is a symbolic link
 VMK_CROSS_DEVICE_LINK            195887203   0xbad0063    EXDEV         Cross-device link
 VMK_NOT_A_SOCKET                 195887204   0xbad0064    ENOTSOCK      Not a socket
 VMK_ILLEGAL_SEEK                 195887205   0xbad0065    ESPIPE        Illegal seek
 VMK_ADDRFAM_UNSUPP               195887206   0xbad0066    EAFNOSUPPORT  Unsupported address family
 VMK_ALREADY_CONNECTED            195887207   0xbad0067    EISCONN       Already connected
 VMK_DEATH_PENDING                195887208   0xbad0068    ENOENT        World is marked for death
 VMK_NO_CELL_ASSIGNMENT           195887209   0xbad0069    EINVAL        No valid scheduler cell assignment
 VMK_CPU_MIN_INVALID              195887210   0xbad006a    EINVAL        Invalid cpu min
 VMK_CPU_MINLIMIT_INVALID         195887211   0xbad006b    EINVAL        Invalid cpu minLimit
 VMK_CPU_MAX_INVALID              195887212   0xbad006c    EINVAL        Invalid cpu max
 VMK_CPU_SHARES_INVALID           195887213   0xbad006d    EINVAL        Invalid cpu shares
 VMK_CPU_MIN_OVERFLOW             195887214   0xbad006e    EINVAL        Cpu min outside valid range
 VMK_CPU_MINLIMIT_OVERFLOW        195887215   0xbad006f    EINVAL        Cpu minLimit outside valid range
 VMK_CPU_MAX_OVERFLOW             195887216   0xbad0070    EINVAL        Cpu max outside valid range
 VMK_CPU_MIN_GT_MINLIMIT          195887217   0xbad0071    EINVAL        Cpu min exceeds minLimit
 VMK_CPU_MIN_GT_MAX               195887218   0xbad0072    EINVAL        Cpu min exceeds max
 VMK_CPU_MINLIMIT_LT_RESERVED     195887219   0xbad0073    ENOSPC        Cpu minLimit less than cpu already  reserved by children
 VMK_CPU_MAX_LT_RESERVED          195887220   0xbad0074    ENOSPC        Cpu max less than cpu already reserved by children
 VMK_CPU_ADMIT_FAILED             195887221   0xbad0075    ENOSPC        Admission check failed for cpu resource
 VMK_MEM_MIN_INVALID              195887222   0xbad0076    EINVAL        Invalid memory min
 VMK_MEM_MINLIMIT_INVALID         195887223   0xbad0077    EINVAL        Invalid memory minLimit
 VMK_MEM_MAX_INVALID              195887224   0xbad0078    EINVAL        Invalid memory max
 VMK_MEM_MIN_OVERFLOW             195887225   0xbad0079    EINVAL        Memory min outside valid range
 VMK_MEM_MINLIMIT_OVERFLOW        195887226   0xbad007a    EINVAL        Memory minLimit outside valid range
 VMK_MEM_MAX_OVERFLOW             195887227   0xbad007b    EINVAL        Memory max outside valid range
 VMK_MEM_MIN_GT_MINLIMIT          195887228   0xbad007c    EINVAL        Memory min exceeds minLimit
 VMK_MEM_MIN_GT_MAX               195887229   0xbad007d    EINVAL        Memory min exceeds max
 VMK_MEM_MINLIMIT_LT_RESERVED     195887230   0xbad007e    ENOSPC        Memory minLimit less than memory already  reserved by children
 VMK_MEM_MAX_LT_RESERVED          195887231   0xbad007f    ENOSPC        Memory max less than memory already  reserved by children
 VMK_MEM_ADMIT_FAILED             195887232   0xbad0080    ENOSPC        Admission check failed for memory resource
 VMK_NO_SWAP_FILE                 195887233   0xbad0081    ENOENT        No swap file
 VMK_BAD_PARAM_COUNT              195887234   0xbad0082    EINVAL        Bad parameter count
 VMK_BAD_PARAM_TYPE               195887235   0xbad0083    EINVAL        Bad parameter type
 VMK_UNMAP_RETRY                  195887236   0xbad0084    ENOMEM        Dueling unmaps (ok to retry)
 VMK_INVALID_IOCTL                195887237   0xbad0085    ENOTTY        Inappropriate ioctl for device
 VMK_MAPFAULT_RETRY               195887238   0xbad0086    EBUSY         Mmap changed under page fault (ok to  retry)
 VMK_EINPROGRESS                  195887239   0xbad0087    EINPROGRESS   Operation now in progress
 VMK_ADDR_UNMAPPED                195887240   0xbad0088    EFAULT        Address temporarily unmapped
 VMK_INVALID_BUDDY_TYPE           195887241   0xbad0089    ENOMEM        Invalid buddy type
 VMK_LPAGE_INFO_NOT_FOUND         195887242   0xbad008a    ENOMEM        Large page info not found
 VMK_LPAGE_INFO_INVALID           195887243   0xbad008b    EINVAL        Invalid large page info
 VMK_SNAPSHOT_DEV                 195887244   0xbad008c    EIO           SCSI LUN is in snapshot state
 VMK_IN_TRANSITION                195887245   0xbad008d    EIO           SCSI LUN is in transition
 VMK_TXN_FULL                     195887246   0xbad008e    ENOSPC        Transaction ran out of lock space or log  space
 VMK_LOCK_NOT_FREE                195887247   0xbad008f    EBUSY         Lock was not free
 VMK_NUM_FILES_EXCEEDED           195887248   0xbad0090    ENOSPC        Exceed maximum number of files on the filesystem
 VMK_MIGRATE_VMX_FAILURE          195887249   0xbad0091    EINVAL        Migration determined a failure by the VMX
 VMK_VSI_LIST_OVERFLOW            195887250   0xbad0092    EFBIG         VSI GetList handler overflow
 VMK_INVALID_WORLD                195887251   0xbad0093    EINVAL        Invalid world
 VMK_INVALID_VMM                  195887252   0xbad0094    EINVAL        Invalid vmm
 VMK_INVALID_TXN                  195887253   0xbad0095    EINVAL        Invalid transaction
 VMK_FS_RETRY_OPERATION           195887254   0xbad0096    EAGAIN        Transient file system condition, suggest  retry
 VMK_VCPU_LIMIT_EXCEEDED          195887255   0xbad0097    EINVAL        Number of running VCPUs limit exceeded
 VMK_INVALID_METADATA             195887256   0xbad0098    EINVAL        Invalid metadata
 VMK_INVALID_PAGE_NUMBER          195887257   0xbad0099    EINVAL        Invalid page number
 VMK_NOT_EXEC                     195887258   0xbad009a    ENOEXEC       Not in executable format
 VMK_NFS_CONNECT_FAILURE          195887259   0xbad009b    EHOSTDOWN     Unable to connect to NFS server
 VMK_NFS_MOUNT_NOT_SUPPORTED      195887260   0xbad009c    EINVAL        The NFS server does not support MOUNT  version 3 over TCP
 VMK_NFS_NFS_NOT_SUPPORTED        195887261   0xbad009d    EINVAL        The NFS server does not support NFS  version 3 over TCP
 VMK_NFS_MOUNT_DENIED             195887262   0xbad009e    EPERM         The mount request was denied by the NFS  server. Check that the export exists and that the client is permitted to mount it
 VMK_NFS_MOUNT_NOT_DIR            195887263   0xbad009f    ENOTDIR       The specified mount path was not a directory
 VMK_NFS_BAD_FSINFO               195887264   0xbad00a0    EACCES        Unable to query remote mount point's attributes
 VMK_NFS_VOLUME_LIMIT_EXCEEDED    195887265   0xbad00a1    EINVAL        NFS has reached the maximum number of supported volumes
 VMK_NO_MEMORY_NICE               195887266   0xbad00a2    ENOMEM        Out of nice memory
 VMK_MIGRATE_PREEMPTIVE_FAIL      195887267   0xbad00a3    ENOMEM        VMotion failed to start due to lack of cpu or memory resources
 VMK_CACHE_MISS                   195887268   0xbad00a4    EFAULT        Cache miss
 VMK_STRESS_INDUCED_ERROR         195887269   0xbad00a5    EIO           Error induced when stress options are enabled
 VMK_TOO_MANY_LOCK_HOLDERS        195887270   0xbad00a6    EUSERS        Maximum number of concurrent hosts are already accessing this resource
 VMK_NO_JOURNAL                   195887271   0xbad00a7    EIO           Host doesn't have a journal
 VMK_RANK_VIOLATION               195887272   0xbad00a8    EDEADLK       Lock rank violation detected
 VMK_MODULE_FAILED                195887273   0xbad00a9    ENODEV        Module failed
 VMK_NO_MASTER_PTY                195887274   0xbad00aa    ENXIO         Unable to open slave if no master pty
 VMK_NOT_IOABLE                   195887275   0xbad00ab    EFAULT        Not IOAble
 VMK_NO_FREE_INODES               195887276   0xbad00ac    ENOSPC        No free inodes
 VMK_NO_MEMORY_FOR_FILEDATA       195887277   0xbad00ad    ENOSPC        No free memory for file data
 VMK_NO_TAR_SPACE                 195887278   0xbad00ae    ENOSPC        No free space to expand file or meta data
 VMK_NO_FIFO_READER               195887279   0xbad00af    ENXIO         Unable to open writer if no fifo reader
 VMK_NO_SUCH_DEVICE               195887280   0xbad00b0    EINVAL        No underlying device for major,minor
 VMK_MEM_MIN_GT_MEMSIZE           195887281   0xbad00b1    EINVAL        Memory min exceeds memSize
 VMK_NO_SUCH_VT                   195887282   0xbad00b2    ENXIO         No virtual terminal for number
 VMK_TOO_MANY_ELEMENTS            195887283   0xbad00b3    E2BIG         Too many elements for list
 VMK_SHAREDAREA_MISMATCH          195887284   0xbad00b4    ENOSYS        VMM&lt;-&gt;VMK shared are mismatch
 VMK_EXEC_FAILURE                 195887285   0xbad00b5    ESRCH         Failure during exec while original state already lost
 VMK_VMNIXMOD_NOT_LOADED          195887286   0xbad00b6    ENOSYS        vmnixmod kernel module not loaded
 VMK_INVALID_MODULE               195887287   0xbad00b7    EINVAL        Invalid module
 VMK_UNALIGNED_ADDRESS            195887288   0xbad00b8    EINVAL        Address is not aligned on page boundary
 VMK_NOT_MAPPED                   195887289   0xbad00b9    ENOMEM        Address is not mapped in address space
 VMK_NO_MESSAGE_SPACE             195887290   0xbad00ba    ENOMEM        No space to record a message
 VMK_PDI_STACK_OVERFLOW           195887291   0xbad00bb    EFBIG         No space left on PDI stack
 VMK_EXCEPTION_HANDLER_INVALID    195887292   0xbad00bc    EINVAL        Invalid exception handler
 VMK_EXCEPTION_NOT_HANDLED        195887293   0xbad00bd    EINVAL        Exception not handled by exception handler
 VMK_INVALID_MULTIWRITER_OBJECT   195887294   0xbad00be    EDEADLK       Can't open sparse/TBZ files in  multiwriter mode
 VMK_STORAGE_RETRY_OPERATION      195887295   0xbad00bf    EAGAIN        Transient storage condition, suggest retry
 VMK_HBA_ERROR                    195887296   0xbad00c0    EIO           Storage initiator error
 VMK_TIMER_INIT_FAILED            195887297   0xbad00c1    EINVAL        Timer initialization failed
 VMK_MODULE_NOT_FOUND             195887298   0xbad00c2    ENOENT        Module not found
 VMK_NOT_SOCKET_OWNER             195887299   0xbad00c3    EINVAL        Socket not owned by cartel
 VMK_VSI_HANDLER_NOT_FOUND        195887300   0xbad00c4    ENOENT        No VSI handler found for the requested node
 VMK_INVALID_MMAPPROTFLAGS        195887301   0xbad00c5    EINVAL        Invalid mmap protection flags
 VMK_INVALID_MAPCONTIG_SIZE       195887302   0xbad00c6    EINVAL        Invalid chunk size for contiguous mmap 
 VMK_INVALID_MAPCONTIG_MAX        195887303   0xbad00c7    EINVAL        Invalid MPN max for contiguous mmap 
 VMK_INVALID_MAPCONTIG_FLAG       195887304   0xbad00c8    EINVAL        Invalid mmap flag on contiguous mmap 
 VMK_NOT_LAZY_MMINFO              195887305   0xbad00c9    EINVAL        Unexpected fault on pre-faulted memory region
 VMK_MMINFO_WONT_SPLIT            195887306   0xbad00ca    EINVAL        Memory region cannot be split (remap/unmap)
 VMK_NO_CACHE_INFO                195887307   0xbad00cb    ENOENT        Cache Information not available
 VMK_CANNOT_REMAP_PINNED_MEMORY   195887308   0xbad00cc    EINVAL        Cannot remap pinned memory
 VMK_NO_SUCH_CARTELGROUP          195887309   0xbad00cd    ESRCH         No cartel group by that name
 VMK_SPLOCKSTATS_DISABLED         195887310   0xbad00ce    EINVAL        SPLock stats collection disabled
 VMK_BAD_TAR_IMAGE                195887311   0xbad00cf    EINVAL        Boot image is corrupted
 VMK_BRANCHED_ALREADY             195887312   0xbad00d0    EPERM         Branched file cannot be modified
 VMK_NAME_RESERVED_FOR_BRANCH     195887313   0xbad00d1    EPERM         Name is reserved for branched file
 VMK_CANNOT_BRANCH_UNLINKED       195887314   0xbad00d2    EPERM         Unlinked file cannot be branched
 VMK_MAX_RETRIES_EXCEEDED         195887315   0xbad00d3    EAGAIN        Maximum kernel-level retries exceeded
 VMK_OPTLOCK_STOLEN               195887316   0xbad00d4    EAGAIN        Optimistic lock acquired by another host
 VMK_NOT_MMAPABLE                 195887317   0xbad00d5    ENODEV        Object cannot be mmapped
 VMK_INVALID_CPU_AFFINITY         195887318   0xbad00d6    EINVAL        Invalid cpu affinity
 VMK_DEVICE_NOT_PARTOF_LV         195887319   0xbad00d7    ENXIO         Device does not contain a logical volume
 VMK_NO_SPACE                     195887320   0xbad00d8    ENOSPC        No space left on device
 VMK_VSI_INVALID_NODE_ID          195887321   0xbad00d9    EINVAL        Invalid vsi node ID
 VMK_TOO_MANY_USERS               195887322   0xbad00da    EUSERS        Too many users accessing this resource
 VMK_EALREADY                     195887323   0xbad00db    EALREADY      Operation already in progress
 VMK_BUF_TOO_SMALL                195887324   0xbad00dc    EINVAL        Buffer too small to complete the operation
 VMK_SNAPSHOT_DEV_DISALLOWED      195887325   0xbad00dd    EACCES        Snapshot device disallowed
 VMK_LVM_DEVICE_UNREACHABLE       195887326   0xbad00de    EIO           LVM device unreachable
 VMK_CPU_INVALID_RESOURCE_UNITS   195887327   0xbad00df    EINVAL        Invalid cpu resource units
 VMK_MEM_INVALID_RESOURCE_UNITS   195887328   0xbad00e0    EINVAL        Invalid memory resource units
 VMK_ABORTED                      195887329   0xbad00e1    ECANCELED     IO was aborted
 VMK_MEM_MIN_LT_RESERVED          195887330   0xbad00e2    ENOSPC        Memory min less than memory already reserved by children
 VMK_MEM_MIN_LT_CONSUMED          195887331   0xbad00e3    ENOSPC        Memory min less than memory required to support current consumption
 VMK_MEM_MAX_LT_CONSUMED          195887332   0xbad00e4    ENOSPC        Memory max less than memory required to support current consumption
 VMK_TIMEOUT_RETRY                195887333   0xbad00e5    ETIMEDOUT     Timeout (ok to retry)
 VMK_RESERVATION_LOST             195887334   0xbad00e6    EBUSY         Reservation Lost
 VMK_FS_STALE_METADATA            195887335   0xbad00e7    ENOENT        Cached metadata is stale
 VMK_NO_FCNTL_LOCK                195887336   0xbad00e8    ENOLCK        No fcntl lock slot left
 VMK_NO_FCNTL_LOCK_HOLDER         195887337   0xbad00e9    ENOLCK        No fcntl lock holder slot left
 VMK_NO_LICENSE                   195887338   0xbad00ea    EACCES        Not licensed to access VMFS volumes
 VMK_LVM_RETRY_OPERATION          195887339   0xbad00eb    EAGAIN        Transient LVM device condition, suggest retry
 VMK_SNAPSHOT_LV_INCOMPLETE       195887340   0xbad00ec    EAGAIN        Snapshot LV incomplete
 VMK_MEDIUM_NOT_FOUND             195887341   0xbad00ed    EIO           Medium not found
 VMK_MAX_PATHS_CLAIMED            195887342   0xbad00ee    ENOMEM        Maximum allowed SCSI paths have already  been claimed
 VMK_NOT_MOUNTABLE                195887343   0xbad00ef    ENODEV        Filesystem is not mountable
 VMK_MEMSIZE_GT_MEMSIZELIMIT      195887344   0xbad00f0    EINVAL        Memory size exceeds memSizeLimit
 VMK_GENERIC_LINUX_ERROR          732758016   0x2bad0000   EIO           Generic service console error

==== External Links ====

* [http://kb.vmware.com/kb/1004250 VMware KB: Decoding Purple Screen errors]
* [http://kb.vmware.com/kb/1005184 VMware KB: Decoding Machine Check Exception (MCE) output after a purple screen (PSOD) error]


[[Category: ESX]] [[Category: CLI]]</text>
    <sha1>355ea00c1b2b671f879d7cfd762643e5e71b6f75</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Build host vmware kernel modules</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>1101</id>
    <parentid>997</parentid>
    <timestamp>2009-09-23T10:16:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added tip from birdie on creating an alias for vmware-config.pl on newer VMware workstation setups</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3151" xml:space="preserve">====Integrated modules build script sometimes fails====
The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

====The solution====
You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm -f /etc/vmware/not_configured 

====Preconditions for the script to work====
You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko

====Alternative solution====
Of course there is still a vmware application available that you can use for this as well.
[http://communities.vmware.com/people/birdie Birdie] came up with a smart alternative so you can keep things like they used to be by creating an alias for the modconfig with the correct parameters to run it in the console.
 alias vmware-config.pl='vmware-modconfig --console --install-all'

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>d050d663798ac2302dbdadd0204dafb137e54200</sha1>
  </revision>
</page>
<page arvcontinue="20090819201450|1054">
  <title>Vmsvc/device.diskadd</title>
  <ns>0</ns>
  <id>158</id>
  <revision>
    <id>1102</id>
    <parentid>313</parentid>
    <timestamp>2009-09-23T19:05:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>adding example to vimsh device.diskadd</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="481" xml:space="preserve">==== vimsh vmsvc/device.diskadd ====
Usage: device.diskadd vmid size controller-number unit-number datastore

Add a disk to the virtual machine with id vmid.
Size is in kilobytes.
Controller number is the controller number as is specified in the vmx configuration file.

==== Example ====

vim-cmd vmsvc/device.diskadd 16 5242880 scsi0 2 datastore1

See also: 
* [http://communities.vmware.com/thread/233019 VMTN: vim-cmd vmsvc/device.diskadd syntax headaches]

[[Category: Vimsh]]</text>
    <sha1>0e868d8aa887c24ea8273f8ff38e6d5bbac82c33</sha1>
  </revision>
  <revision>
    <id>1103</id>
    <parentid>1102</parentid>
    <timestamp>2009-09-23T19:07:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="504" xml:space="preserve">==== vimsh vmsvc/device.diskadd ====
Usage: device.diskadd vmid size controller-number unit-number datastore

Add a disk to the virtual machine with id vmid.
 Size is the new disk size in kilobytes. 
 Controller number is the controller number as is specified in the vmx configuration file.
 

==== Example ====

vim-cmd vmsvc/device.diskadd 16 5242880 scsi0 2 datastore1

See also: 
* [http://communities.vmware.com/thread/233019 VMTN: vim-cmd vmsvc/device.diskadd syntax headaches]

[[Category: Vimsh]]</text>
    <sha1>f5779859fc178bc1321d49001eb717a23823e5dc</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>1104</id>
    <parentid>1097</parentid>
    <timestamp>2009-09-25T13:01:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to PowerCLI blog on how-to run scripts from vCenter alarms</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5938" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>efdef1045ead9579995dc90231afb74b61cbc5c8</sha1>
  </revision>
  <revision>
    <id>1105</id>
    <parentid>1104</parentid>
    <timestamp>2009-10-06T09:40:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to VMTN PowerCLI Poster</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6036" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>8f823116d07e4b7de58c1a4955fbed628fb636bb</sha1>
  </revision>
  <revision>
    <id>1108</id>
    <parentid>1105</parentid>
    <timestamp>2009-10-17T13:10:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to interactive powershell tutorial</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6171" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>e0b0ce61588ee374ea342ca438458700abe822d8</sha1>
  </revision>
  <revision>
    <id>1111</id>
    <parentid>1108</parentid>
    <timestamp>2009-11-21T20:17:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6230" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [[Jonathan Medd's Powershell 2.0 One Cmdlet at a time]]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>1d7f30f32ad8f25fa3c5b7700054c81466d5b0f9</sha1>
  </revision>
  <revision>
    <id>1121</id>
    <parentid>1111</parentid>
    <timestamp>2010-02-03T12:54:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to Sapien technologies Free windows Powershell eBook</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6359" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [[Jonathan Medd's Powershell 2.0 One Cmdlet at a time]]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

*[http://blog.sapien.com/index.php/2009/12/01/free-windows-powershell-ebook/ Sapien technologies Free windows Powershell eBook]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>36729f69cdfcdf931411a496a2f68f0d1b1ce768</sha1>
  </revision>
  <revision>
    <id>1122</id>
    <parentid>1121</parentid>
    <timestamp>2010-02-11T16:01:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6386" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [[Jonathan Medd's Powershell 2.0 One Cmdlet at a time]]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

*[http://blog.sapien.com/index.php/2009/12/01/free-windows-powershell-ebook/ Sapien technologies Free windows Powershell eBook]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>fa2449d2c1fcae909f340271756fc5e7ee38be2a</sha1>
  </revision>
  <revision>
    <id>1124</id>
    <parentid>1122</parentid>
    <timestamp>2010-02-11T16:06:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>moving powershell resources cont.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6198" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

==== General powershell ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>35054df8e90822e29d1edc91642ec34fbdb0127d</sha1>
  </revision>
  <revision>
    <id>1127</id>
    <parentid>1124</parentid>
    <timestamp>2010-02-11T16:18:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>moving moving moving ;)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3756" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>f8567752103ce9c5ff99b712029de3dafe244ed5</sha1>
  </revision>
  <revision>
    <id>1129</id>
    <parentid>1127</parentid>
    <timestamp>2010-02-11T16:24:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>More reorganizing in the powershell page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3884" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====
===== General Powershell =====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Powershell techniques and tips]]

* [[Powershell Tools]]

===== VI-Toolkit / PowerCLI =====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts (not categorized) ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>0c8e80a3b345504428dedffaa430fac40f9c25d0</sha1>
  </revision>
  <revision>
    <id>1132</id>
    <parentid>1129</parentid>
    <timestamp>2010-02-11T16:29:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3895" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====
===== General Powershell =====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Powershell techniques and tips]]

* [[Powershell Tools]]

===== VI-Toolkit / PowerCLI =====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>2f2c0c5599cf51118e722f8668f49efa0d86d648</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Perl</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>1106</id>
    <parentid>1093</parentid>
    <timestamp>2009-10-06T09:46:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to William Lam's Getting started doc on VMTN</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="547" xml:space="preserve">==== Learning more about Perl and the SDK ====
[http://communities.vmware.com/docs/DOC-10837 Getting Started with the vSphere SDK for Perl]

[http://www.perl.org/docs.html Perl.org Online Documentation]


==== Scripts ====
[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]

[[Listing all VM's in a cluster]]

[[Rename local storage datastore]]

[[Factory Reset of ESXi]]

[[Category: Perl]]</text>
    <sha1>246ddb17d1967ef7979af1e8ae341570c07b1bf1</sha1>
  </revision>
  <revision>
    <id>1142</id>
    <parentid>1106</parentid>
    <timestamp>2010-02-27T16:49:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="587" xml:space="preserve">==== Learning more about Perl and the SDK ====
[http://communities.vmware.com/docs/DOC-10837 Getting Started with the vSphere SDK for Perl]

[http://www.perl.org/docs.html Perl.org Online Documentation]

[[Install the VI Perl Toolkit on OS X]]

==== Scripts ====
[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]

[[Listing all VM's in a cluster]]

[[Rename local storage datastore]]

[[Factory Reset of ESXi]]

[[Category: Perl]]</text>
    <sha1>eba95462bef4fdd0ae53f882ba014a54ac27f0ea</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Vmware-configcheck</title>
  <ns>0</ns>
  <id>507</id>
  <revision>
    <id>1107</id>
    <timestamp>2009-10-16T16:37:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Jason Boche just pointed out how to use vmware-configcheck, very very nice Jason, thanks!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="482" xml:space="preserve">==== Vmware-configcheck ====

You can use this command to check your vmx files.
For example run it as:
 vmware-configcheck | grep -v PASS
will show all the lines from the output that did NOT pass the configcheck.

==== example output ====
 # vmware-configcheck
 PASS /vmfs/volumes/78141e02-84ea5898-92c1-0001b3a0924a/Vista/vista.vmx
 PASS /vmfs/volumes/78141e1a-046271b8-0a48-0001b3a0924a/CentOS/CentOS.vmx
 PASS /vmfs/volumes/78141dd7-7b370470-6a0d-0001b3a0924a/Solaris/Solaris.vmx</text>
    <sha1>cf54ffc60358e82a0b26a891b32ceb138ac6b7c9</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>1109</id>
    <parentid>1072</parentid>
    <timestamp>2009-10-24T07:45:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added page with external scripts for my todo list</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3001" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]

[[Performing emergency shut down of VM's on ESX]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

[[APC/APCUPSD ESX/ESXi Host shutdown script]]

==== Perl scripts ====
[[Recover vmx from log file]]

==== AppleScript ====

[http://communities.vmware.com/thread/122793 AppleScript to Run Virtual Machine and switch to Full Screen View or Unity View at Login]

==== Javascript ====
[[Ghetto vCenter 4.0 Unattended Installer]]

==== In the pipeline ====
[[External scripts that are not processed yet]]</text>
    <sha1>081ddc71843ad08f55cfa7d6b7ee88a78f88b6a7</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>External scripts that are not processed yet</title>
  <ns>0</ns>
  <id>508</id>
  <revision>
    <id>1110</id>
    <timestamp>2009-10-24T07:50:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>list with lots of hyperlinks to other scripts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4399" xml:space="preserve">Unfortunately I have been rather busy lately. 
Because of that I've had little time to process the scripts that have been published.
But that doesn't mean I didn't keep a record of them :)
So until I get a bit more time, here's the list of scripts... (It will probably grow some more before it gets shorter again)

==== recent hyperlinks ====
[http://professionalvmware.com/2008/12/vmware-vix-changing-ips-of-a-guest-vm/ VMware VIX – Changing IP’s of a Guest VM]

[http://professionalvmware.com/2009/09/four-powercli-one-liners-that-saved-the-world/ Four PowerCLI One-Liners That Saved The World!]

[http://communities.vmware.com/docs/DOC-10878 Getting Started with the vMA (tips/tricks)]

[http://blogs.vmware.com/developer/2009/10/vsphere-apis-for-performance-monitoring-webinar-pdf-posted-.html vSphere APIs for Performance Monitoring - Webinar, PDF Posted !]

[http://www.jonathanmedd.net/2009/09/find-the-bios-version-of-an-esx-host.html Find the BIOS Version of an ESX Host ]

[http://get-admin.com/blog/?p=863 PowerCLI: VM displayName -ne Name]

[http://get-admin.com/blog/?p=879 PowerCLI: Speed boost, Find VM Snapshots by Name.]

[http://www.peetersonline.nl/index.php/vmware/add-vmx-path-to-vi-client-using-powershell/ Add Vmx Path to VI Client using Powershell]

[http://communities.vmware.com/docs/DOC-10641 Service status and email if down (as well as try to start it)]

[http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/ PowerCLI: Set-dvSwitch]

[http://communities.vmware.com/docs/DOC-10859 Creating vSphere Client Plug In - Tech Ex Developer Day Session]

[http://communities.vmware.com/docs/DOC-10883 useVIFastpassOnvMAToRunPerlScriptWithoutClearTextPassword.pl]

[http://www.virtu-al.net/2009/10/12/powercli-more-hal-information/ PowerCLI: More HAL Information]

[http://www.virtu-al.net/2009/10/14/powercli-host-network-config/ PowerCLI: Host Network Config]

[http://ict-freak.nl/2009/10/05/powercli-enabledisable-the-vm-hot-add-features/ PowerCLI: Enable/Disable the VM Hot Add features]

[http://ict-freak.nl/2009/10/05/powercli-check-cpumemory-hot-add/ PowerCLI: Check CPU/Memory Hot Add]

[http://www.virtu-al.net/2009/09/21/powercli-one-liners-checking-host-network-information/ PowerCLI: One-Liners Checking Host Network Information]

[http://poshcode.org/1337 Get-SerialNumber]

[http://www.virtu-al.net/2009/09/23/powercli-how-many-vms-on-your-datastores/ PowerCLI: How many VMs on your Datastores ?]

[http://communities.vmware.com/docs/DOC-10807 getVMsPerDatastore.pl]

[http://communities.vmware.com/docs/DOC-10809 generateVMRemoteConsoleURL.pl]

[http://communities.vmware.com/docs/DOC-10777 getVMThinProvisionedSavings.pl]

[http://blogs.vmware.com/vipowershell/2009/08/how-to-list-datastores-that-are-on-shared-storage.html How to list datastores and VMs that are on shared storage.]

[http://communities.vmware.com/docs/DOC-10552 getShareableAndNonSharDatastore.pl]

[http://www.virtu-al.net/2009/08/17/powercli-reading-host-log-files/ PowerCLI: Reading host log files]

[http://www.ntpro.nl/blog/archives/1228-Visual-Basic-Samples-for-VMware-vSphere-Webservices-SDK.html Visual Basic Samples for VMware vSphere™ Webservices SDK]

[http://communities.vmware.com/docs/DOC-10003 Create File system]

[http://communities.vmware.com/docs/DOC-9925 Performance Statistics]

[http://communities.vmware.com/thread/221619?tstart=0 Remote Console URL]

[http://www.jonathanmedd.net/2009/09/average-cpu-and-memory-use-per-host-per-cluster.html Average CPU and Memory Use Per Host Per Cluster]

[http://www.ntpro.nl/blog/archives/1296-Ruby-sample-code-and-library-for-VI-SDK.html Ruby sample code and library for VI SDK]

[http://communities.vmware.com/docs/DOC-10885 getVMDiskInfo.pl]

[http://ict-freak.nl/2009/10/09/powercli-virtual-machine-disk-vmdk-info/ PowerCLI: Virtual Machine Disk (VMDK) info]

[http://day2dayadmin.blogspot.com/2009/10/configuring-network-with-powercli-and.html Configuring Network with PowerCLI and .CSV File]

[http://poshcode.org/1384 Get-Hostname]

[http://communities.vmware.com/docs/DOC-10866 setUserDatastorePermission.pl]

[http://blogs.vmware.com/vipowershell/2009/10/when-was-the-last-time-that-vm-was-powered-on.html When was the last time that VM was powered on?]

[http://communities.vmware.com/docs/DOC-10847 pluginExtensionManager.pl]

[http://halr9000.com/article/828 Adding Port Groups with PowerCLI]


[[Category: ToDo]]</text>
    <sha1>a885f18354882782d1d7c6804ee5dcc7b84a65f4</sha1>
  </revision>
  <revision>
    <id>1152</id>
    <parentid>1110</parentid>
    <timestamp>2010-02-28T21:45:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added some more links for the ToDo list..</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6865" xml:space="preserve">Unfortunately I have been rather busy lately. 
Because of that I've had little time to process the scripts that have been published.
But that doesn't mean I didn't keep a record of them :)
So until I get a bit more time, here's the list of scripts... (It will grow some more before it gets shorter again)

[http://professionalvmware.com/2008/12/vmware-vix-changing-ips-of-a-guest-vm/ VMware VIX – Changing IP’s of a Guest VM]

[http://professionalvmware.com/2009/09/four-powercli-one-liners-that-saved-the-world/ Four PowerCLI One-Liners That Saved The World!]

[http://communities.vmware.com/docs/DOC-10878 Getting Started with the vMA (tips/tricks)]

[http://blogs.vmware.com/developer/2009/10/vsphere-apis-for-performance-monitoring-webinar-pdf-posted-.html vSphere APIs for Performance Monitoring - Webinar, PDF Posted !]

[http://www.jonathanmedd.net/2009/09/find-the-bios-version-of-an-esx-host.html Find the BIOS Version of an ESX Host ]

[http://get-admin.com/blog/?p=863 PowerCLI: VM displayName -ne Name]

[http://get-admin.com/blog/?p=879 PowerCLI: Speed boost, Find VM Snapshots by Name.]

[http://www.peetersonline.nl/index.php/vmware/add-vmx-path-to-vi-client-using-powershell/ Add Vmx Path to VI Client using Powershell]

[http://communities.vmware.com/docs/DOC-10641 Service status and email if down (as well as try to start it)]

[http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/ PowerCLI: Set-dvSwitch]

[http://communities.vmware.com/docs/DOC-10859 Creating vSphere Client Plug In - Tech Ex Developer Day Session]

[http://www.virtu-al.net/2009/10/12/powercli-more-hal-information/ PowerCLI: More HAL Information]

[http://www.virtu-al.net/2009/10/14/powercli-host-network-config/ PowerCLI: Host Network Config]

[http://ict-freak.nl/2009/10/05/powercli-enabledisable-the-vm-hot-add-features/ PowerCLI: Enable/Disable the VM Hot Add features]

[http://ict-freak.nl/2009/10/05/powercli-check-cpumemory-hot-add/ PowerCLI: Check CPU/Memory Hot Add]

[http://poshcode.org/1337 Get-SerialNumber]

[http://www.virtu-al.net/2009/09/23/powercli-how-many-vms-on-your-datastores/ PowerCLI: How many VMs on your Datastores ?]

[http://blogs.vmware.com/vipowershell/2009/08/how-to-list-datastores-that-are-on-shared-storage.html How to list datastores and VMs that are on shared storage.]

[http://www.virtu-al.net/2009/08/17/powercli-reading-host-log-files/ PowerCLI: Reading host log files]

[http://www.ntpro.nl/blog/archives/1228-Visual-Basic-Samples-for-VMware-vSphere-Webservices-SDK.html Visual Basic Samples for VMware vSphere™ Webservices SDK]

[http://communities.vmware.com/docs/DOC-10003 Create File system]

[http://communities.vmware.com/docs/DOC-9925 Performance Statistics]

[http://communities.vmware.com/thread/221619?tstart=0 Remote Console URL]

[http://www.jonathanmedd.net/2009/09/average-cpu-and-memory-use-per-host-per-cluster.html Average CPU and Memory Use Per Host Per Cluster]

[http://www.ntpro.nl/blog/archives/1296-Ruby-sample-code-and-library-for-VI-SDK.html Ruby sample code and library for VI SDK]

[http://ict-freak.nl/2009/10/09/powercli-virtual-machine-disk-vmdk-info/ PowerCLI: Virtual Machine Disk (VMDK) info]

[http://day2dayadmin.blogspot.com/2009/10/configuring-network-with-powercli-and.html Configuring Network with PowerCLI and .CSV File]

[http://poshcode.org/1384 Get-Hostname]

[http://blogs.vmware.com/vipowershell/2009/10/when-was-the-last-time-that-vm-was-powered-on.html When was the last time that VM was powered on?]

[http://halr9000.com/article/828 Adding Port Groups with PowerCLI]

[http://professionalvmware.com/2009/11/disabling-copy-paste-the-powercli-way/ Disabling Copy Paste – The PowerCLI way]

[http://www.virtu-al.net/2009/10/26/workstation-server-audit-script-v3/ Workstation &amp; Server Audit Script V3]

[http://lucd.info/?p=859 Thick to Thin with PowerCLI and the SDK]

[http://professionalvmware.com/2009/10/a-quick-powercli-lesson-digging-for-info-who-powered-off-that-vm/ A Quick PowerCLI Lesson – Digging for Info (Who Powered Off that VM)]

[http://www.virtu-al.net/2009/10/19/powercli-mass-vm-portgroup-change/ PowerCLI: Mass VM Portgroup Change]

[http://www.virtu-al.net/2009/11/10/powercli-where-do-i-start/ PowerCLI – Where do I start ?!]

[http://vinternals.com/esxi-mastery/ ESXi Mastery]

[http://www.virtu-al.net/2009/10/30/powercli-vsphere-license-export/ PowerCLI: vSphere License Export]

[http://www.peetersonline.nl/index.php/vmware/report-vsphere-alarms-with-powershell/ Report vSphere Alarms with Powershell]

[http://www.virtu-al.net/2009/10/28/powercli-listing-cluster-primary-ha-nodes/ PowerCLI: Listing Cluster Primary HA Nodes]

[http://ict-freak.nl/2009/11/17/powercli-one-liner-to-get-vms-clusters-esx-hosts-and-datastores/ PowerCLI: One-Liner to get VMs, Clusters, ESX Hosts and Datastores]

[http://www.vmware.com/support/developer/windowstoolkit/wintk40u1/html/index.html vSphere PowerCLI 4.0 Update 1 Cmdlets Reference]

[http://communities.vmware.com/thread/235164 PowerCLI Poster]

[http://ict-freak.nl/2010/01/21/powercli-move-template/ PowerCLI: Move-Template]

[http://ict-freak.nl/2010/01/27/move-template-integrated-into-the-vesi/ Move-Template integrated into the VESI]

[http://ict-freak.nl/2010/01/28/backup-and-restore-drs-rules-with-the-vesi/ Backup and Restore DRS Rules with the VESI]

[http://www.virtu-al.net/2010/02/09/powercli-how-many-hbas/ PowerCLI: How many HBA’s ?]

[http://get-admin.com/blog/?p=941 PowerCLI: Remove SMVI snapshots]

[http://get-admin.com/blog/?p=954 PowerShell: Custom Types, and Formatting]

[http://searchvmware.techtarget.com/generic/0,295582,sid179_gci1381348,00.html Using PowerShell and PowerCLI to work with host servers]

==== Perl ====

[http://communities.vmware.com/docs/DOC-11135 findVMsWithRDMs.pl]

[http://communities.vmware.com/docs/DOC-11003 vmISOManagement.pl]

[http://communities.vmware.com/docs/DOC-10974 rdmManagmement.pl]

[http://communities.vmware.com/docs/DOC-11000 upgradeVMVirtualHardware.pl]

[http://communities.vmware.com/docs/DOC-11221 configureAdvHAClusterOptions.pl]

[http://communities.vmware.com/docs/DOC-11213 addExistingVMDKToVM.pl]

[http://communities.vmware.com/docs/DOC-11054 listHAClusterNodes.pl]

[http://communities.vmware.com/docs/DOC-10866 setUserDatastorePermission.pl]

[http://communities.vmware.com/docs/DOC-10847 pluginExtensionManager.pl]

[http://communities.vmware.com/docs/DOC-10883 useVIFastpassOnvMAToRunPerlScriptWithoutClearTextPassword.pl]

[http://communities.vmware.com/docs/DOC-10807 getVMsPerDatastore.pl]

[http://communities.vmware.com/docs/DOC-10809 generateVMRemoteConsoleURL.pl]

[http://communities.vmware.com/docs/DOC-10777 getVMThinProvisionedSavings.pl]

[http://communities.vmware.com/docs/DOC-10552 getShareableAndNonSharDatastore.pl]

[http://communities.vmware.com/docs/DOC-10885 getVMDiskInfo.pl]

[[Category: ToDo]]</text>
    <sha1>d407b6809295f211d8ca5645382d514c17632b1c</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Jonathan Medd's Powershell 2.0 One Cmdlet at a time</title>
  <ns>0</ns>
  <id>509</id>
  <revision>
    <id>1112</id>
    <timestamp>2009-11-21T20:20:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Jonathan Medd's Powershell Cmdlet series</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1397" xml:space="preserve">==== Learning Powershell ====
Jonathan Medd is creating a powershell 2.0 guide where he explains cmdlet's one by one.

He call's it the Cmdlet series: [http://www.jonathanmedd.net/category/cmdlet-series Powershell 2.0: One Cmdlet at a Time] 

Per Cmdlet, he explains what it does and adds a nice example on how-to use the Cmdlet in real life.
If there are any dependencies besides installing powershell 2.0, they are listed.
As a final teaser he also explains how you could do a similar thing with Powershell 1.0

Very nicely done Jonathan, keep up the good work!

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-1-get-random.html Get-Random]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-2-send-mailmessage.html Send-MailMessage]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-3-get-counter.html Get-Counter]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-4-out-gridview.html Out-GridView]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-5-get-hotfix.html Get-Hotfix]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-6-test-connection.html Test-Connection]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-7-reset-computermachinepassword.html Reset-ComputerMachinePassword]

[[Category: Powershell]]</text>
    <sha1>fd8a2f3e4a43259dbff30f9531fd63409c1cf5f6</sha1>
  </revision>
  <revision>
    <id>1113</id>
    <parentid>1112</parentid>
    <timestamp>2009-12-13T17:37:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Jonathan Medd is still going strong with his One Cmdlet at a time series, added the 11 next Cmdlet's!!! he documented to this page here. Very impressive reading!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2620" xml:space="preserve">==== Learning Powershell ====
Jonathan Medd is creating a powershell 2.0 guide where he explains cmdlet's one by one.

He call's it the Cmdlet series: [http://www.jonathanmedd.net/category/cmdlet-series Powershell 2.0: One Cmdlet at a Time] 

Per Cmdlet, he explains what it does and adds a nice example on how-to use the Cmdlet in real life.
If there are any dependencies besides installing powershell 2.0, they are listed.
As a final teaser he also explains how you could do a similar thing with Powershell 1.0

Very nicely done Jonathan, keep up the good work!

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-1-get-random.html Get-Random]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-2-send-mailmessage.html Send-MailMessage]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-3-get-counter.html Get-Counter]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-4-out-gridview.html Out-GridView]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-5-get-hotfix.html Get-Hotfix]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-6-test-connection.html Test-Connection]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-7-reset-computermachinepassword.html Reset-ComputerMachinePassword]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-8-get-module.html Get-Module]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-9-checkpoint-compute.html Checkpoint-Computer]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-10-restar-computer.html Restart-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-11-add-computer.html Add-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-12-write-eventlog.html Write-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-13-clear-eventlog.html Clear-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-14-start-process.html Start-Process]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-15-start-job.html Start-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-16-get-job.html Get-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-17-receive-job.html Receive-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-18-remove-job.html Remove-Job]

[[Category: Powershell]]</text>
    <sha1>36684c1b2e3240762515871c3b2c828b845e8a19</sha1>
  </revision>
  <revision>
    <id>1118</id>
    <parentid>1113</parentid>
    <timestamp>2010-01-04T13:29:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added the latest updates from the Powershell 2.0 One CmdLet at a time series from Jonathan Medd, cmdlet 19 to 27</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3715" xml:space="preserve">==== Learning Powershell ====
Jonathan Medd is creating a powershell 2.0 guide where he explains cmdlet's one by one.

He call's it the Cmdlet series: [http://www.jonathanmedd.net/category/cmdlet-series Powershell 2.0: One Cmdlet at a Time] 

Per Cmdlet, he explains what it does and adds a nice example on how-to use the Cmdlet in real life.
If there are any dependencies besides installing powershell 2.0, they are listed.
As a final teaser he also explains how you could do a similar thing with Powershell 1.0

Very nicely done Jonathan, keep up the good work!

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-1-get-random.html Get-Random]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-2-send-mailmessage.html Send-MailMessage]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-3-get-counter.html Get-Counter]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-4-out-gridview.html Out-GridView]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-5-get-hotfix.html Get-Hotfix]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-6-test-connection.html Test-Connection]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-7-reset-computermachinepassword.html Reset-ComputerMachinePassword]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-8-get-module.html Get-Module]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-9-checkpoint-compute.html Checkpoint-Computer]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-10-restar-computer.html Restart-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-11-add-computer.html Add-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-12-write-eventlog.html Write-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-13-clear-eventlog.html Clear-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-14-start-process.html Start-Process]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-15-start-job.html Start-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-16-get-job.html Get-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-17-receive-job.html Receive-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-18-remove-job.html Remove-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-19-stop-job.html Stop-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-20-wait-job.html Wait-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-21-select-xml.html Select-Xml]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-22-enable-computerrestore.html Enable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-23-disable-computerrestore.html Disable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-24-get-computerrestorepoint.html Get-ComputerRestorePoint]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-25-restore-computer.html Restore-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-26-new-webserviceproxy.html New-WebServiceProxy]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-27-test-computersecurechannel.html Test-ComputerSecureChannel]

[[Category: Powershell]]</text>
    <sha1>fd1a012a5fafbe2b858a747a6e8f8bd49e2769ab</sha1>
  </revision>
  <revision>
    <id>1133</id>
    <parentid>1118</parentid>
    <timestamp>2010-02-11T16:50:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Catching up with Jonathan Medd's amazing One Cmdlet at a time series, there's 62! cmdlets explained by now</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8066" xml:space="preserve">==== Learning Powershell ====
Jonathan Medd is creating a powershell 2.0 guide where he explains cmdlet's one by one.

He call's it the Cmdlet series: [http://www.jonathanmedd.net/category/cmdlet-series Powershell 2.0: One Cmdlet at a Time] 

Per Cmdlet, he explains what it does and adds a nice example on how-to use the Cmdlet in real life.
If there are any dependencies besides installing powershell 2.0, they are listed.
As a final teaser he also explains how you could do a similar thing with Powershell 1.0

Very nicely done Jonathan, keep up the good work!

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-1-get-random.html Get-Random]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-2-send-mailmessage.html Send-MailMessage]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-3-get-counter.html Get-Counter]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-4-out-gridview.html Out-GridView]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-5-get-hotfix.html Get-Hotfix]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-6-test-connection.html Test-Connection]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-7-reset-computermachinepassword.html Reset-ComputerMachinePassword]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-8-get-module.html Get-Module]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-9-checkpoint-compute.html Checkpoint-Computer]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-10-restar-computer.html Restart-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-11-add-computer.html Add-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-12-write-eventlog.html Write-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-13-clear-eventlog.html Clear-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-14-start-process.html Start-Process]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-15-start-job.html Start-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-16-get-job.html Get-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-17-receive-job.html Receive-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-18-remove-job.html Remove-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-19-stop-job.html Stop-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-20-wait-job.html Wait-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-21-select-xml.html Select-Xml]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-22-enable-computerrestore.html Enable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-23-disable-computerrestore.html Disable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-24-get-computerrestorepoint.html Get-ComputerRestorePoint]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-25-restore-computer.html Restore-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-26-new-webserviceproxy.html New-WebServiceProxy]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-27-test-computersecurechannel.html Test-ComputerSecureChannel]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-28-export-counter.html Export-Counter]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-29-import-counter.html Import-Counter]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-30-enable-psremoting.html Enable-PSRemoting]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-31-enter-pssession.html Enter-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-32-exit-pssession.html Exit-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-33-new-pssession.html New-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-34-invoke-commmand.html Invoke-Command]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-35-new-pssessionoption.html New-PSSessionOption]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-36-get-pssession.html Get-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-37-remove-pssession.html Remove-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-38-get-pssessionconfiguration.html Get-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-39-register-pssessionconfiguration.html Register-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-40-set-pssessionconfiguration.html Set-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-41-disable-pssessionconfiguration.html Disable-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-42-enable-pssessionconfiguration.html Enable-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-43-unregister-pssessionconfiguration.html Unregister-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-44-set-wsmanquickconfig.html Set-WSManQuickConfig]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-45-connect-wsman.html Connect-WSMan]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-46-test-wsman.html Test-WSMan]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-47-invoke-wsmanaction.html Invoke-WSManAction]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-48-get-wsmaninstance.html Get-WSManInstance]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-49-new-wsmaninstance.html New-WSManInstance]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-50-set-wsmaninstance.html Set-WSManInstance]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-51-remove-wsmaninstance.html Remove-WSManInstance]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-52-new-wsmansessionoption.html New-WSManSessionOption]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-53-enable-wsmancredssp.html Enable-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-54-get-wsmancredssp.html Get-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-55-disable-wsmancredssp.html Disable-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-56-disconnect-wsman.html Disconnect-WSMan]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-57-import-pssession.html Import-PSSession]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-58-export-pssession.html Export-PSSession]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-59-set-psbreakpoint.html Set-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-60-get-psbreakpoint.html Get-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-61-disable-psbreakpoint.html Disable-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-62-enable-psbreakpoint.html Enable-PSBreakpoint]


[[Category: Powershell]]</text>
    <sha1>2b2868f93fd609429aa2edfba301336cc6ae4ae5</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>PowerCLI Oneliners: VM Configuration</title>
  <ns>0</ns>
  <id>494</id>
  <revision>
    <id>1114</id>
    <parentid>1081</parentid>
    <timestamp>2009-12-15T16:24:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added guest OS mismatch one liner written by Alan Renouf published at Frank Denneman's blog</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1290" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

* [http://communities.vmware.com/thread/227705 Get VMware Tools version for all VM's]

* [http://technodrone.blogspot.com/2009/08/powercli-storage-vmotion.html Relocate VM using storage VMotion]

* [http://frankdenneman.wordpress.com/2009/12/15/impact-of-mismatch-guest-os-type/ Finding VM's with mismatched Guest OS type]

[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>24c5aaef0c6fe77af3b319b1851a31e8fd33e0b6</sha1>
  </revision>
  <revision>
    <id>1116</id>
    <parentid>1114</parentid>
    <timestamp>2009-12-24T17:04:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added links to Arne Fokkema's Change persistence mode on the Fly article</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1584" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

* [http://communities.vmware.com/thread/227705 Get VMware Tools version for all VM's]

* [http://technodrone.blogspot.com/2009/08/powercli-storage-vmotion.html Relocate VM using storage VMotion]

* [http://frankdenneman.wordpress.com/2009/12/15/impact-of-mismatch-guest-os-type/ Finding VM's with mismatched Guest OS type]

* [http://ict-freak.nl/2009/12/01/powercli-change-persistence-mode-on-the-fly/ Return all the vmdk’s with the Independent Persistent mode enabled]

* [http://ict-freak.nl/2009/12/01/powercli-change-persistence-mode-on-the-fly/ Disable persistent mode for all vmdk's with this mode enabled]


[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>5a45285dc8bc7c7c55df5abc282916053a724ea7</sha1>
  </revision>
  <revision>
    <id>1140</id>
    <parentid>1116</parentid>
    <timestamp>2010-02-24T15:59:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Link to one liner List VM's with CD connected to a Datastore or host device</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1690" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

* [http://communities.vmware.com/thread/227705 Get VMware Tools version for all VM's]

* [http://technodrone.blogspot.com/2009/08/powercli-storage-vmotion.html Relocate VM using storage VMotion]

* [http://frankdenneman.wordpress.com/2009/12/15/impact-of-mismatch-guest-os-type/ Finding VM's with mismatched Guest OS type]

* [http://ict-freak.nl/2009/12/01/powercli-change-persistence-mode-on-the-fly/ Return all the vmdk’s with the Independent Persistent mode enabled]

* [http://ict-freak.nl/2009/12/01/powercli-change-persistence-mode-on-the-fly/ Disable persistent mode for all vmdk's with this mode enabled]

* [http://communities.vmware.com/thread/256747 List VM's with CD connected to a Datastore or host device]

[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>0ca7b9e31da81b1c12fa15b64a9ddf1e9370590f</sha1>
  </revision>
  <revision>
    <id>1141</id>
    <parentid>1140</parentid>
    <timestamp>2010-02-24T23:42:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Another Luc Dekens one liner - Get VM SCSI Card Adapter - Bus Logic or LSI Logic</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1789" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

* [http://communities.vmware.com/thread/227705 Get VMware Tools version for all VM's]

* [http://technodrone.blogspot.com/2009/08/powercli-storage-vmotion.html Relocate VM using storage VMotion]

* [http://frankdenneman.wordpress.com/2009/12/15/impact-of-mismatch-guest-os-type/ Finding VM's with mismatched Guest OS type]

* [http://ict-freak.nl/2009/12/01/powercli-change-persistence-mode-on-the-fly/ Return all the vmdk’s with the Independent Persistent mode enabled]

* [http://ict-freak.nl/2009/12/01/powercli-change-persistence-mode-on-the-fly/ Disable persistent mode for all vmdk's with this mode enabled]

* [http://communities.vmware.com/thread/256747 List VM's with CD connected to a Datastore or host device]

* [http://communities.vmware.com/thread/232209 Get VM SCSI Card Adapter - Bus Logic or LSI Logic]

[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>b9180139a8f548d165c6d634b29ee1b00d658542</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>PowerCLI Oneliners: Host Configuration</title>
  <ns>0</ns>
  <id>493</id>
  <revision>
    <id>1115</id>
    <parentid>1063</parentid>
    <timestamp>2009-12-21T22:53:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to one liner from Hypervizor.fr</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1195" xml:space="preserve">==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.virtu-al.net/2009/08/14/powercli-do-you-have-the-time/ Check that Hosts are using the same NTP Server and that the service is started]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

* [http://www.hypervisor.fr/?p=1687 Move your templates]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>9900df8eb82bdf01152cdca2e7d5f88d5da3af0b</sha1>
  </revision>
  <revision>
    <id>1151</id>
    <parentid>1115</parentid>
    <timestamp>2010-02-28T21:28:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Adding PowerCLI onelines for host network information (virtu-al)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1498" xml:space="preserve">==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.virtu-al.net/2009/09/21/powercli-one-liners-checking-host-network-information/ List all ESX Hosts and their Service console information]

* [http://www.virtu-al.net/2009/09/21/powercli-one-liners-checking-host-network-information/ List all ESX Hosts and their VMotion Enabled Networks]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.virtu-al.net/2009/08/14/powercli-do-you-have-the-time/ Check that Hosts are using the same NTP Server and that the service is started]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

* [http://www.hypervisor.fr/?p=1687 Move your templates]


[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>e10f11ce3be1f9e61b014db9b6af3a5d05861242</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Vmsvc/device.diskadd</title>
  <ns>0</ns>
  <id>158</id>
  <revision>
    <id>1117</id>
    <parentid>1103</parentid>
    <timestamp>2010-01-04T12:45:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to virtualization review</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="617" xml:space="preserve">==== vimsh vmsvc/device.diskadd ====
Usage: device.diskadd vmid size controller-number unit-number datastore

Add a disk to the virtual machine with id vmid.
 Size is the new disk size in kilobytes. 
 Controller number is the controller number as is specified in the vmx configuration file.
 

==== Example ====

vim-cmd vmsvc/device.diskadd 16 5242880 scsi0 2 datastore1

See also: 
* [http://communities.vmware.com/thread/233019 VMTN: vim-cmd vmsvc/device.diskadd syntax headaches]
* [http://virtualizationreview.com/Blogs/Everyday-Virtualization/2009/12/ESX-Add-Disk.aspx Add a disk with ESXi]

[[Category: Vimsh]]</text>
    <sha1>edfb45c4e82ae25b20c2ea0db9b1f16d440571e3</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>User talk:AshcraftJane</title>
  <ns>3</ns>
  <id>510</id>
  <revision>
    <id>1119</id>
    <timestamp>2010-01-06T18:46:43Z</timestamp>
    <contributor>
      <username>AshcraftJane</username>
      <id>34</id>
    </contributor>
    <comment>Created page with 'AshcraftJane  As the adoption of server virtualization continues to accelerate, organizations are looking to reduce the risk, cost and complexities associated with applying tradi...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="984" xml:space="preserve">AshcraftJane

As the adoption of server virtualization continues to accelerate, organizations are looking to reduce the risk, cost and complexities associated with applying traditional disaster recovery methods to virtualized workloads, and maximize the safeguard of application data stored on sprawled virtual machines across the datacenter. To address these pressing customer challenges, the Hitachi Storage Replication Adapter facilitates the linkage between Hitachi’s market-leading array-based replication technologies, including Hitachi Universal Replicator, Hitachi TrueCopy® Synchronous, and Hitachi ShadowImage® in-system replication software, and VMware Site Recovery Manager. Coupled together, these software solutions provide industry-leading operational resilience, robust data protection, recovery management and replication capabilities optimized for VMware infrastructure.

email  tracytasha12@yahoo.com

website: [http://www.essaywriters.net/ online writing jobs]</text>
    <sha1>679a4049fe06b2b1d867e27057babb21b4b66f7b</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>1120</id>
    <parentid>985</parentid>
    <timestamp>2010-02-03T10:00:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1933" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.engr.ucsb.edu/~duonglt/vmware/ William Lam and Tuan Duong's VMware ESX 3.x and ESXi Shell scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

*[http://www.vm4all.com/ Eric Sloof's vm4all VMware Tools Repository]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>1ad02622e8a8d9b105b2a027294268952cf3f90c</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Learning Powershell</title>
  <ns>0</ns>
  <id>511</id>
  <revision>
    <id>1123</id>
    <timestamp>2010-02-11T16:04:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Moving general powershell learning resources to its own page.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="220" xml:space="preserve">==== Powershell books ====

[http://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=df8ed469-9007-401c-85e7-46649a32d0e0 Microsoft Windows PowerShell Quick Reference (Feb 2010)]

[[Category: Powershell]]</text>
    <sha1>d9ce398f4a03fc4faa367937442507c5013f6daa</sha1>
  </revision>
  <revision>
    <id>1125</id>
    <parentid>1123</parentid>
    <timestamp>2010-02-11T16:08:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="449" xml:space="preserve">==== Powershell books ====

[http://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=df8ed469-9007-401c-85e7-46649a32d0e0 Microsoft Windows PowerShell Quick Reference (Feb 2010)]

* [http://blog.sapien.com/index.php/2009/12/01/free-windows-powershell-ebook/ Sapien technologies Free windows Powershell eBook]

==== Powershell Cmdlet Deep Dive ====

* [[Jonathan Medd's Powershell 2.0 One Cmdlet at a time]]


[[Category: Powershell]]</text>
    <sha1>4d1dc6a886ce1672801c91544993949e48271d1f</sha1>
  </revision>
  <revision>
    <id>1126</id>
    <parentid>1125</parentid>
    <timestamp>2010-02-11T16:08:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="451" xml:space="preserve">==== Powershell books ====

* [http://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=df8ed469-9007-401c-85e7-46649a32d0e0 Microsoft Windows PowerShell Quick Reference (Feb 2010)]

* [http://blog.sapien.com/index.php/2009/12/01/free-windows-powershell-ebook/ Sapien technologies Free windows Powershell eBook]

==== Powershell Cmdlet Deep Dive ====

* [[Jonathan Medd's Powershell 2.0 One Cmdlet at a time]]


[[Category: Powershell]]</text>
    <sha1>7f4e3c763763437a46bc398239e5295d0e03a6dd</sha1>
  </revision>
  <revision>
    <id>1128</id>
    <parentid>1126</parentid>
    <timestamp>2010-02-11T16:20:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="494" xml:space="preserve">* [[BEGINNERS PAGE | Beginners page]]


==== Powershell books ====

* [http://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=df8ed469-9007-401c-85e7-46649a32d0e0 Microsoft Windows PowerShell Quick Reference (Feb 2010)]

* [http://blog.sapien.com/index.php/2009/12/01/free-windows-powershell-ebook/ Sapien technologies Free windows Powershell eBook]

==== Powershell Cmdlet Deep Dive ====

* [[Jonathan Medd's Powershell 2.0 One Cmdlet at a time]]


[[Category: Powershell]]</text>
    <sha1>012b58ca40ce68f10dc67e782e5f130728e93820</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Powershell techniques and tips</title>
  <ns>0</ns>
  <id>512</id>
  <revision>
    <id>1130</id>
    <timestamp>2010-02-11T16:26:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>moved general powershell links / tips / articles to its own page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2144" xml:space="preserve">==== General powershell techniques and tips ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

[[Category: Powershell]]</text>
    <sha1>43169f0a1d5afc8a16ef36e02736030c93b771d4</sha1>
  </revision>
  <revision>
    <id>1135</id>
    <parentid>1130</parentid>
    <timestamp>2010-02-15T14:12:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to Dennis Damen his "create MD5 with powershell" script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2215" xml:space="preserve">==== General powershell techniques and tips ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

* [http://www.dennisdamen.com/?p=17 Create MD5 Hash using PowerShell]

[[Category: Powershell]]</text>
    <sha1>bc45d42af129ec9428266a36305a906814bc8ee6</sha1>
  </revision>
  <revision>
    <id>1136</id>
    <parentid>1135</parentid>
    <timestamp>2010-02-15T17:20:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>adding some links to POSH topics</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2609" xml:space="preserve">==== General powershell techniques and tips ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

* [http://www.dennisdamen.com/?p=17 Create MD5 Hash using PowerShell]

* [http://lunex.spaces.live.com/Blog/cns!64CB3857E28BD106!376.entry Multithreading In Powershell Version 2.0]

* [http://www.myitforum.com/myITWiki/(X(1)S(pgqkw0jfcpxe3r550sfpnxyf))/Default.aspx?Page=WPScripts&amp;NS=&amp;AspxAutoDetectCookieSupport=1 windows Powershell script repository]

* [http://powershell.com/cs/blogs/tobias/archive/2010/01/16/cancelling-a-pipeline.aspx Cancelling a Pipeline]

[[Category: Powershell]]</text>
    <sha1>81309d2eeda742a9b3a28efd3773f9f4d8017fc5</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Powershell Tools</title>
  <ns>0</ns>
  <id>513</id>
  <revision>
    <id>1131</id>
    <timestamp>2010-02-11T16:27:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Moved powershell tools to its own page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="368" xml:space="preserve">
==== Powershell tools ====

* [http://www.thevesi.org The Vizioncore Virtualization Ecoshell initiative]

* [http://www.powergui.org Quest Software PowerGUI]

* [http://www.primaltools.com/freetools/ SAPIEN Primalforms] See also [http://blog.sapien.com/index.php/2008/11/03/getting-started-with-primalforms/ Getting started with Primalforms]

[[Category: Powershell]]</text>
    <sha1>ccb865cebdd59c2effc15fcb9dc04005413181ec</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>PowerCLI Oneliners: Statistics</title>
  <ns>0</ns>
  <id>491</id>
  <revision>
    <id>1134</id>
    <parentid>1084</parentid>
    <timestamp>2010-02-14T10:21:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added oneliner from hypervisor.fr list VMs with less then 5% free space</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1131" xml:space="preserve">==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM with least free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]

* [http://www.virtu-al.net/2009/08/27/powercli-one-liners-last-10-vms-created-and-removed/ Last 10 VMs created and removed]

* [http://www.hypervisor.fr/?p=1465 Oneliner: List VM's with less then 5% free space in just a few seconds]


[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>2621220054fb935351fb98d4e1aeabef110e0b54</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>VIOPS VMware Icons and diagrams</title>
  <ns>0</ns>
  <id>469</id>
  <revision>
    <id>1137</id>
    <parentid>949</parentid>
    <timestamp>2010-02-22T11:12:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to Technodrone's visio stencils as the ones on VMware VIOPS are still gone</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="708" xml:space="preserve">Visio stencils made from the artwork as released by the official VMware branding team.
Can be used for documentation, now also includes vSphere artwork.


[http://viops.vmware.com/home/docs/DOC-1514  VIOPS: Visio Stencils for vSphere]
and
http://viops.vmware.com/home/docs/DOC-1338

Unfortunately these visio stencils have disappeared, even after asking the VMTN team about this a couple of months ago, they are still gone.
An alternative can be found here: [http://technodrone.blogspot.com/2009/12/my-visio-stencils-again.html Technodrone: My Visio stencils again] There's a few other places on the web with visio templates, see the category below for more or search for visio.

[[Category: VMware Artwork]]</text>
    <sha1>e8e5269de466942749aea9e3745079c488aad9e4</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>VMware Icons</title>
  <ns>0</ns>
  <id>423</id>
  <revision>
    <id>1138</id>
    <parentid>941</parentid>
    <timestamp>2010-02-22T11:23:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="405" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints seem to have moved to:
http://viops.vmware.com/home/docs/DOC-1338

Correction, when VIOPS moved, the powerpoints have disappeared.

[[Category: VMware Artwork]]</text>
    <sha1>603fa6b6d8a87f0b416ef71218f8888e96f44d88</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>PowerCLI Oneliners: Events</title>
  <ns>0</ns>
  <id>492</id>
  <revision>
    <id>1139</id>
    <parentid>1069</parentid>
    <timestamp>2010-02-24T15:48:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added link to one liner for Who's spying on me in Virtual Center</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="974" xml:space="preserve">==== Events ====

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events per VM]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors from the past 24 hours]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all errors related to a cluster]

* [http://www.peetersonline.nl/index.php/vmware/quick-vi-toolkit-one-liners/ Get all events related to DRS]

* [http://www.peetersonline.nl/index.php/powershell/powershell-oneliner-2/ Hosts whose CPU reached red Load level]

* [http://get-admin.com/blog/?p=725 Inform when running task completes]

* [http://ict-freak.nl/2009/08/20/powercli-reading-the-vmkernel-logfiles-with-powershell-v2 Reading the VMKERNEL logfiles with Powershell v2]

* [http://www.virtualinsanity.com/index.php/2010/02/24/whos-spying-on-me-in-virtual-center/ Who's spying on me in virtual center]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>485a24b80746a9a4b93ea7462a819424d3b6722a</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Install the VI Perl Toolkit on OS X</title>
  <ns>0</ns>
  <id>514</id>
  <revision>
    <id>1143</id>
    <timestamp>2010-02-27T16:51:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Installation notes for installing VI Perl Toolkit on OS X using cpan</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7460" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
// by Wil van Antwerpen //
=== Installing Developer Tools ===
The VI Perl Toolkit needs to get a few extra packages to the perl setup that is by default installed on Mac OS X. In order to get these package we use CPAN.
Perl CPAN has some prerequisites of its own.

For starters your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

=== Getting the Perl VI Toolkit SDK ===
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for OS X Leopard I downloaded the 32 bits .tar.gz linux installer.

Then untar the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the packages we need to install in perl that are missing for the toolkit to work.

=== Installing missing perl dependencies ===
So now we need to setup CPAN unless you already have it working, then you can skip this step.

==== Is /usr/local setup? ====
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

==== Configure CPAN ====
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

=== Install VI Perl Toolkit ===
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.

=== Uninstall Developer Tools and cleaning up CPAN ===

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is sometimes needed if a module gets stuck while trying to install it.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

=== External links ===

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]</text>
    <sha1>d028b150f3f4a4f99b37761933af3ddce60df83c</sha1>
  </revision>
  <revision>
    <id>1144</id>
    <parentid>1143</parentid>
    <timestamp>2010-02-27T16:59:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7458" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 
== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra packages to the perl setup that is by default installed on Mac OS X. In order to get these package we use CPAN.
Perl CPAN has some prerequisites of its own.

For starters your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for OS X Leopard I downloaded the 32 bits .tar.gz linux installer.

Then untar the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the packages we need to install in perl that are missing for the toolkit to work.

== Installing missing perl dependencies ==
So now we need to setup CPAN unless you already have it working, then you can skip this step.

== Is /usr/local setup? ==
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

== Configure CPAN ==
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

== Installing the VI Perl Toolkit dependencies ==

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is sometimes needed if a module gets stuck while trying to install it.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>25af5e665975c8b4d7cffccfae2778ffac4580d1</sha1>
  </revision>
  <revision>
    <id>1145</id>
    <parentid>1144</parentid>
    <timestamp>2010-02-27T19:19:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Adding how-to setup using MacPorts (more details will follow... )</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8337" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 

Basically there are two ways in which you can get the VI Perl Toolkit working on OS X. 
One way is by using the CPAN functionality of Perl which is already installed on your Mac and the other way is by using Macports. 
I will first walk you through how-to this using the CPAN Network and then show you how to get it working using macports.
You will only need to use one method in order to use the Toolkit.

== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra modules added to the current perl setup that is by default installed on Mac OS X. In order to get these modules we use CPAN or macPorts.
Both have some prerequisites of their own.

For starters your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for OS X Leopard I downloaded the 32 bits .tar.gz linux installer.

Then untar the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the packages we need to install in perl that are missing for the toolkit to work.

== Installing missing perl dependencies ==
So now we need to setup CPAN or MacPorts unless you already have it working, in that case you can skip the installation part.

=== CPAN: Is /usr/local setup? ===
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

=== CPAN: Configuration ===
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== CPAN: Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

=== Setting up MacPorts ===
Go to the [http://www.macports.org/install.php Macports install page] and download the .dmg file for your environment and run the installer.
=== MacPorts: Installing the VI Perl Toolkit dependencies ===

== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

Be aware that you can then no longer use CPAN or Macports to extend your system!

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is a troubleshoot step and sometimes needed if a module gets stuck while trying to install it.
Again don't remove any module your install depends on.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>ee58d186d0675a9de430307f6e66fa2e86cf2c2b</sha1>
  </revision>
  <revision>
    <id>1146</id>
    <parentid>1145</parentid>
    <timestamp>2010-02-27T19:45:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Added more steps on the MacPorts way of doing this.. Its so much smoother to use MacPorts...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8815" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 

Basically there are two ways in which you can get the VI Perl Toolkit working on OS X. 

One way is by using the CPAN functionality of Perl which is already installed on your Mac and the other way is by using [http://www.macports.org/ MacPorts]. 
I will first walk you through how-to this using the CPAN Network and then show you how to get it working using macports.

Obviously, you will only need to use one of these methods in order to use the Toolkit.

== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra modules added to the current perl setup that is by default installed on Mac OS X. In order to get these modules we use CPAN or macPorts.
Both have some prerequisites of their own and in this case it is the same for both.

Your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for both OS X Leopard and Snow Leopard I downloaded the same 32 bits .tar.gz linux installer.

After downloading unpack the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the modules we need to install in perl that are missing for the toolkit to work.
So we are going to install these modules first, before we can continue with our main installation.

== Installing missing perl dependencies ==
So now we need to setup CPAN or MacPorts unless you already have it working, in that case you can skip the installation part.

=== CPAN: Is /usr/local setup? ===
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

=== CPAN: Configuration ===
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== CPAN: Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

=== Setting up MacPorts ===
Go to the [http://www.macports.org/install.php Macports install page] and download the .dmg file for your environment and run the installer.
=== MacPorts: Installing the VI Perl Toolkit dependencies ===

 sudo port install p5-class-methodmaker
On my Snow Leopard machine, this dragged in a complete new version of Perl (5.8.9), very nice.
Then we need Crypt::SSLeay
 sudo port install p5-crypt-ssleay
and SOAP::Lite
 sudo port install p5-soap-lite
Finally UUID


== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

Be aware that you can then no longer use CPAN or Macports to extend your system!

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is a troubleshoot step and sometimes needed if a module gets stuck while trying to install it.
Again don't remove any module your install depends on.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>c130632d197c08466ea296f9a3f94e761f4f55bb</sha1>
  </revision>
  <revision>
    <id>1147</id>
    <parentid>1146</parentid>
    <timestamp>2010-02-27T20:04:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9132" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 

Basically there are two ways in which you can get the VI Perl Toolkit working on OS X. 

One way is by using the CPAN functionality of Perl which is already installed on your Mac and the other way is by using [http://www.macports.org/ MacPorts]. 
I will first walk you through how-to this using the CPAN Network and then show you how to get it working using macports.

Obviously, you will only need to use one of these methods in order to use the Toolkit.

== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra modules added to the current perl setup that is by default installed on Mac OS X. In order to get these modules we use CPAN or macPorts.
Both have some prerequisites of their own and in this case it is the same for both.

Your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for both OS X Leopard and Snow Leopard I downloaded the same 32 bits .tar.gz linux installer.

After downloading unpack the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the modules we need to install in perl that are missing for the toolkit to work.
So we are going to install these modules first, before we can continue with our main installation.

== Installing missing perl dependencies ==
So now we need to setup CPAN or MacPorts unless you already have it working, in that case you can skip the installation part.

=== CPAN: Is /usr/local setup? ===
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

=== CPAN: Configuration ===
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== CPAN: Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

=== Setting up MacPorts ===
Go to the [http://www.macports.org/install.php Macports install page] and download the .dmg file for your environment and run the installer.
=== MacPorts: Installing the VI Perl Toolkit dependencies ===

 sudo port install p5-class-methodmaker
On my Snow Leopard machine, this dragged in a complete new version of Perl (5.8.9), very nice.
Then we need Crypt::SSLeay
 sudo port install p5-crypt-ssleay
and SOAP::Lite
 sudo port install p5-soap-lite
Finally UUID
 sudo port install p5-uuid

Now as I said it pulled in its own perl environment... so it turns out that we need to add another module which is missing.
 sudo part install p5-xml-libxml

Woww this was quick and we can now get back to installing the VI Perl Toolkit

== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 
For CPAN:
 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit
For MacPorts:
 /opt/local/bin/perl MakeFile.pl

That UUID is not yet version 0.03 seems to be OK
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

Be aware that you can then no longer use CPAN or Macports to extend your system!

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is a troubleshoot step and sometimes needed if a module gets stuck while trying to install it.
Again don't remove any module your install depends on.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>881edc1a048ef3fd096e76401f7395c3e1701a4a</sha1>
  </revision>
  <revision>
    <id>1148</id>
    <parentid>1147</parentid>
    <timestamp>2010-02-27T21:42:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9365" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 

Basically there are two ways in which you can get the VI Perl Toolkit working on OS X. 

One way is by using the CPAN functionality of Perl which is already installed on your Mac and the other way is by using [http://www.macports.org/ MacPorts]. 
I will first walk you through how-to this using the CPAN Network and then show you how to get it working using macports.

Obviously, you will only need to use one of these methods in order to use the Toolkit.

== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra modules added to the current perl setup that is by default installed on Mac OS X. In order to get these modules we use CPAN or macPorts.
Both have some prerequisites of their own and in this case it is the same for both.

Your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for both OS X Leopard and Snow Leopard I downloaded the same 32 bits .tar.gz linux installer.

After downloading unpack the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the modules we need to install in perl that are missing for the toolkit to work.
So we are going to install these modules first, before we can continue with our main installation.

== Installing missing perl dependencies ==
So now we need to setup CPAN or MacPorts unless you already have it working, in that case you can skip the installation part.

=== CPAN: Is /usr/local setup? ===
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

=== CPAN: Configuration ===
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== CPAN: Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

=== Setting up MacPorts ===
Go to the [http://www.macports.org/install.php Macports install page] and download the .dmg file for your environment and run the installer.
=== MacPorts: Installing the VI Perl Toolkit dependencies ===

 sudo port install p5-class-methodmaker
On my Snow Leopard machine, this dragged in a complete new version of Perl (5.8.9), very nice.
Then we need Crypt::SSLeay
 sudo port install p5-crypt-ssleay
and SOAP::Lite
 sudo port install p5-soap-lite
Finally UUID
 sudo port install p5-uuid

Now as I said it pulled in its own perl environment... so it turns out that we need to add another module which is missing.
 sudo part install p5-xml-libxml

Woww this was quick and we can now get back to installing the VI Perl Toolkit, but first close your terminal as you need to restart that one in order to use the new Perl version installed in /opt/local/bin instead of the default one which is still in /usr/bin

== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK (On Snow Leopard it is 0.04)
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.
You may want to keep the makefile around if you later want to uninstall this.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

Be aware that you can then no longer use CPAN or Macports to extend your system!

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is a troubleshoot step and sometimes needed if a module gets stuck while trying to install it.
Again don't remove any module your install depends on.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>52f219bfd6cf9d9e496f2423c8b4c1efe90c5efb</sha1>
  </revision>
  <revision>
    <id>1149</id>
    <parentid>1148</parentid>
    <timestamp>2010-02-27T21:44:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Added note to use CPAN method, as the MacPorts method of installing doesn't work for me (yet)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9453" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 

Basically there are two ways in which you can get the VI Perl Toolkit working on OS X. 

One way is by using the CPAN functionality of Perl which is already installed on your Mac and the other way is by using [http://www.macports.org/ MacPorts]. 
I will first walk you through how-to this using the CPAN Network and then show you how to get it working using macports.

Obviously, you will only need to use one of these methods in order to use the Toolkit.
FOR THE MOMENT I SUGGEST USING THE CPAN METHOD as MacPorts is still giving me problems.

== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra modules added to the current perl setup that is by default installed on Mac OS X. In order to get these modules we use CPAN or macPorts.
Both have some prerequisites of their own and in this case it is the same for both.

Your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for both OS X Leopard and Snow Leopard I downloaded the same 32 bits .tar.gz linux installer.

After downloading unpack the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the modules we need to install in perl that are missing for the toolkit to work.
So we are going to install these modules first, before we can continue with our main installation.

== Installing missing perl dependencies ==
So now we need to setup CPAN or MacPorts unless you already have it working, in that case you can skip the installation part.

=== CPAN: Is /usr/local setup? ===
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

=== CPAN: Configuration ===
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== CPAN: Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

=== Setting up MacPorts ===
Go to the [http://www.macports.org/install.php Macports install page] and download the .dmg file for your environment and run the installer.
=== MacPorts: Installing the VI Perl Toolkit dependencies ===

 sudo port install p5-class-methodmaker
On my Snow Leopard machine, this dragged in a complete new version of Perl (5.8.9), very nice.
Then we need Crypt::SSLeay
 sudo port install p5-crypt-ssleay
and SOAP::Lite
 sudo port install p5-soap-lite
Finally UUID
 sudo port install p5-uuid

Now as I said it pulled in its own perl environment... so it turns out that we need to add another module which is missing.
 sudo part install p5-xml-libxml

Woww this was quick and we can now get back to installing the VI Perl Toolkit, but first close your terminal as you need to restart that one in order to use the new Perl version installed in /opt/local/bin instead of the default one which is still in /usr/bin

== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK (On Snow Leopard it is 0.04)
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.
You may want to keep the makefile around if you later want to uninstall this.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

Be aware that you can then no longer use CPAN or Macports to extend your system!

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is a troubleshoot step and sometimes needed if a module gets stuck while trying to install it.
Again don't remove any module your install depends on.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>504205bd3e1c64fba4d367d1f98e08ee6bdc367a</sha1>
  </revision>
  <revision>
    <id>1150</id>
    <parentid>1149</parentid>
    <timestamp>2010-02-27T21:44:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9454" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 

Basically there are two ways in which you can get the VI Perl Toolkit working on OS X. 

One way is by using the CPAN functionality of Perl which is already installed on your Mac and the other way is by using [http://www.macports.org/ MacPorts]. 
I will first walk you through how-to this using the CPAN Network and then show you how to get it working using macports.

Obviously, you will only need to use one of these methods in order to use the Toolkit.

FOR THE MOMENT I SUGGEST USING THE CPAN METHOD as MacPorts is still giving me problems.

== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra modules added to the current perl setup that is by default installed on Mac OS X. In order to get these modules we use CPAN or macPorts.
Both have some prerequisites of their own and in this case it is the same for both.

Your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for both OS X Leopard and Snow Leopard I downloaded the same 32 bits .tar.gz linux installer.

After downloading unpack the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the modules we need to install in perl that are missing for the toolkit to work.
So we are going to install these modules first, before we can continue with our main installation.

== Installing missing perl dependencies ==
So now we need to setup CPAN or MacPorts unless you already have it working, in that case you can skip the installation part.

=== CPAN: Is /usr/local setup? ===
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

=== CPAN: Configuration ===
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== CPAN: Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

=== Setting up MacPorts ===
Go to the [http://www.macports.org/install.php Macports install page] and download the .dmg file for your environment and run the installer.
=== MacPorts: Installing the VI Perl Toolkit dependencies ===

 sudo port install p5-class-methodmaker
On my Snow Leopard machine, this dragged in a complete new version of Perl (5.8.9), very nice.
Then we need Crypt::SSLeay
 sudo port install p5-crypt-ssleay
and SOAP::Lite
 sudo port install p5-soap-lite
Finally UUID
 sudo port install p5-uuid

Now as I said it pulled in its own perl environment... so it turns out that we need to add another module which is missing.
 sudo part install p5-xml-libxml

Woww this was quick and we can now get back to installing the VI Perl Toolkit, but first close your terminal as you need to restart that one in order to use the new Perl version installed in /opt/local/bin instead of the default one which is still in /usr/bin

== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK (On Snow Leopard it is 0.04)
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.
You may want to keep the makefile around if you later want to uninstall this.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

Be aware that you can then no longer use CPAN or Macports to extend your system!

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is a troubleshoot step and sometimes needed if a module gets stuck while trying to install it.
Again don't remove any module your install depends on.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>0670b54c0a53f99c1e3dcce5c690e30a8ee371d4</sha1>
  </revision>
</page>
<page arvcontinue="20090925130137|1104">
  <title>Hostsvc/net/config load</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>1153</id>
    <parentid>250</parentid>
    <timestamp>2010-03-02T20:12:37Z</timestamp>
    <contributor>
      <username>Jennnyjordan</username>
      <id>35</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="146" xml:space="preserve">'''Guidelines on writing Essays'''
I found this site that help me through writing [http://www.research-service.com research papers] for my reports</text>
    <sha1>13d43193b4c665ee389c236d5124507ca1e0d962</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>PowerCLI Oneliners: Host Configuration</title>
  <ns>0</ns>
  <id>493</id>
  <revision>
    <id>1154</id>
    <parentid>1151</parentid>
    <timestamp>2010-03-02T21:37:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1603" xml:space="preserve">==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.virtu-al.net/2009/09/21/powercli-one-liners-checking-host-network-information/ List all ESX Hosts and their Service console information]

* [http://www.virtu-al.net/2009/09/21/powercli-one-liners-checking-host-network-information/ List all ESX Hosts and their VMotion Enabled Networks]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.virtu-al.net/2009/08/14/powercli-do-you-have-the-time/ Check that Hosts are using the same NTP Server and that the service is started]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

* [http://www.hypervisor.fr/?p=1687 Move your templates]

* [http://www.vmwarescripting.com/index.php/topic,1302.0.html Add/Change DNS suffix's on your ESX hosts]


[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>e615d0e6fb0793cdbdbb0fe437f2217ad729d4da</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Hostsvc/net/config load</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>1155</id>
    <parentid>1153</parentid>
    <timestamp>2010-03-03T11:11:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Jennnyjordan|Jennnyjordan]] ([[User talk:Jennnyjordan|Talk]]) to last version by [[User:Wila|Wila]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="147" xml:space="preserve">==== vimsh hostsvc/net/config_load ====
Usage: config_load filename

Loads a network configuration from a file and updates it.

[[Category: Vimsh]]</text>
    <sha1>aad43ba4921b5b7f7a5d61d827507f53cdc229ad</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Install the VI Perl Toolkit on OS X</title>
  <ns>0</ns>
  <id>514</id>
  <revision>
    <id>1156</id>
    <parentid>1150</parentid>
    <timestamp>2010-03-12T21:00:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>highlighted to NOT use MacPorts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9603" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 

Basically there are two ways in which you can get the VI Perl Toolkit working on OS X. 

One way is by using the CPAN functionality of Perl which is already installed on your Mac and the other way is by using [http://www.macports.org/ MacPorts]. 
I will first walk you through how-to this using the CPAN Network and then show you how to get it working using macports.

Obviously, you will only need to use one of these methods in order to use the Toolkit.

''' I SUGGEST USING THE CPAN METHOD and not install MacPorts if you can as MacPorts will give you problems due to it changing paths and installing its own complete perl environment. I will remove the MacPort parts of the notes ASAP. '''

== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra modules added to the current perl setup that is by default installed on Mac OS X. In order to get these modules we use CPAN or macPorts.
Both have some prerequisites of their own and in this case it is the same for both.

Your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for both OS X Leopard and Snow Leopard I downloaded the same 32 bits .tar.gz linux installer.

After downloading unpack the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the modules we need to install in perl that are missing for the toolkit to work.
So we are going to install these modules first, before we can continue with our main installation.

== Installing missing perl dependencies ==
So now we need to setup CPAN or MacPorts unless you already have it working, in that case you can skip the installation part.

=== CPAN: Is /usr/local setup? ===
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
See if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we create the folder, but as you will see its owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

=== CPAN: Configuration ===
With the developer tools setup now you have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools finds the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== CPAN: Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful so we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

=== Setting up MacPorts ===
Go to the [http://www.macports.org/install.php Macports install page] and download the .dmg file for your environment and run the installer.
=== MacPorts: Installing the VI Perl Toolkit dependencies ===

 sudo port install p5-class-methodmaker
On my Snow Leopard machine, this dragged in a complete new version of Perl (5.8.9), very nice.
Then we need Crypt::SSLeay
 sudo port install p5-crypt-ssleay
and SOAP::Lite
 sudo port install p5-soap-lite
Finally UUID
 sudo port install p5-uuid

Now as I said it pulled in its own perl environment... so it turns out that we need to add another module which is missing.
 sudo part install p5-xml-libxml

Woww this was quick and we can now get back to installing the VI Perl Toolkit, but first close your terminal as you need to restart that one in order to use the new Perl version installed in /opt/local/bin instead of the default one which is still in /usr/bin

== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK (On Snow Leopard it is 0.04)
With this version of the toolkit, there are no tests defined for the make file so install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.
You may want to keep the makefile around if you later want to uninstall this.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

Be aware that you can then no longer use CPAN or Macports to extend your system!

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is a troubleshoot step and sometimes needed if a module gets stuck while trying to install it.
Again don't remove any module your install depends on.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>2f1c156680de70c9c0c0b53e432413d0f0ec05af</sha1>
  </revision>
  <revision>
    <id>1157</id>
    <parentid>1156</parentid>
    <timestamp>2010-03-14T09:15:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Completely removed the MacPorts steps as they didn't turn out to work</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8603" xml:space="preserve">== Installing the VI Perl Toolkit on OS X ==
'' by Wil van Antwerpen '' 

This document describes the preferred way on how-to get the VI Perl Toolkit working on OS X. 

We are doing this by using the CPAN functionality of Perl which is already installed on your Mac.
I will walk you through how-to set this up from the start using the CPAN Network.

''' We have also tried to do this by using [http://www.macports.org/ MacPorts].  but as it turns out MacPorts will give you problems due to it changing paths and installing its own complete perl environment. For now we are not aware of a way to use the toolkit using Macports. '''

== Installing Developer Tools ==
The VI Perl Toolkit needs to get a few extra modules added to the current perl setup that is by default installed on Mac OS X. In order to get these modules we use CPAN.
CPAN has some prerequisites of its own that we are going to have to satisfy first.

The main issue is that your system must have "make" installed.
The most straightforward way to get that package installed is to take your original OS X installation disk and install Developer Tools (XcodeTools.mpkg) which can be found under Option Installs on the DVD.
Just keep the default settings and you'll be fine.

It is a bit big though (over 2GB) so it is a steep requirement for just getting the VI Perl toolkit to work OK. If you don't have the space, the part from the developer tools that is needed is the BSD "make" command and a number of other commands. It should be sufficient to install the UNIX Development Support (or BSD SDK) sub-package of the Developer Tools.

== Getting the Perl VI Toolkit SDK ==
First step is to download the latest perl SDK from:
http://communities.vmware.com/community/developer/forums/vsphere_sdk_perl

for both OS X Leopard and Snow Leopard I downloaded the same 32 bits .tar.gz linux installer.

After downloading unpack the archive by running
 tar -xvzf VMware-vSphere-SDK-for-Perl-4.0.0-161974.i386.tar.gz 
from the command line.
cd into the new vmware-vsphere-cli-distrib/ folder
 cd vmware-vsphere-cli-distrib/
and run:
 perl MakeFile.pl
this will most likely return the following warnings:
 Warning: prerequisite Class::MethodMaker 2.08 not found.
 Warning: prerequisite Crypt::SSLeay 0.51 not found.
 Warning: prerequisite SOAP::Lite 0.67 not found.
 Warning: prerequisite UUID 0.03 not found.
 Writing Makefile for VIPerlToolkit
The warnings we see here are the modules we need to install for perl that are missing in order for getting the toolkit to work.
So we are going to install these modules first, before we can continue with our main installation.

== Installing missing perl dependencies ==
So now we need to setup CPAN unless you already have CPAN working, in that case you can skip the installation part.

=== CPAN: Is /usr/local setup? ===
By default cpan will try to install some documentation under the /usr/local folder, so this folder has to exist and it needs to have the correct ownership privileges setup.
Check if the folder already exists:
 $ ls /usr/
 X11		bin		lib		sbin		standalone
 X11R6		include		libexec		share
In my case it isn't there yet, so create it:
 $ mkdir /usr/local
 mkdir: /usr/local: Permission denied
Ha!.. you can't create the folder unless you have elevated rights (of course)
 $ sudo mkdir /usr/local
 Password:
So now we created the folder, but as you will see it is owned by root and we can't install our packages in there unless we allow our user. 
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 root  wheel    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 root  wheel   408B Feb 27 01:06 ..
In my case the username is "topaz", replace "topaz" with your username below:
 $ sudo chown topaz:topaz /usr/local
 $ ls -alh /usr/local
 total 0
 drwxr-xr-x   2 topaz topaz    68B Feb 27 01:06 .
 drwxr-xr-x@ 12 topaz topaz   408B Feb 27 01:06 ..

=== CPAN: Configuration ===
With the developer tools setup you now have to configure CPAN. You can also use this step if you want to change your CPAN configuration.
Configuring CPAN makes sure that the tools find the necessary commands on your system (make et al). To do that, run:

 perl -MCPAN -e shell
 cpan&gt; o conf init

This throws up a bunch of questions. 
 /Users/topaz/.cpan/CPAN/MyConfig.pm initialized.
 
 
 CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate  the same contents all around the globe. Many countries have at least one CPAN site already. The  resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly.
 
 If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.)
 
 Are you ready for manual configuration? [yes]
You can take the defaults for pretty much all of them, so just press enter.
It is fine if the configuration script doesn't find programs for things like lynx, wget, ncftp, ftp etcetera...

The main things to select are country to download from and the site(s) which you want to use for the repositories. Just make the most logical selections here.

=== CPAN: Installing the VI Perl Toolkit dependencies ===

Now we'll get the missing dependencies by running them one by one. We could add all of these on a single line, but we want it to be easy to see if the install was successful. This is why we are running them one by one. 
 cpan Class::MethodMaker
this should now end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
  /usr/bin/make install  -- OK

So continue with the next one:

 cpan Crypt::SSLeay 
Just choose the defaults if questions are asked. As long as it ends like the previous package you are fine.

Next up is:
 cpan SOAP::Lite
Same same, choose defaults. In my setup it nagged that I missed out on some dependencies of its own and if I wanted to add those.. Sure.. let the installer add anything it suggests.

Finally:
 cpan UUID
Which down here installed fine too, so now we can finally get back to installing the VI Perl Toolkit.

== Install VI Perl Toolkit ==
Now go back to the folder where you unpacked the VI Perl Toolkit: 

 perl MakeFile.pl
 Warning: prerequisite UUID 0.03 not found. We have 0.020.
 Writing Makefile for VIPerlToolkit

That UUID is not yet version 0.03 seems to be OK (On Snow Leopard it is 0.04)
With this version of the toolkit, there are no tests defined for the make file so we are going to install it directly:

 sudo make install
 Password:
 Manifying blib/man3/VMware::VIM25Runtime.3pm
 Manifying blib/man3/VMware::VIM2Stub.3pm
 Manifying blib/man3/VMware::VIM25Stub.3pm
 Manifying blib/man3/VMware::VIM2Runtime.3pm
 Installing /Library/Perl/5.8.8/vmware-install.pl
 Installing /Library/Perl/5.8.8/VMware/VICommon.pm
 Installing /Library/Perl/5.8.8/VMware/VICredStore.pm
 ....
  many more lines here
 ....
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/vm/vmunregister.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/checksensorhealth.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/firmwarerevisions.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listfrus.pl
 Installing /usr/share/doc/vmware-viperl/doc/samples/WSMan/listpowersupplies.pl

and that's how a successful Perl Toolkit install looks like.

If you want you can now delete your unpacked setup files and VI Perl tar.gz file.
You may want to keep the makefile around if you later want to uninstall this.

== Uninstall Developer Tools and cleaning up CPAN ==

If you want to uninstall the Developer Tools, you need to run the command:
 /Developer/Library/uninstall-devtools --mode=all

Be aware that you can then no longer use CPAN or Macports to extend your system!

From CPAN you can remove an installed module by running a clean command. 
Such as:
 cpan clean Class::MethodMaker

This is a troubleshoot step and sometimes needed if a module gets stuck while trying to install it.
Again don't remove any module your install depends on.

If CPAN still gives problems, then you can remove your local CPAN configuration and cache directory by running:
 rm -r ~/.cpan

== External link ==

The following link turned out to be very helpful while I was trying to get this to work:

[http://itknowledgeexchange.techtarget.com/virtualization-pro/managing-vi3-from-os-x-1051-leopard/ Managing VMware Infrastructure 3 (VI3) from OS X (10.5.1 Leopard)]

[[Category: Perl]]</text>
    <sha1>8e39cf0b0b1a559a1572fa12bb37d8d373f7e18c</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Perl</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>1158</id>
    <parentid>1142</parentid>
    <timestamp>2010-03-14T09:57:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="616" xml:space="preserve">==== Learning more about Perl and the SDK ====
[http://communities.vmware.com/docs/DOC-10837 Getting Started with the vSphere SDK for Perl]

[http://www.perl.org/docs.html Perl.org Online Documentation]

[[Install the VI Perl Toolkit on OS X]]

[[Install vGhetto on OS X]]

==== Scripts ====
[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]

[[Listing all VM's in a cluster]]

[[Rename local storage datastore]]

[[Factory Reset of ESXi]]

[[Category: Perl]]</text>
    <sha1>7662d786e0d989c79e7548078bdd62923682c574</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Install vGhetto on OS X</title>
  <ns>0</ns>
  <id>515</id>
  <revision>
    <id>1159</id>
    <timestamp>2010-03-14T10:10:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Run vGhetto on OS X</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4901" xml:space="preserve">==== First steps ====
In order to install the [http://bit.ly/vGhettoGUI vGhetto client] and to be able to run all of its accompanied scripts, you'll have to install the VI Perl Toolkit. 
So follow the installation tips for that here [[Install the VI Perl Toolkit on OS X]]

==== Graphical environment ====
The vGhetto client uses a graphical user interface and because of that, it has a dependency on the X11 server.
Starting with OS X Leopard, this is included in the default install of OS X. So unless you are experiencing some real problems getting things to work I would not update X11 server. It is added to the steps below because you might have to redo it depending on your current setup.

==== Install module Tk ====
vGhetto uses the perl module Tk for the graphical environment, so this is one of the main dependencies.
You can install it by running:
 cpan Tk
During the install you'll see many displays popup to test the functionality from tk, that's normal.
If you are extremely lucky it ends with OK..., but if you are like me you'll get:
 Failed Test     Stat Wstat Total Fail  Failed  List of Failed
 -------------------------------------------------------------------------------
 t/canvas.t         1   256   158    1   0.63%  84
 t/coloreditor.t  255 65280     8   11 137.50%  3-8
 t/wm-tcl.t         1   256   315    1   0.32%  240
  (37 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 161 subtests skipped.
 Failed 3/62 test scripts, 95.16% okay. 8/3686 subtests failed, 99.78% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

''' If that's your result too, then skip the next few steps as it is expected that a few test scripts will fail '''

Turns out I still had an X11 Server installed from tiger.
 XQuartz 2.1.6 (xorg-server 1.4.2-apple33

So from the DVD, go to option installs and select Optional Installs.mpkg :
In the applications part select X11.

==== Remove X11 ====
Messed it up, got confused, want to start over?

Before you start deleting anything, make sure you have a Leopard's installation DVD available and downloaded the latest X11 package from the Xquartz Project.

* Delete pretty much all X11 from you system, and let it forget its receipts:

Code:

 sudo rm -rf /usr/X11 /usr/X11R6
 sudo pkgutil --forget com.apple.pkg.X11DocumentationLeo
 sudo pkgutil --forget com.apple.pkg.X11User
 sudo pkgutil --forget com.apple.pkg.X11SDKLeo
 sudo pkgutil --forget org.x.X11.pkg

* Install X11User.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Install/Optional Installs.mpkg

* Install X11SDK.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Installs/Xcode Tools/Packages/

* Install [http://xquartz.macosforge.org/trac/wiki/Releases the latest X11 package] release from the Xquartz Project.

===== Install Tk second try =====
After installing X11 2.4.0 from the xquartz project, trying to install Tk gives even more errors:

  (32 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 173 subtests skipped.
 Failed 22/62 test scripts, 64.52% okay. 1258/3686 subtests failed, 65.87% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

===== Install Tk third try =====
So much fun, after following the complete removal steps from X11 and only installing the default Leopard parts (not the quartz update) and rerunning the cpan Tk setup. Now I'm getting:

  (37 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 161 subtests skipped.
 Failed 4/62 test scripts, 93.55% okay. 9/3686 subtests failed, 99.76% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

Well maybe having 4 failed tests is not so bad?

==== Force feeding tk-perl ====

If you scroll up on the part where we're trying to install Tk via cpan, then you'll see right at the top something along these lines: 
 /Users/topaz/.cpan/sources/authors/id/S/SR/SREZIC/Tk-804.028.tar.gz
So our Tk version is Tk-804.028
Move to our build folder:
 cd /Users/topaz/.cpan/build/Tk-804.028
Now install by running:
 sudo make install
If there's no complaint after that, you should be OK

==== time-modules ====
 cpan Time::ParseDate

This should install the time-modules library and if it works OK, you should see this step end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
   /usr/bin/make install  -- OK


==== Done ====
That's it. With all of these requirements in place, you should now be able to run the vGhetto client directly from OS X by running:
 ./vGhetto.pl
(You might have to make vGhetto.pl executable first by executing "chmod +x vGhetto.pl" )</text>
    <sha1>50f52e97875543eb3046c1db8d9d4ce3fa0187ff</sha1>
  </revision>
  <revision>
    <id>1160</id>
    <parentid>1159</parentid>
    <timestamp>2010-03-14T10:11:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4903" xml:space="preserve">==== First steps ====
In order to install the [http://bit.ly/vGhettoGUI vGhetto client] and to be able to run all of its accompanied scripts, you'll have to install the VI Perl Toolkit. 
So follow the installation tips for that here [[Install the VI Perl Toolkit on OS X]]

==== Graphical environment ====
The vGhetto client uses a graphical user interface and because of that, it has a dependency on the X11 server.
Starting with OS X Leopard, this is included in the default install of OS X. So unless you are experiencing some real problems getting things to work I would not update X11 server. It is added to the steps below because you might have to redo it depending on your current setup.

==== Install module Tk ====
vGhetto uses the perl module Tk for the graphical environment, so this is one of the main dependencies.
You can install it by running:
 cpan Tk
During the install you'll see many displays popup to test the functionality from tk, that's normal.
If you are extremely lucky it ends with OK..., but if you are like me you'll get:
 Failed Test     Stat Wstat Total Fail  Failed  List of Failed
 -------------------------------------------------------------------------------
 t/canvas.t         1   256   158    1   0.63%  84
 t/coloreditor.t  255 65280     8   11 137.50%  3-8
 t/wm-tcl.t         1   256   315    1   0.32%  240
  (37 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 161 subtests skipped.
 Failed 3/62 test scripts, 95.16% okay. 8/3686 subtests failed, 99.78% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

''' If that's your result too, then skip the next few steps as it is expected that a few test scripts will fail '''

Turns out I still had an X11 Server installed from tiger.
 XQuartz 2.1.6 (xorg-server 1.4.2-apple33

So from the DVD, go to option installs and select Optional Installs.mpkg :
In the applications part select X11.

===== Remove X11 =====
Messed it up, got confused, want to start over?

Before you start deleting anything, make sure you have a Leopard's installation DVD available and downloaded the latest X11 package from the Xquartz Project.

* Delete pretty much all X11 from you system, and let it forget its receipts:

Code:

 sudo rm -rf /usr/X11 /usr/X11R6
 sudo pkgutil --forget com.apple.pkg.X11DocumentationLeo
 sudo pkgutil --forget com.apple.pkg.X11User
 sudo pkgutil --forget com.apple.pkg.X11SDKLeo
 sudo pkgutil --forget org.x.X11.pkg

* Install X11User.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Install/Optional Installs.mpkg

* Install X11SDK.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Installs/Xcode Tools/Packages/

* Install [http://xquartz.macosforge.org/trac/wiki/Releases the latest X11 package] release from the Xquartz Project.

===== Install Tk second try =====
After installing X11 2.4.0 from the xquartz project, trying to install Tk gives even more errors:

  (32 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 173 subtests skipped.
 Failed 22/62 test scripts, 64.52% okay. 1258/3686 subtests failed, 65.87% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

===== Install Tk third try =====
So much fun, after following the complete removal steps from X11 and only installing the default Leopard parts (not the quartz update) and rerunning the cpan Tk setup. Now I'm getting:

  (37 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 161 subtests skipped.
 Failed 4/62 test scripts, 93.55% okay. 9/3686 subtests failed, 99.76% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

Well maybe having 4 failed tests is not so bad?

==== Force feeding tk-perl ====

If you scroll up on the part where we're trying to install Tk via cpan, then you'll see right at the top something along these lines: 
 /Users/topaz/.cpan/sources/authors/id/S/SR/SREZIC/Tk-804.028.tar.gz
So our Tk version is Tk-804.028
Move to our build folder:
 cd /Users/topaz/.cpan/build/Tk-804.028
Now install by running:
 sudo make install
If there's no complaint after that, you should be OK

==== time-modules ====
 cpan Time::ParseDate

This should install the time-modules library and if it works OK, you should see this step end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
   /usr/bin/make install  -- OK


==== Done ====
That's it. With all of these requirements in place, you should now be able to run the vGhetto client directly from OS X by running:
 ./vGhetto.pl
(You might have to make vGhetto.pl executable first by executing "chmod +x vGhetto.pl" )</text>
    <sha1>2bda11157091aeb5f9cf7b0be3f3e5a208d2bd74</sha1>
  </revision>
  <revision>
    <id>1161</id>
    <parentid>1160</parentid>
    <timestamp>2010-03-14T11:36:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>forgot to add category Perl</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4923" xml:space="preserve">==== First steps ====
In order to install the [http://bit.ly/vGhettoGUI vGhetto client] and to be able to run all of its accompanied scripts, you'll have to install the VI Perl Toolkit. 
So follow the installation tips for that here [[Install the VI Perl Toolkit on OS X]]

==== Graphical environment ====
The vGhetto client uses a graphical user interface and because of that, it has a dependency on the X11 server.
Starting with OS X Leopard, this is included in the default install of OS X. So unless you are experiencing some real problems getting things to work I would not update X11 server. It is added to the steps below because you might have to redo it depending on your current setup.

==== Install module Tk ====
vGhetto uses the perl module Tk for the graphical environment, so this is one of the main dependencies.
You can install it by running:
 cpan Tk
During the install you'll see many displays popup to test the functionality from tk, that's normal.
If you are extremely lucky it ends with OK..., but if you are like me you'll get:
 Failed Test     Stat Wstat Total Fail  Failed  List of Failed
 -------------------------------------------------------------------------------
 t/canvas.t         1   256   158    1   0.63%  84
 t/coloreditor.t  255 65280     8   11 137.50%  3-8
 t/wm-tcl.t         1   256   315    1   0.32%  240
  (37 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 161 subtests skipped.
 Failed 3/62 test scripts, 95.16% okay. 8/3686 subtests failed, 99.78% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

''' If that's your result too, then skip the next few steps as it is expected that a few test scripts will fail '''

Turns out I still had an X11 Server installed from tiger.
 XQuartz 2.1.6 (xorg-server 1.4.2-apple33

So from the DVD, go to option installs and select Optional Installs.mpkg :
In the applications part select X11.

===== Remove X11 =====
Messed it up, got confused, want to start over?

Before you start deleting anything, make sure you have a Leopard's installation DVD available and downloaded the latest X11 package from the Xquartz Project.

* Delete pretty much all X11 from you system, and let it forget its receipts:

Code:

 sudo rm -rf /usr/X11 /usr/X11R6
 sudo pkgutil --forget com.apple.pkg.X11DocumentationLeo
 sudo pkgutil --forget com.apple.pkg.X11User
 sudo pkgutil --forget com.apple.pkg.X11SDKLeo
 sudo pkgutil --forget org.x.X11.pkg

* Install X11User.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Install/Optional Installs.mpkg

* Install X11SDK.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Installs/Xcode Tools/Packages/

* Install [http://xquartz.macosforge.org/trac/wiki/Releases the latest X11 package] release from the Xquartz Project.

===== Install Tk second try =====
After installing X11 2.4.0 from the xquartz project, trying to install Tk gives even more errors:

  (32 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 173 subtests skipped.
 Failed 22/62 test scripts, 64.52% okay. 1258/3686 subtests failed, 65.87% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

===== Install Tk third try =====
So much fun, after following the complete removal steps from X11 and only installing the default Leopard parts (not the quartz update) and rerunning the cpan Tk setup. Now I'm getting:

  (37 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 161 subtests skipped.
 Failed 4/62 test scripts, 93.55% okay. 9/3686 subtests failed, 99.76% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

Well maybe having 4 failed tests is not so bad?

==== Force feeding tk-perl ====

If you scroll up on the part where we're trying to install Tk via cpan, then you'll see right at the top something along these lines: 
 /Users/topaz/.cpan/sources/authors/id/S/SR/SREZIC/Tk-804.028.tar.gz
So our Tk version is Tk-804.028
Move to our build folder:
 cd /Users/topaz/.cpan/build/Tk-804.028
Now install by running:
 sudo make install
If there's no complaint after that, you should be OK

==== time-modules ====
 cpan Time::ParseDate

This should install the time-modules library and if it works OK, you should see this step end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
   /usr/bin/make install  -- OK


==== Done ====
That's it. With all of these requirements in place, you should now be able to run the vGhetto client directly from OS X by running:
 ./vGhetto.pl
(You might have to make vGhetto.pl executable first by executing "chmod +x vGhetto.pl" )

[[Category: Perl]]</text>
    <sha1>7e2ad0aad61e74967971806b7c8aacb84dde4d12</sha1>
  </revision>
  <revision>
    <id>1191</id>
    <parentid>1161</parentid>
    <timestamp>2010-08-26T14:52:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added note about automated script for installing under OS X</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5136" xml:space="preserve">==== First steps ====
In order to install the [http://bit.ly/vGhettoGUI vGhetto client] and to be able to run all of its accompanied scripts, you'll have to install the VI Perl Toolkit. 
So follow the installation tips for that here [[Install the VI Perl Toolkit on OS X]]


Also note that there is now a script in the subversion repository in the [http://vghetto.svn.sourceforge.net/viewvc/vghetto/installers/ installers folder], called vghetto-osx.sh, that automates the steps below.

==== Graphical environment ====
The vGhetto client uses a graphical user interface and because of that, it has a dependency on the X11 server.
Starting with OS X Leopard, this is included in the default install of OS X. So unless you are experiencing some real problems getting things to work I would not update X11 server. It is added to the steps below because you might have to redo it depending on your current setup.

==== Install module Tk ====
vGhetto uses the perl module Tk for the graphical environment, so this is one of the main dependencies.
You can install it by running:
 cpan Tk
During the install you'll see many displays popup to test the functionality from tk, that's normal.
If you are extremely lucky it ends with OK..., but if you are like me you'll get:
 Failed Test     Stat Wstat Total Fail  Failed  List of Failed
 -------------------------------------------------------------------------------
 t/canvas.t         1   256   158    1   0.63%  84
 t/coloreditor.t  255 65280     8   11 137.50%  3-8
 t/wm-tcl.t         1   256   315    1   0.32%  240
  (37 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 161 subtests skipped.
 Failed 3/62 test scripts, 95.16% okay. 8/3686 subtests failed, 99.78% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

''' If that's your result too, then skip the next few steps as it is expected that a few test scripts will fail '''

Turns out I still had an X11 Server installed from tiger.
 XQuartz 2.1.6 (xorg-server 1.4.2-apple33

So from the DVD, go to option installs and select Optional Installs.mpkg :
In the applications part select X11.

===== Remove X11 =====
Messed it up, got confused, want to start over?

Before you start deleting anything, make sure you have a Leopard's installation DVD available and downloaded the latest X11 package from the Xquartz Project.

* Delete pretty much all X11 from you system, and let it forget its receipts:

Code:

 sudo rm -rf /usr/X11 /usr/X11R6
 sudo pkgutil --forget com.apple.pkg.X11DocumentationLeo
 sudo pkgutil --forget com.apple.pkg.X11User
 sudo pkgutil --forget com.apple.pkg.X11SDKLeo
 sudo pkgutil --forget org.x.X11.pkg

* Install X11User.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Install/Optional Installs.mpkg

* Install X11SDK.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Installs/Xcode Tools/Packages/

* Install [http://xquartz.macosforge.org/trac/wiki/Releases the latest X11 package] release from the Xquartz Project.

===== Install Tk second try =====
After installing X11 2.4.0 from the xquartz project, trying to install Tk gives even more errors:

  (32 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 173 subtests skipped.
 Failed 22/62 test scripts, 64.52% okay. 1258/3686 subtests failed, 65.87% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

===== Install Tk third try =====
So much fun, after following the complete removal steps from X11 and only installing the default Leopard parts (not the quartz update) and rerunning the cpan Tk setup. Now I'm getting:

  (37 subtests UNEXPECTEDLY SUCCEEDED), 2 tests and 161 subtests skipped.
 Failed 4/62 test scripts, 93.55% okay. 9/3686 subtests failed, 99.76% okay.
 make: *** [test_dynamic] Error 255
   /usr/bin/make test -- NOT OK
 Running make install
   make test had returned bad status, won't install without force

Well maybe having 4 failed tests is not so bad?

==== Force feeding tk-perl ====

If you scroll up on the part where we're trying to install Tk via cpan, then you'll see right at the top something along these lines: 
 /Users/topaz/.cpan/sources/authors/id/S/SR/SREZIC/Tk-804.028.tar.gz
So our Tk version is Tk-804.028
Move to our build folder:
 cd /Users/topaz/.cpan/build/Tk-804.028
Now install by running:
 sudo make install
If there's no complaint after that, you should be OK

==== time-modules ====
 cpan Time::ParseDate

This should install the time-modules library and if it works OK, you should see this step end with:
 Appending installation info to /Library/Perl/Updates/5.8.8/darwin-thread-multi-2level/perllocal.pod
   /usr/bin/make install  -- OK


==== Done ====
That's it. With all of these requirements in place, you should now be able to run the vGhetto client directly from OS X by running:
 ./vGhetto.pl
(You might have to make vGhetto.pl executable first by executing "chmod +x vGhetto.pl" )

[[Category: Perl]]</text>
    <sha1>50825bbe5c472e8a5ba7b8b5c65d668fe2e9bdc4</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>PowerShell</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>1163</id>
    <parentid>1132</parentid>
    <timestamp>2010-05-08T14:36:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3964" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====
===== General Powershell =====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Powershell techniques and tips]]

* [[Powershell Tools]]

===== VI-Toolkit / PowerCLI =====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>7b199d5cc388f434bf9c6a047bb15000014a65de</sha1>
  </revision>
  <revision>
    <id>1166</id>
    <parentid>1163</parentid>
    <timestamp>2010-05-10T16:02:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4001" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====
===== General Powershell =====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Powershell techniques and tips]]

* [[Powershell Tools]]

===== VI-Toolkit / PowerCLI =====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>f4782aa9e830a17d042fe99b70d70d76791854e4</sha1>
  </revision>
  <revision>
    <id>1184</id>
    <parentid>1166</parentid>
    <timestamp>2010-07-31T11:08:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4096" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]
It is nowadays also offered via Windows Update as an optional update.
Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]].


==== Learning VI-Toolkit Powershell ====
===== General Powershell =====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Powershell techniques and tips]]

* [[Powershell Tools]]

===== VI-Toolkit / PowerCLI =====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>dd547de9f1e895754aca89a730243d9aa6131a1b</sha1>
  </revision>
  <revision>
    <id>1186</id>
    <parentid>1184</parentid>
    <timestamp>2010-07-31T11:29:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="658" xml:space="preserve">If you are not running windows 2008/Windows 7 and don't have PowerShell (Posh) installed then go get it from Microsoft's [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx PowerShell landing page]

It is nowadays also offered via Windows Update as an optional update.

Then in order to manage your virtual infrastructure you will need the [[VI Toolkit for windows]] and then go to the [[PowerCLI]] page.


==== Learning Powershell ====

* [[BEGINNERS PAGE | Beginners page]]

* [[Learning Powershell]]

* [[Powershell techniques and tips]]

* [[Powershell Tools]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>3b15fb7bf2ee495d50e66681cb2f31cfe617684a</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Patching ESX with PowerCLI 4.0 U1</title>
  <ns>0</ns>
  <id>517</id>
  <revision>
    <id>1164</id>
    <timestamp>2010-05-08T14:42:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Carter Shanklin here shows how you can use PowerCLI scripting to patch multiple hosts at the same time. He completely walks you through patching 4 hosts at the same time and expl...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="334" xml:space="preserve">Carter Shanklin here shows how you can use PowerCLI scripting to patch multiple hosts at the same time.
He completely walks you through patching 4 hosts at the same time and explains every step along the way.

[http://www.youtube.com/watch?v=gXdX4xTlCP8 Patching ESX with PowerCLI 4.0 U1]

[[Category: PowerCLI]]  [[Category: Videos]]</text>
    <sha1>d1036fc703563e80cf45d2a35943baa993358c94</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>PowerCLI Oneliners: Statistics</title>
  <ns>0</ns>
  <id>491</id>
  <revision>
    <id>1165</id>
    <parentid>1134</parentid>
    <timestamp>2010-05-08T14:46:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1221" xml:space="preserve">==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM's with least free disk space]

* [http://www.hypervisor.fr/?p=2051 Statistics: Top 20 VM's with most free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]

* [http://www.virtu-al.net/2009/08/27/powercli-one-liners-last-10-vms-created-and-removed/ Last 10 VMs created and removed]

* [http://www.hypervisor.fr/?p=1465 Oneliner: List VM's with less then 5% free space in just a few seconds]


[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>91077ff50277219bc70965ad9468a81710dc9aff</sha1>
  </revision>
  <revision>
    <id>1174</id>
    <parentid>1165</parentid>
    <timestamp>2010-05-15T13:52:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added memory overcommit ratio oneliner from Hypervisor.fr</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1282" xml:space="preserve">==== Statistics ====

* [http://www.peetersonline.nl/index.php/vmware/vmware-stats-oneliner/ Statistics: Average CPU and memory usage]

* [http://www.virtu-al.net/2009/07/01/powercli-stats-one-liner/ Statistics: Number of CPUs, amount of memory assigned, Average CPU and memory usage]

* [http://www.peetersonline.nl/index.php/vmware/oneliner-for-the-road/ Memory Usage statistics sorted per VM]

* [http://www.peetersonline.nl/index.php/vmware/posting-pause-plus-bonus-one-liner/ Statistics: Top 20 VM's with least free disk space]

* [http://www.hypervisor.fr/?p=2051 Statistics: Top 20 VM's with most free disk space]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-4/ Get a list of vm's and the number of snapshots per vm]

* [http://www.virtu-al.net/2009/06/25/powercli-more-one-liners/ Number of VM's per Resource Pool]

* [http://www.virtu-al.net/2009/06/17/one-liner-how-many-vms/ How many VM's per Host]

* [http://www.virtu-al.net/2009/08/27/powercli-one-liners-last-10-vms-created-and-removed/ Last 10 VMs created and removed]

* [http://www.hypervisor.fr/?p=1465 Oneliner: List VM's with less then 5% free space in just a few seconds]

* [http://www.hypervisor.fr/?p=1730 Memory Overcommit Ratio]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>ea8d860b5caee0bc7326b47341a0fbae0118e9c9</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Invoke-VM with PowerCLI 4.0 U1</title>
  <ns>0</ns>
  <id>518</id>
  <revision>
    <id>1167</id>
    <timestamp>2010-05-10T16:06:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Carter Shanklin here shows how you can use PowerCLI to run batch files in Windows guest or even scripts in Linux guests. The technique shown allows you to automate a variety of t...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="354" xml:space="preserve">Carter Shanklin here shows how you can use PowerCLI to run batch files in Windows guest or even scripts in Linux guests.
The technique shown allows you to automate a variety of tasks in your guests using PowerCLI.

[http://www.youtube.com/watch?v=BnqssP0Yck8  Invoke-VMscript Improvements in PowerCLI 4.0 U1]

[[Category: PowerCLI]]  [[Category: Videos]]</text>
    <sha1>69c6555d392d977c5f1ee8a8084e61594185c9f1</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Jonathan Medd's Powershell 2.0 One Cmdlet at a time</title>
  <ns>0</ns>
  <id>509</id>
  <revision>
    <id>1168</id>
    <parentid>1133</parentid>
    <timestamp>2010-05-11T09:22:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Catching up a little bit with Jonathan Medd's amazing One Cmdlet at a time series</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11192" xml:space="preserve">==== Learning Powershell ====
Jonathan Medd is creating a powershell 2.0 guide where he explains cmdlet's one by one.

He call's it the Cmdlet series: [http://www.jonathanmedd.net/category/cmdlet-series Powershell 2.0: One Cmdlet at a Time] 

Per Cmdlet, he explains what it does and adds a nice example on how-to use the Cmdlet in real life.
If there are any dependencies besides installing powershell 2.0, they are listed.
As a final teaser he also explains how you could do a similar thing with Powershell 1.0

Very nicely done Jonathan, keep up the good work! His list is -at the time of writing- almost 100 Cmdlets, VERY impressive!

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-1-get-random.html Get-Random]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-2-send-mailmessage.html Send-MailMessage]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-3-get-counter.html Get-Counter]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-4-out-gridview.html Out-GridView]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-5-get-hotfix.html Get-Hotfix]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-6-test-connection.html Test-Connection]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-7-reset-computermachinepassword.html Reset-ComputerMachinePassword]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-8-get-module.html Get-Module]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-9-checkpoint-compute.html Checkpoint-Computer]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-10-restar-computer.html Restart-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-11-add-computer.html Add-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-12-write-eventlog.html Write-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-13-clear-eventlog.html Clear-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-14-start-process.html Start-Process]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-15-start-job.html Start-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-16-get-job.html Get-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-17-receive-job.html Receive-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-18-remove-job.html Remove-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-19-stop-job.html Stop-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-20-wait-job.html Wait-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-21-select-xml.html Select-Xml]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-22-enable-computerrestore.html Enable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-23-disable-computerrestore.html Disable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-24-get-computerrestorepoint.html Get-ComputerRestorePoint]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-25-restore-computer.html Restore-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-26-new-webserviceproxy.html New-WebServiceProxy]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-27-test-computersecurechannel.html Test-ComputerSecureChannel]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-28-export-counter.html Export-Counter]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-29-import-counter.html Import-Counter]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-30-enable-psremoting.html Enable-PSRemoting]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-31-enter-pssession.html Enter-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-32-exit-pssession.html Exit-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-33-new-pssession.html New-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-34-invoke-commmand.html Invoke-Command]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-35-new-pssessionoption.html New-PSSessionOption]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-36-get-pssession.html Get-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-37-remove-pssession.html Remove-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-38-get-pssessionconfiguration.html Get-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-39-register-pssessionconfiguration.html Register-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-40-set-pssessionconfiguration.html Set-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-41-disable-pssessionconfiguration.html Disable-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-42-enable-pssessionconfiguration.html Enable-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-43-unregister-pssessionconfiguration.html Unregister-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-44-set-wsmanquickconfig.html Set-WSManQuickConfig]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-45-connect-wsman.html Connect-WSMan]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-46-test-wsman.html Test-WSMan]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-47-invoke-wsmanaction.html Invoke-WSManAction]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-48-get-wsmaninstance.html Get-WSManInstance]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-49-new-wsmaninstance.html New-WSManInstance]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-50-set-wsmaninstance.html Set-WSManInstance]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-51-remove-wsmaninstance.html Remove-WSManInstance]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-52-new-wsmansessionoption.html New-WSManSessionOption]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-53-enable-wsmancredssp.html Enable-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-54-get-wsmancredssp.html Get-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-55-disable-wsmancredssp.html Disable-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-56-disconnect-wsman.html Disconnect-WSMan]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-57-import-pssession.html Import-PSSession]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-58-export-pssession.html Export-PSSession]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-59-set-psbreakpoint.html Set-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-60-get-psbreakpoint.html Get-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-61-disable-psbreakpoint.html Disable-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-62-enable-psbreakpoint.html Enable-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-63-remove-psbreakpoint.html Remove-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-64-clear-history.html Clear-History]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-65-new-eventlog.html New-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-66-limit-eventlog.html Limit-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-67-remove-eventlog.html Remove-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-68-show-eventlog.html Show-EventLog]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-69-get-winevent.html Get-WinEvent]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-70-import-module.html Import-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-71-new-module.html New-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-72-export-modulemember.html Export-ModuleMember]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-73-new-modulemanifest.html New-ModuleManifest]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-74-test-modulemanifest.html Test-ModuleManifest]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-75-remove-module.html Remove-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-76-stop-computer.html Stop-Computer]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-77-remove-computer.html Remove-Computer]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-78-start-transaction.html Start-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-79-complete-transaction.html Complete-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-80-get-transaction.html Get-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-81-undo-transaction.html Undo-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-82-use-transaction.html Use-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-83-convertto-csv.html ConvertTo-CSV]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-84-convertfrom-csv.html ConvertFrom-CSV]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-85-convertfrom-stringdata.html ConvertFrom-StringData]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-86-convertto-xml.html ConvertTo-XML]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-87-get-formatdata.html Get-FormatData]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-88-export-formatdata.html Export-FormatData]


[[Category: Powershell]]</text>
    <sha1>098677b46c747bb499448ce2fffc311f7be18caf</sha1>
  </revision>
  <revision>
    <id>1169</id>
    <parentid>1168</parentid>
    <timestamp>2010-05-13T10:45:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Catched up with Jonathans powershell series</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12485" xml:space="preserve">==== Learning Powershell ====
Jonathan Medd is creating a powershell 2.0 guide where he explains cmdlet's one by one.

He call's it the Cmdlet series: [http://www.jonathanmedd.net/category/cmdlet-series Powershell 2.0: One Cmdlet at a Time] 

Per Cmdlet, he explains what it does and adds a nice example on how-to use the Cmdlet in real life.
If there are any dependencies besides installing powershell 2.0, they are listed.
As a final teaser he also explains how you could do a similar thing with Powershell 1.0

Very nicely done Jonathan, keep up the good work! His list is -at the time of writing- almost 100 Cmdlets, VERY impressive!

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-1-get-random.html Get-Random]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-2-send-mailmessage.html Send-MailMessage]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-3-get-counter.html Get-Counter]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-4-out-gridview.html Out-GridView]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-5-get-hotfix.html Get-Hotfix]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-6-test-connection.html Test-Connection]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-7-reset-computermachinepassword.html Reset-ComputerMachinePassword]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-8-get-module.html Get-Module]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-9-checkpoint-compute.html Checkpoint-Computer]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-10-restar-computer.html Restart-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-11-add-computer.html Add-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-12-write-eventlog.html Write-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-13-clear-eventlog.html Clear-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-14-start-process.html Start-Process]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-15-start-job.html Start-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-16-get-job.html Get-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-17-receive-job.html Receive-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-18-remove-job.html Remove-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-19-stop-job.html Stop-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-20-wait-job.html Wait-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-21-select-xml.html Select-Xml]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-22-enable-computerrestore.html Enable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-23-disable-computerrestore.html Disable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-24-get-computerrestorepoint.html Get-ComputerRestorePoint]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-25-restore-computer.html Restore-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-26-new-webserviceproxy.html New-WebServiceProxy]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-27-test-computersecurechannel.html Test-ComputerSecureChannel]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-28-export-counter.html Export-Counter]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-29-import-counter.html Import-Counter]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-30-enable-psremoting.html Enable-PSRemoting]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-31-enter-pssession.html Enter-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-32-exit-pssession.html Exit-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-33-new-pssession.html New-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-34-invoke-commmand.html Invoke-Command]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-35-new-pssessionoption.html New-PSSessionOption]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-36-get-pssession.html Get-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-37-remove-pssession.html Remove-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-38-get-pssessionconfiguration.html Get-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-39-register-pssessionconfiguration.html Register-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-40-set-pssessionconfiguration.html Set-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-41-disable-pssessionconfiguration.html Disable-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-42-enable-pssessionconfiguration.html Enable-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-43-unregister-pssessionconfiguration.html Unregister-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-44-set-wsmanquickconfig.html Set-WSManQuickConfig]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-45-connect-wsman.html Connect-WSMan]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-46-test-wsman.html Test-WSMan]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-47-invoke-wsmanaction.html Invoke-WSManAction]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-48-get-wsmaninstance.html Get-WSManInstance]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-49-new-wsmaninstance.html New-WSManInstance]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-50-set-wsmaninstance.html Set-WSManInstance]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-51-remove-wsmaninstance.html Remove-WSManInstance]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-52-new-wsmansessionoption.html New-WSManSessionOption]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-53-enable-wsmancredssp.html Enable-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-54-get-wsmancredssp.html Get-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-55-disable-wsmancredssp.html Disable-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-56-disconnect-wsman.html Disconnect-WSMan]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-57-import-pssession.html Import-PSSession]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-58-export-pssession.html Export-PSSession]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-59-set-psbreakpoint.html Set-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-60-get-psbreakpoint.html Get-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-61-disable-psbreakpoint.html Disable-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-62-enable-psbreakpoint.html Enable-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-63-remove-psbreakpoint.html Remove-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-64-clear-history.html Clear-History]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-65-new-eventlog.html New-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-66-limit-eventlog.html Limit-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-67-remove-eventlog.html Remove-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-68-show-eventlog.html Show-EventLog]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-69-get-winevent.html Get-WinEvent]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-70-import-module.html Import-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-71-new-module.html New-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-72-export-modulemember.html Export-ModuleMember]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-73-new-modulemanifest.html New-ModuleManifest]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-74-test-modulemanifest.html Test-ModuleManifest]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-75-remove-module.html Remove-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-76-stop-computer.html Stop-Computer]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-77-remove-computer.html Remove-Computer]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-78-start-transaction.html Start-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-79-complete-transaction.html Complete-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-80-get-transaction.html Get-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-81-undo-transaction.html Undo-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-82-use-transaction.html Use-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-83-convertto-csv.html ConvertTo-CSV]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-84-convertfrom-csv.html ConvertFrom-CSV]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-85-convertfrom-stringdata.html ConvertFrom-StringData]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-86-convertto-xml.html ConvertTo-XML]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-87-get-formatdata.html Get-FormatData]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-88-export-formatdata.html Export-FormatData]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-89-invoke-wmimethod.html Invoke-WMIMethod]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-90-remove-wmiobject.html Remove-WMIMethod]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-91-set-wmiinstance.html Set-WMIInstance]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-92-register-wmievent.html Register-WMIEvent]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-93-register-objectevent.html Register-ObjectEvent]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-94-get-eventsubscriber.html Get-EventSubscriber]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-95-register-engine-event.html Register-Engine-Event]

* [http://www.jonathanmedd.net/2010/05/powershell-2-0-one-cmdlet-at-a-time-96-new-event.html New-Event]

* [http://www.jonathanmedd.net/2010/05/powershell-2-0-one-cmdlet-at-a-time-97-get-event.html Get-Event]

* [http://www.jonathanmedd.net/2010/05/powershell-2-0-one-cmdlet-at-a-time-98-wait-event.html Wait-Event]

* [http://www.jonathanmedd.net/2010/05/powershell-2-0-one-cmdlet-at-a-time-99-unregister-event.html Unregister-Event]


[[Category: Powershell]]</text>
    <sha1>21d960a57a8c32d689038d02c20b62c49877a02b</sha1>
  </revision>
  <revision>
    <id>1170</id>
    <parentid>1169</parentid>
    <timestamp>2010-05-13T10:55:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Reordered Jonathan's Medds "One cmdlet at a time series" into a more logical ordering</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12710" xml:space="preserve">==== Learning Powershell ====
Jonathan Medd is creating a powershell 2.0 guide where he explains cmdlet's one by one.

He call's it the Cmdlet series: [http://www.jonathanmedd.net/category/cmdlet-series Powershell 2.0: One Cmdlet at a Time] 

Per Cmdlet, he explains what it does and adds a nice example on how-to use the Cmdlet in real life.
If there are any dependencies besides installing powershell 2.0, they are listed.
As a final teaser he also explains how you could do a similar thing with Powershell 1.0

Very nicely done Jonathan, keep up the good work! His list is -at the time of writing- almost 100 Cmdlets, VERY impressive!

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-1-get-random.html Get-Random]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-2-send-mailmessage.html Send-MailMessage]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-3-get-counter.html Get-Counter]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-4-out-gridview.html Out-GridView]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-5-get-hotfix.html Get-Hotfix]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-6-test-connection.html Test-Connection]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-14-start-process.html Start-Process]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-21-select-xml.html Select-Xml]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-26-new-webserviceproxy.html New-WebServiceProxy]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-27-test-computersecurechannel.html Test-ComputerSecureChannel]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-28-export-counter.html Export-Counter]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-29-import-counter.html Import-Counter]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-30-enable-psremoting.html Enable-PSRemoting]

==== Jobs ====

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-15-start-job.html Start-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-16-get-job.html Get-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-17-receive-job.html Receive-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-18-remove-job.html Remove-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-19-stop-job.html Stop-Job]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-20-wait-job.html Wait-Job]

==== Sessions ====

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-31-enter-pssession.html Enter-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-32-exit-pssession.html Exit-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-33-new-pssession.html New-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-34-invoke-commmand.html Invoke-Command]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-35-new-pssessionoption.html New-PSSessionOption]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-36-get-pssession.html Get-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-37-remove-pssession.html Remove-PSSession]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-38-get-pssessionconfiguration.html Get-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-39-register-pssessionconfiguration.html Register-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-40-set-pssessionconfiguration.html Set-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-41-disable-pssessionconfiguration.html Disable-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-42-enable-pssessionconfiguration.html Enable-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-43-unregister-pssessionconfiguration.html Unregister-PSSessionConfiguration]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-44-set-wsmanquickconfig.html Set-WSManQuickConfig]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-45-connect-wsman.html Connect-WSMan]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-46-test-wsman.html Test-WSMan]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-47-invoke-wsmanaction.html Invoke-WSManAction]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-48-get-wsmaninstance.html Get-WSManInstance]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-49-new-wsmaninstance.html New-WSManInstance]

* [http://www.jonathanmedd.net/2010/01/powershell-2-0-one-cmdlet-at-a-time-50-set-wsmaninstance.html Set-WSManInstance]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-51-remove-wsmaninstance.html Remove-WSManInstance]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-52-new-wsmansessionoption.html New-WSManSessionOption]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-53-enable-wsmancredssp.html Enable-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-54-get-wsmancredssp.html Get-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-55-disable-wsmancredssp.html Disable-WSManCredSSP]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-56-disconnect-wsman.html Disconnect-WSMan]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-57-import-pssession.html Import-PSSession]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-58-export-pssession.html Export-PSSession]

==== Breakpoints ====

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-59-set-psbreakpoint.html Set-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-60-get-psbreakpoint.html Get-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-61-disable-psbreakpoint.html Disable-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-62-enable-psbreakpoint.html Enable-PSBreakpoint]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-63-remove-psbreakpoint.html Remove-PSBreakpoint]

==== Eventlog ====

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-12-write-eventlog.html Write-EventLog]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-13-clear-eventlog.html Clear-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-64-clear-history.html Clear-History]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-65-new-eventlog.html New-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-66-limit-eventlog.html Limit-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-67-remove-eventlog.html Remove-EventLog]

* [http://www.jonathanmedd.net/2010/02/powershell-2-0-one-cmdlet-at-a-time-68-show-eventlog.html Show-EventLog]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-69-get-winevent.html Get-WinEvent]

==== Modules ====

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-8-get-module.html Get-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-70-import-module.html Import-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-71-new-module.html New-Module]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-72-export-modulemember.html Export-ModuleMember]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-73-new-modulemanifest.html New-ModuleManifest]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-74-test-modulemanifest.html Test-ModuleManifest]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-75-remove-module.html Remove-Module]

==== Computer ====

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-7-reset-computermachinepassword.html Reset-ComputerMachinePassword]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-9-checkpoint-compute.html Checkpoint-Computer]

* [http://www.jonathanmedd.net/2009/11/powershell-2-0-one-cmdlet-at-a-time-10-restar-computer.html Restart-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-11-add-computer.html Add-Computer]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-22-enable-computerrestore.html Enable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-23-disable-computerrestore.html Disable-ComputerRestore]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-24-get-computerrestorepoint.html Get-ComputerRestorePoint]

* [http://www.jonathanmedd.net/2009/12/powershell-2-0-one-cmdlet-at-a-time-25-restore-computer.html Restore-Computer]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-76-stop-computer.html Stop-Computer]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-77-remove-computer.html Remove-Computer]

==== Transactions ====

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-78-start-transaction.html Start-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-79-complete-transaction.html Complete-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-80-get-transaction.html Get-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-81-undo-transaction.html Undo-Transaction]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-82-use-transaction.html Use-Transaction]

==== Converting and formatting data ====

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-83-convertto-csv.html ConvertTo-CSV]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-84-convertfrom-csv.html ConvertFrom-CSV]

* [http://www.jonathanmedd.net/2010/03/powershell-2-0-one-cmdlet-at-a-time-85-convertfrom-stringdata.html ConvertFrom-StringData]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-86-convertto-xml.html ConvertTo-XML]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-87-get-formatdata.html Get-FormatData]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-88-export-formatdata.html Export-FormatData]

==== WMI Methods ====

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-89-invoke-wmimethod.html Invoke-WMIMethod]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-90-remove-wmiobject.html Remove-WMIMethod]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-91-set-wmiinstance.html Set-WMIInstance]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-92-register-wmievent.html Register-WMIEvent]

==== Events ====

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-93-register-objectevent.html Register-ObjectEvent]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-94-get-eventsubscriber.html Get-EventSubscriber]

* [http://www.jonathanmedd.net/2010/04/powershell-2-0-one-cmdlet-at-a-time-95-register-engine-event.html Register-Engine-Event]

* [http://www.jonathanmedd.net/2010/05/powershell-2-0-one-cmdlet-at-a-time-96-new-event.html New-Event]

* [http://www.jonathanmedd.net/2010/05/powershell-2-0-one-cmdlet-at-a-time-97-get-event.html Get-Event]

* [http://www.jonathanmedd.net/2010/05/powershell-2-0-one-cmdlet-at-a-time-98-wait-event.html Wait-Event]

* [http://www.jonathanmedd.net/2010/05/powershell-2-0-one-cmdlet-at-a-time-99-unregister-event.html Unregister-Event]


[[Category: Powershell]]</text>
    <sha1>556f13505e2de2f46a2735bf81147b062f483cf9</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>1171</id>
    <parentid>535</parentid>
    <timestamp>2010-05-15T11:06:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="822" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

Supported on VMware Workstation 6.0.x and up, VMware Server 1.x and up, VMware ESX3.5U2+

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX 1.1 API reference Guide]

[http://www.vmware.com/support/developer/vix-api/vix16_reference/ VMware VIX 1.6 API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

==== Presentations ====

[[VIX API Tech Talk Partner Exchange]]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>0dbc6df5d72a84bd5a7cddbc498eb27d2b5218f5</sha1>
  </revision>
  <revision>
    <id>1175</id>
    <parentid>1171</parentid>
    <timestamp>2010-05-24T13:51:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="844" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

Supported on VMware Workstation 6.0.x and up, VMware Server 1.x and up, VMware ESX3.5U2+

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX 1.1 API reference Guide]

[http://www.vmware.com/support/developer/vix-api/vix16_reference/ VMware VIX 1.6 API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

==== Presentations ====

[[VIX API Tech Talk Partner Exchange]]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Vix Java Toolkit]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>865843736fc4d90cdbc42587f1ea2c8f234c410c</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>VIX API Tech Talk Partner Exchange</title>
  <ns>0</ns>
  <id>519</id>
  <revision>
    <id>1172</id>
    <timestamp>2010-05-15T11:11:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Pablo has put the video from the VIX API Tech Talk by Matt Lamantia from the event last February online at the VMware VIX blog.   It explains what Guest Operations are, and how t...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="525" xml:space="preserve">Pablo has put the video from the VIX API Tech Talk by Matt Lamantia from the event last February online at the VMware VIX blog. 

It explains what Guest Operations are, and how to use VIX to automate them for VMs running in vSphere, VMware Server, VMware Workstation, or VMware Player.

[http://blogs.vmware.com/vix/2010/05/vix-api-tech-talk-from-vmware-partner-exchange-is-available-online.html VMware Blog article VIX API Tech Talk]

[http://vimeo.com/10705257 Direct link to Vimeo]

[[Category: VIX]]  [[Category: Videos]]</text>
    <sha1>75f8b7933b6c74aa7d20fcbfefb687b1b1bd2531</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>PowerCLI Oneliners: VM Configuration</title>
  <ns>0</ns>
  <id>494</id>
  <revision>
    <id>1173</id>
    <parentid>1141</parentid>
    <timestamp>2010-05-15T11:29:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Oneliner enable/disable FT</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1902" xml:space="preserve">==== VM Configuration ====

* [http://www.peetersonline.nl/index.php/vmware/oneliner-of-the-day/ Copy Active Directory Description to your VM]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Reset CPU and Memory limits to “Unlimited” for all VMs in vCenter]

* [http://www.virtu-al.net/2009/07/07/powercli-more-one-liner-power/ Get name of the VM and the network adapter for supplied Mac address]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere]

* [http://ict-freak.nl/2009/07/10/powercli-two-vhardware-one-liners/ Get names of VM's not yet upgraded to vSphere and VM Tools not upgraded]

* [http://ict-freak.nl/2009/08/14/powercli-add-notes-to-multiple-vms/ Add notes to multiple VM's using CSV]

* [http://ict-freak.nl/2009/08/17/powercli-set-custom-fields/ Set description of custom fields for multiple VM's from CSV]

* [http://communities.vmware.com/thread/227705 Get VMware Tools version for all VM's]

* [http://technodrone.blogspot.com/2009/08/powercli-storage-vmotion.html Relocate VM using storage VMotion]

* [http://frankdenneman.wordpress.com/2009/12/15/impact-of-mismatch-guest-os-type/ Finding VM's with mismatched Guest OS type]

* [http://ict-freak.nl/2009/12/01/powercli-change-persistence-mode-on-the-fly/ Return all the vmdk’s with the Independent Persistent mode enabled]

* [http://ict-freak.nl/2009/12/01/powercli-change-persistence-mode-on-the-fly/ Disable persistent mode for all vmdk's with this mode enabled]

* [http://communities.vmware.com/thread/256747 List VM's with CD connected to a Datastore or host device]

* [http://communities.vmware.com/thread/232209 Get VM SCSI Card Adapter - Bus Logic or LSI Logic]

* [http://professionalvmware.com/2009/09/scheduling-vmwares-ft-fault-tolerance/ Enable/Disable Fault Tolerance]

[[Category: PowerCLI]][[Category: VM Management]]</text>
    <sha1>a0d7fbd3c7704531632c4f0b53c24a381e9b371e</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Vix Java Toolkit</title>
  <ns>0</ns>
  <id>520</id>
  <revision>
    <id>1176</id>
    <timestamp>2010-05-24T13:56:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added reference to Daniel Parrella's vixJava project</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="510" xml:space="preserve">VMware employee Dan Parrella has provided a java interface to VIX.

Features are:

    * Provides access to VMware VIX APIs through Java
    * Supports VMware VIX version 1.8.1, which includes support for Player, Workstation, and vSphere
    * Object-oriented design instead of just access to functions in the API

[http://sourceforge.net/projects/vixjava/ Sourceforge vixJava project page]

[http://sourceforge.net/apps/wordpress/vixjava/ Blog vixJava]


[[Category: VIX]] [[Category: SDK]] [[Category: Java]]</text>
    <sha1>e9cbe7bfd5e04ead883737b6f19067a7bf09596a</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>SDK</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>1177</id>
    <parentid>822</parentid>
    <timestamp>2010-06-03T09:51:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="322" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

[[VMware Icons]]

[[vCenter Orchestrator]]

==== External links ====

[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's


[[Category: SDK]]</text>
    <sha1>2ed6dd98a5fdd9f03fee67c3bda4ec023ce54a6f</sha1>
  </revision>
  <revision>
    <id>1190</id>
    <parentid>1177</parentid>
    <timestamp>2010-08-03T12:22:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to vCloud API forums landing page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="416" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

[[VMware Icons]]

[[vCenter Orchestrator]]

==== External links ====

[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's

[http://communities.vmware.com/community/developer/forums/vcloudapi VMware vCloud API forums]

[[Category: SDK]]</text>
    <sha1>a981dd0c1860915767d102008a066afbe49f9f3e</sha1>
  </revision>
  <revision>
    <id>1194</id>
    <parentid>1190</parentid>
    <timestamp>2010-09-17T15:30:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added link to php beta SDK forum</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="504" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

[[VMware Icons]]

[[vCenter Orchestrator]]

==== External links ====

[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's

[http://communities.vmware.com/community/developer/forums/vcloudapi VMware vCloud API forums]

[http://communities.vmware.com/community/beta/vcloudsdkphp VMware vCloud php SDK beta]

[[Category: SDK]]</text>
    <sha1>7d0082471bcfe727ac8c2cfa25fd912526f96c64</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>VCenter Orchestrator</title>
  <ns>0</ns>
  <id>521</id>
  <revision>
    <id>1178</id>
    <timestamp>2010-06-03T09:54:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Sorry not much content here yet.  ==== Presentations ====  [[Orchestrator - VMworld 2009 Developer day]]  [[Category: SDK]]'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="123" xml:space="preserve">Sorry not much content here yet.

==== Presentations ====

[[Orchestrator - VMworld 2009 Developer day]]

[[Category: SDK]]</text>
    <sha1>015c834b3265bec5f41cc120bc71fd551d99b580</sha1>
  </revision>
  <revision>
    <id>1179</id>
    <parentid>1178</parentid>
    <timestamp>2010-06-03T09:55:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="150" xml:space="preserve">Sorry not much content here yet.

==== Presentations ====

[[vCenter Orchestrator APIs -  session from VMworld 2009 Developer day]]

[[Category: SDK]]</text>
    <sha1>e1bcada21c4660336bea4a2f1927eb51f8aea17b</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>VCenter Orchestrator APIs - session from VMworld 2009 Developer day</title>
  <ns>0</ns>
  <id>522</id>
  <revision>
    <id>1180</id>
    <timestamp>2010-06-03T09:59:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with 'Session from VMworld Developer Day 2009 presented by Stefan H. from Orchestrator Engineering   [http://vimeo.com/12251995 vimeo vCenter Orchestrator APIs ]  [Category: SDK] [Cate...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="191" xml:space="preserve">Session from VMworld Developer Day 2009 presented by Stefan H. from Orchestrator Engineering 

[http://vimeo.com/12251995 vimeo vCenter Orchestrator APIs ]

[Category: SDK] [Category: Videos]</text>
    <sha1>b7b60c5f654506c2e9818370b9a28ca5a5384a65</sha1>
  </revision>
  <revision>
    <id>1181</id>
    <parentid>1180</parentid>
    <timestamp>2010-06-03T09:59:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="195" xml:space="preserve">Session from VMworld Developer Day 2009 presented by Stefan H. from Orchestrator Engineering 

[http://vimeo.com/12251995 vimeo vCenter Orchestrator APIs ]

[[Category: SDK]] [[Category: Videos]]</text>
    <sha1>170d76b667dd712044f8a4849fb7217fe1f681aa</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>1183</id>
    <parentid>1120</parentid>
    <timestamp>2010-07-31T10:52:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>updating the resources with Luc Deken's, Jonathan Medd's and William Lam's blogs (sorry it took me so long guys kepts on forgetting to update this page)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2029" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

*[http://www.vm4all.com/ Eric Sloof's vm4all VMware Tools Repository]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>0c22417b5e4003b92002f4c00b5788ac4a9314b1</sha1>
  </revision>
  <revision>
    <id>1192</id>
    <parentid>1183</parentid>
    <timestamp>2010-09-01T21:16:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>add developer cheat sheet site</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2082" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

*[http://www.vm4all.com/ Eric Sloof's vm4all VMware Tools Repository]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>e0cf13cee1d686a4ffbeb51642fe588b5f908375</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>PowerCLI</title>
  <ns>0</ns>
  <id>524</id>
  <revision>
    <id>1185</id>
    <timestamp>2010-07-31T11:27:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Cleaning up: moving PowerCLI from the powershell page to its own page.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3762" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[Powershell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>15a4dbbb2da017ae0ad3f5c2603d012f21267ca9</sha1>
  </revision>
  <revision>
    <id>1187</id>
    <parentid>1185</parentid>
    <timestamp>2010-07-31T11:37:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>added link to Ricky El-Qasem's powerCLI lessons</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3859" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[Powershell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>19d369b409e5e591e9a8f07883b8a92d2d284eb8</sha1>
  </revision>
  <revision>
    <id>1188</id>
    <parentid>1187</parentid>
    <timestamp>2010-07-31T11:44:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3859" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>78ffe93acf6ee3b3c680b6c0bb5c3b9ed77d93de</sha1>
  </revision>
  <revision>
    <id>1196</id>
    <parentid>1188</parentid>
    <timestamp>2010-10-29T18:32:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Adding link to VM as XML export script from Doug Yould</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3909" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]
===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>24d9818128d569f5b44d5e9649e84513c4297f35</sha1>
  </revision>
  <revision>
    <id>1199</id>
    <parentid>1196</parentid>
    <timestamp>2010-10-30T18:44:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Adding link to Arnim van Lieshout's scripts for matching VM and Windows hard disks</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3959" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>c419d95ca0227248fa90097ca2c27b2f17a9bd3f</sha1>
  </revision>
  <revision>
    <id>1201</id>
    <parentid>1199</parentid>
    <timestamp>2010-11-04T00:47:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added link to vmworld powerCLI lab manual</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4115" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>9cee48b99cf0ec6bd83a29cf0e8729040205389c</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Powershell techniques and tips</title>
  <ns>0</ns>
  <id>512</id>
  <revision>
    <id>1189</id>
    <parentid>1136</parentid>
    <timestamp>2010-07-31T11:45:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2819" xml:space="preserve">==== General powershell techniques and tips ====

* [http://blogs.msdn.com/powershell/archive/2006/11/03/erroraction-and-errorvariable.aspx Error handling in Powershell]

* [http://blog.sapien.com/index.php/2009/05/12/a-powershell-port-scan/ A powershell port scan]

* [[Remote WMI defrag script]]

* [http://stackoverflow.com/questions/893295/what-are-some-of-the-most-useful-yet-little-known-features-in-the-powershell-lang useful less known features in powershell]

* [http://www.microsoft.com/technet/scriptcenter/default.mspx MS Technet scriptcenter]

* [http://www.virtu-al.net/2009/07/10/running-a-powercli-scheduled-task/ Virtu-al: Running a PowerCLI Scheduled task]

* [http://blog.geekpoet.net/2008/04/powershell-script-to-report-on-all.html Geekpoet: Report on all scheduled tasks in your domain]

* [http://www.peetersonline.nl/index.php/powershell/user-confirmation-in-powershell/ Peetersonline: User Confirmation in Powershell]

* [http://autopowershell.com/projects/show/autops Autopowershell scripting host]

* [http://dmitrysotnikov.wordpress.com/2009/07/14/powerguiorg-now-with-about_-topics/ twitter @powerGuiOrg]

* [http://blogs.msdn.com/powershell/archive/2009/07/22/dynamic-binary-modules.aspx MSDN Powershell blog: Dynamically compile and load an assembly on Remote Host]

* [http://blogs.technet.com/heyscriptingguy/archive/2009/07/22/hey-scripting-guy-how-can-i-speed-up-my-windows-powershell-scripts.aspx Technet Blog: How can I speed up my Powershell scripts?]

* [http://www.nivot.org/2009/08/19/PowerShell20AConfigurableAndFlexibleScriptLoggerModule.aspx PowerShell 2.0: A Configurable and Flexible Script Logger Module]

* [http://www.idera.com/Products/Free-Tools/PowerShell-scripts/ Free SQL Server powershell scripts]

* [http://www.astroarch.com/blog/?p=11 Blue Gears: Power Shell-ism's Tales from a Linux Developer]

* [http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/09/07/parsing-powershell-scripts.aspx parsing PowerShell scripts]

* [http://dougfinke.com/blog/index.php/2009/09/28/try-powershell-an-interactive-tutorial/ Try PowerShell – An Interactive Tutorial]

* [http://www.dennisdamen.com/?p=17 Create MD5 Hash using PowerShell]

* [http://lunex.spaces.live.com/Blog/cns!64CB3857E28BD106!376.entry Multithreading In Powershell Version 2.0]

* [http://www.myitforum.com/myITWiki/(X(1)S(pgqkw0jfcpxe3r550sfpnxyf))/Default.aspx?Page=WPScripts&amp;NS=&amp;AspxAutoDetectCookieSupport=1 windows Powershell script repository]

* [http://powershell.com/cs/blogs/tobias/archive/2010/01/16/cancelling-a-pipeline.aspx Cancelling a Pipeline]

* [http://blogs.msdn.com/b/powershell/archive/2009/11/23/you-don-t-have-to-be-an-administrator-to-run-remote-powershell-commands.aspx You Don’t Have to Be An Administrator to Run Remote PowerShell Commands]

[[Category: Powershell]]</text>
    <sha1>e5674d98993ea0de1f2287052a11a83a93cabaaa</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>VMware Icons</title>
  <ns>0</ns>
  <id>423</id>
  <revision>
    <id>1193</id>
    <parentid>1138</parentid>
    <timestamp>2010-09-17T15:22:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="483" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints seem to have moved to:
http://viops.vmware.com/home/docs/DOC-1338

The icons can now be found here: http://communities.vmware.com/docs/DOC-9441

Correction, when VIOPS moved, the powerpoints have disappeared.

[[Category: VMware Artwork]]</text>
    <sha1>424cb85504d711092b5e17aedf02fa384692273b</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>VI Toolkit</title>
  <ns>0</ns>
  <id>19</id>
  <revision>
    <id>1195</id>
    <parentid>424</parentid>
    <timestamp>2010-09-17T22:02:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added pSphere python bindings for vSphere SDK project</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="441" xml:space="preserve">The VMware Infrastructure Toolkit is the interface to the VMware Infrastructure API (VI API) for administering your virtual machines and hosts.

[[VI Toolkit for windows]]

[[VI Toolkit for perl]]

[[VMware Infrastructure Java API]]

===3rd party ===

* [[Vitforjava]] merged with the above project

* [http://jkinred.bitbucket.org/psphere/ pSphere] pSphere provides native Python bindings for the vSphere Web Services SDK

[[Category: SDK]]</text>
    <sha1>99f91abccffe03c94bfe3f370d338409e2a5b9df</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>PowerCLI: Dump virtual machine info as XML</title>
  <ns>0</ns>
  <id>525</id>
  <revision>
    <id>1197</id>
    <timestamp>2010-10-29T18:45:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '=== get-VmInfoAsXML === Author: Doug Youd  ==== Description ==== Based on the [http://ict-freak.nl/2009/10/11/powercli-virtual-machine-disk-vmdk-info-v2-analyze-data-with-excel/ ...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="804" xml:space="preserve">=== get-VmInfoAsXML ===
Author: Doug Youd

==== Description ====
Based on the [http://ict-freak.nl/2009/10/11/powercli-virtual-machine-disk-vmdk-info-v2-analyze-data-with-excel/ PowerCLI: Virtual Machine Disk (VMDK) info v2: Analyze data with Excel] script by Arne Fokkema, this script will save your virtual machine info in an XML file.

The XML file is formatted for easier readability and contains -among others- the following information:
* List of VMs with
  * port groups with VLAN info
  * Datastore
  * Capacity in GB
  * CPU count
  * Memory size
  * Nic count
  * Disk count
  * full guest name


==== Location ====
[http://blog.cnidus.net/2010/10/25/dump-virtual-machine-info-as-xml-powershell/ Dump Virtual Machine Info as XML (powershell)]

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>f068d8814e9073e479ea51c4560dba7b974f2345</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Vmsvc/tools.cancelinstall</title>
  <ns>0</ns>
  <id>213</id>
  <revision>
    <id>1198</id>
    <parentid>395</parentid>
    <timestamp>2010-10-30T10:16:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added example from Bob Plankers to vimsh vmsvc/tools.cancelinstall</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="505" xml:space="preserve">==== vimsh vmsvc/tools.cancelinstall ====

Usage: tools.cancelinstall vmid

Cancel the tools installation process

==== Cancel a stuck vmware tools install ====

First find the vm id:
 vmware-cmd /vmfs/volumes/datastore-name/vm-folder/vmx-file.vmx getid

then run:
 vmware-vim-cmd vmsvc/tools.cancelinstall idnumber

See also: [http://lonesysadmin.net/2009/12/11/how-to-cancel-a-stuck-vmware-tools-install-from-the-esx-cli/ How to Cancel a Stuck VMware Tools Install from the ESX CLI]

[[Category: Vimsh]]</text>
    <sha1>73353a614756277aa197b1a4cdb166f79077714a</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>PowerCLI: Match VM and Windows hard disks</title>
  <ns>0</ns>
  <id>526</id>
  <revision>
    <id>1200</id>
    <timestamp>2010-10-30T18:44:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '=== Map VM Disks === Author: Arnim van Lieshout  ==== Description ==== Based on the [http://www.peetersonline.nl/index.php/vmware/get-vmware-disk-usage-with-powershell/ Get VMwar...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1075" xml:space="preserve">=== Map VM Disks ===
Author: Arnim van Lieshout

==== Description ====
Based on the [http://www.peetersonline.nl/index.php/vmware/get-vmware-disk-usage-with-powershell/ Get VMware Disk Usage with Powershell] script by Hugo Peeters, this script will identify the locations of the virtual disks used by your virtual machines.

Arnim explains how the mechanism in windows works, which is a little bit different from what you would expect and then applies his knowledge to both Powershell as well as WMI scripts to retrieve the details he needs for getting this to work.
He even throws in how-to add this code to the VESI Powerpack

The information retrieved per VM is:
* SCSI Controller
* DiskName
* SCSI ID
* Disk File
* Disk Size
* Windows Disk ID


==== Location ====
[http://www.van-lieshout.com/2009/12/match-vm-and-windows-harddisks-using-powercli/ Match VM and Windows harddisks using PowerCLI]

[http://www.van-lieshout.com/2010/02/powercli-match-vm-and-windows-harddisks-part-2/ Match VM and Windows harddisks part 2]

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>80a2b5274eec7666132ce9bae2aa76631b5312e9</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Talk:Main Page</title>
  <ns>1</ns>
  <id>527</id>
  <revision>
    <id>1202</id>
    <timestamp>2010-11-22T21:26:59Z</timestamp>
    <contributor>
      <username>Raymond</username>
      <id>41</id>
    </contributor>
    <comment>vim-cmd hostsvc/storage/datastore_browser_search</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="199" xml:space="preserve">I am trying to execute the following command but have been unsuccessful till now :

vim-cmd hostsvc/storage/datastore_browser_search

please if anyone can help with a sample output

Thanks!

~Raymond</text>
    <sha1>17aa29108ec689400481eb2a37cde77d705b3b61</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>VIOPS VMware Icons and diagrams</title>
  <ns>0</ns>
  <id>469</id>
  <revision>
    <id>1204</id>
    <parentid>1137</parentid>
    <timestamp>2010-12-23T18:19:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added latest update from Maish his visio stencils.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="861" xml:space="preserve">Visio stencils made from the artwork as released by the official VMware branding team.
Can be used for documentation, now also includes vSphere artwork.


[http://viops.vmware.com/home/docs/DOC-1514  VIOPS: Visio Stencils for vSphere]
and
http://viops.vmware.com/home/docs/DOC-1338

Unfortunately these visio stencils have disappeared, even after asking the VMTN team about this a couple of months ago, they are still gone.
An alternative can be found here: [http://technodrone.blogspot.com/2009/12/my-visio-stencils-again.html Technodrone: My Visio stencils again] There's a few other places on the web with visio templates, see the category below for more or search for visio.
Update on Maish's his Visio stencils: [http://technodrone.blogspot.com/2010/12/visio-stencils-happy-holiday-to-you-all.html New vSphere vision stencils]

[[Category: VMware Artwork]]</text>
    <sha1>ec2a5e3240fed7929df500beecf667ea113410f9</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1205</id>
    <parentid>940</parentid>
    <timestamp>2011-01-30T17:27:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added info about the vitoolkit twitter account</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3452" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since January 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

Starting February 2011, the [http://www.twitter.com/vitoolkit @vitoolkit twitter account] that accompanies this site is also active. It will retweet/tweet about VMware specific code, scripts or info related to the VMware api's. It will NOT be used for anything else, there's not going to be any social or commercial tweets. 

==== Contribute / help out ====
This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics, search and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you. 

Search tip:
For searching your search term MUST be at least 4 characters long so searching for "VT" or "ESX" will return nothing while there's still content describing this. Instead try another longer related search term like "BIOS" or "backup" for what you are trying to find.

As extra help, the categories are listed below as well.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware Artwork&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>dcbd4410004e7b847178796dd40978b26975c297</sha1>
  </revision>
</page>
<page arvcontinue="20100302213730|1154">
  <title>Hostsvc/hosthardware</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>1206</id>
    <parentid>525</parentid>
    <timestamp>2011-01-31T20:17:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>add link to vmware KB to retrieve NX/XD flag</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24054" xml:space="preserve">==== Vimsh Hostsvc/hosthardware ====
Usage: hosthardware

Retrieves the host hardware information.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password hostsvc/hosthardware
 (vim.host.HardwareInfo) {
   dynamicType = &lt;unset&gt;,
   systemInfo = (vim.host.SystemInfo) {
      dynamicType = &lt;unset&gt;,
      vendor = "VMware, Inc.",
      model = "VMware Virtual Platform",
      uuid = "238ef3e5-a923-b48c-5ab7-0d820b1cbde7",
      otherIdentifyingInfo = (vim.host.SystemIdentificationInfo) [
         (vim.host.SystemIdentificationInfo) {
            dynamicType = &lt;unset&gt;,
            identifierValue = " No Asset Tag",
            identifierType = (vim.ElementDescription) {
               dynamicType = &lt;unset&gt;,
               label = "AssetTag",
               summary = "AssetTag",
               key = "AssetTag",
            },
         }
      ],
   },
   cpuInfo = (vim.host.CpuInfo) {
      dynamicType = &lt;unset&gt;,
      numCpuPackages = 2,
      numCpuCores = 2,
      numCpuThreads = 2,
      hz = 2407469482,
   },
   cpuPkg = (vim.host.CpuPackage) [
      (vim.host.CpuPackage) {
         dynamicType = &lt;unset&gt;,
         index = 0,
         vendor = "intel",
         hz = 2407469482,
         busHz = 65958068,
         description = "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz",
         threadId = (short) [
            0
         ],
         cpuFeature = (vim.host.CpuIdInfo) [
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 0,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:1010",
               ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
               ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
               edx = "0100:1001:0110:0101:0110:1110:0110:1001",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 1,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0110:1111:1011",
               ebx = "0000:0000:0000:0001:0000:1000:0000:0000",
               ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
               edx = "0000:1111:1110:1011:1111:1011:1111:1111",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483648,
               vendor = &lt;unset&gt;,
               eax = "1000:0000:0000:0000:0000:0000:0000:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483647,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:0000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
               edx = "0010:0000:0001:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483640,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0011:0000:0010:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            }
         ],
      },
      (vim.host.CpuPackage) {
         dynamicType = &lt;unset&gt;,
         index = 1,
         vendor = "intel",
         hz = 2407469482,
         busHz = 65958068,
         description = "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz",
         threadId = (short) [
            1
         ],
         cpuFeature = (vim.host.CpuIdInfo) [
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 0,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:1010",
               ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
               ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
               edx = "0100:1001:0110:0101:0110:1110:0110:1001",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = 1,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0110:1111:1011",
               ebx = "0000:0010:0000:0001:0000:1000:0000:0000",
               ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
               edx = "0000:1111:1110:1011:1111:1011:1111:1111",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483648,
               vendor = &lt;unset&gt;,
               eax = "1000:0000:0000:0000:0000:0000:0000:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483647,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0000:0000:0000:0000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
               edx = "0010:0000:0001:0000:0000:0000:0000:0000",
            },
            (vim.host.CpuIdInfo) {
               dynamicType = &lt;unset&gt;,
               level = -2147483640,
               vendor = &lt;unset&gt;,
               eax = "0000:0000:0000:0000:0011:0000:0010:1000",
               ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
               ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
               edx = "0000:0000:0000:0000:0000:0000:0000:0000",
            }
         ],
      }
   ],
   memorySize = 1771626496,
   numaInfo = (vim.host.NumaInfo) {
      dynamicType = &lt;unset&gt;,
      type = "Fake Numa",
      numNodes = 1,
      numaNode = (vim.host.NumaNode) [
         (vim.host.NumaNode) {
            dynamicType = &lt;unset&gt;,
            typeId = 0,
            cpuID = (short) [
               1,
               0
            ],
            memoryRangeBegin = 0,
            memoryRangeLength = 1879048192,
         }
      ],
   },
   pciDevice = (vim.host.PciDevice) [
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:00.0",
         classId = 1536,
         bus = 0,
         slot = 0,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 29072,
         subDeviceId = 6518,
         deviceName = "440BX/ZX/DX - 82443BX/ZX/DX Host bridge",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:01.0",
         classId = 1540,
         bus = 0,
         slot = 1,
         function = 0,
         vendorId = -32634,
         subVendorId = 0,
         vendorName = "Intel Corporation",
         deviceId = 29073,
         subDeviceId = 0,
         deviceName = "440BX/ZX/DX - 82443BX/ZX/DX AGP bridge",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.0",
         classId = 1537,
         bus = 0,
         slot = 7,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28944,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 ISA",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.1",
         classId = 257,
         bus = 0,
         slot = 7,
         function = 1,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28945,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 IDE",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.3",
         classId = 1664,
         bus = 0,
         slot = 7,
         function = 3,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 28947,
         subDeviceId = 6518,
         deviceName = "82371AB/EB/MB PIIX4 ACPI",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:07.7",
         classId = 2176,
         bus = 0,
         slot = 7,
         function = 7,
         vendorId = 5549,
         subVendorId = 5549,
         vendorName = "VMWare Inc",
         deviceId = 1856,
         subDeviceId = 1856,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:0f.0",
         classId = 768,
         bus = 0,
         slot = 15,
         function = 0,
         vendorId = 5549,
         subVendorId = 5549,
         vendorName = "VMWare Inc",
         deviceId = 1029,
         subDeviceId = 1029,
         deviceName = "Virtual SVGA",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:10.0",
         classId = 256,
         bus = 0,
         slot = 16,
         function = 0,
         vendorId = 4096,
         subVendorId = 5549,
         vendorName = "LSI Logic / Symbios Logic",
         deviceId = 48,
         subDeviceId = 6518,
         deviceName = "53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:11.0",
         classId = 1540,
         bus = 0,
         slot = 17,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1936,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.0",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.1",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.2",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.3",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.4",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.5",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.6",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:15.7",
         classId = 1540,
         bus = 0,
         slot = 21,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.0",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.1",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.2",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.3",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.4",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.5",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.6",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:16.7",
         classId = 1540,
         bus = 0,
         slot = 22,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.0",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.1",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.2",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.3",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.4",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.5",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.6",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:17.7",
         classId = 1540,
         bus = 0,
         slot = 23,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.0",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 0,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.1",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 1,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.2",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 2,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.3",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 3,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.4",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 4,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.5",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 5,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.6",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 6,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "00:18.7",
         classId = 1540,
         bus = 0,
         slot = 24,
         function = 7,
         vendorId = 5549,
         subVendorId = 0,
         vendorName = "VMWare Inc",
         deviceId = 1952,
         subDeviceId = 0,
         deviceName = "Unknown",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "02:00.0",
         classId = 512,
         bus = 2,
         slot = 0,
         function = 0,
         vendorId = -32634,
         subVendorId = 5549,
         vendorName = "Intel Corporation",
         deviceId = 4111,
         subDeviceId = 1872,
         deviceName = "82545EM Gigabit Ethernet Controller (Copper)",
      },
      (vim.host.PciDevice) {
         dynamicType = &lt;unset&gt;,
         id = "02:01.0",
         classId = 512,
         bus = 2,
         slot = 1,
         function = 0,
         vendorId = 4130,
         subVendorId = 4130,
         vendorName = "Advanced Micro Devices [AMD]",
         deviceId = 8192,
         subDeviceId = 8192,
         deviceName = "NetFinity 10/100 Fast Ethernet",
      }
   ],
   cpuFeature = (vim.host.CpuIdInfo) [
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = 0,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0000:0000:1010",
         ebx = "0111:0101:0110:1110:0110:0101:0100:0111",
         ecx = "0110:1100:0110:0101:0111:0100:0110:1110",
         edx = "0100:1001:0110:0101:0110:1110:0110:1001",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = 1,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0110:1111:1011",
         ebx = "0000:0000:0000:0001:0000:1000:0000:0000",
         ecx = "1000:0000:0000:0000:0010:0010:0000:0001",
         edx = "0000:1111:1110:1011:1111:1011:1111:1111",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483648,
         vendor = &lt;unset&gt;,
         eax = "1000:0000:0000:0000:0000:0000:0000:1000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
         edx = "0000:0000:0000:0000:0000:0000:0000:0000",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483647,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0000:0000:0000:0000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0001",
         edx = "0000:0000:0001:0000:0000:0000:0000:0000",
      },
      (vim.host.CpuIdInfo) {
         dynamicType = &lt;unset&gt;,
         level = -2147483640,
         vendor = &lt;unset&gt;,
         eax = "0000:0000:0000:0000:0011:0000:0010:1000",
         ebx = "0000:0000:0000:0000:0000:0000:0000:0000",
         ecx = "0000:0000:0000:0000:0000:0000:0000:0000",
         edx = "0000:0000:0000:0000:0000:0000:0000:0000",
      }
   ],
   biosInfo = (vim.host.BIOSInfo) {
      dynamicType = &lt;unset&gt;,
      biosVersion = "6.00",
      releaseDate = "2008-07-29T00:00:00Z",
   },
 }

==== See also ====

[http://kb.vmware.com/kb/1031785 Checking cpuinfo information on an ESXi host for NX/XD flag]

[[Category: Vimsh]]</text>
    <sha1>021e58c3b86bdfcc2e7f214716f025e1d06fb915</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>VI-Toolkit:Community Portal</title>
  <ns>4</ns>
  <id>6</id>
  <revision>
    <id>1207</id>
    <parentid>1006</parentid>
    <timestamp>2011-02-01T10:34:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1240" xml:space="preserve">==== Main Index ====
The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

[[VMware KB articles]]

==== Management Virtual Machines  ====
VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and VMware [[VI Perl Toolkit]] to aide in managing your VI infrastructure.

In vSphere we now use the [[vMA]] appliance, documentation is here http://www.vmware.com/support/developer/vcli/</text>
    <sha1>1fb1c7893a51063c3ad8520e892f971432777aff</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>VMware KB articles</title>
  <ns>0</ns>
  <id>528</id>
  <revision>
    <id>1208</id>
    <timestamp>2011-02-01T10:37:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with '==== VMware KB articles ====  There's very interesting code specific Knowledge Base articles to be found.  I'm trying to list them here.  [http://kb.vmware.com/kb/1033447 Recomme...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="786" xml:space="preserve">==== VMware KB articles ====

There's very interesting code specific Knowledge Base articles to be found. 
I'm trying to list them here.

[http://kb.vmware.com/kb/1033447 Recommended values in the soapAction field when forming Soap Requests for vSphere API]

[http://kb.vmware.com/kb/1007289 Changing or blocking the default ports 80 (http) and 443 (https) on ESX hosts]


[http://kb.vmware.com/kb/738107 What is the syntax for vmware-cmd createsnapshot?]

[http://kb.vmware.com/kb/1019561 Collecting VIX diagnostic information]

[http://kb.vmware.com/kb/1026554 Enabling logging for Likewise agents on ESX/ESXi 4.1]

[http://kb.vmware.com/kb/1033317 Recording ESX or ESXi VMkernel state with vsi_traverse]

[http://kb.vmware.com/kb/1031785 Checking cpuinfo information on an ESXi host]</text>
    <sha1>17d803e938c15cf2a39902bff6b62a85b995c36e</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>VI-Toolkit:Users</title>
  <ns>4</ns>
  <id>2</id>
  <revision>
    <id>1209</id>
    <parentid>438</parentid>
    <timestamp>2011-02-09T15:19:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Notice about disabling anonymous account creation due to spam posts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1382" xml:space="preserve">=== Anonymous access ===
We do not allow anonymous edits on this web site. 
The sole reason for this is to combat spam. It would be awesome to allow completely anonymous edits, but I currently do not see how.
Please do ''' not let you stop that '''... getting an account for the site is about 2 minutes of ''work''.

=== Join Us! ===
You are welcome to add/edit content to the site after signing up for a user account.
Joining the site only requires a working email address and a name. We will under no circumstance abuse your email address or give it to someone else, it is only used for the initial sign up.

You can sign up [[Special:UserLogin| here]]

** 2011-02-09 Sorry, anonymous account signup has been disabled due to some severe spamming action, will look into a workaround for that later. If you want to help out, then I can create an account for you, just send me an email in that case and give me a little background on what you intend to add **

=== New content rules ===
When adding content there is a restriction that the subject must be about VMware related products, problems or solutions.
For the moment we do not welcome posts with a clear commercial intent where a user is endorsing his or her product.
This rule might change in the future, it is not cast in stone. 

If you have a question about that then send [[User:wila|me]] an email.

[[Category: website]]</text>
    <sha1>e007ace728f10a0ad99b44ae3ed354b47114f14f</sha1>
  </revision>
  <revision>
    <id>1210</id>
    <parentid>1209</parentid>
    <timestamp>2011-02-09T16:04:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1387" xml:space="preserve">=== Anonymous access ===
We do not allow anonymous edits on this web site. 
The sole reason for this is to combat spam. It would be awesome to allow completely anonymous edits, but I currently do not see how.
Please do ''' not let you stop that '''... getting an account for the site is about 2 minutes of ''work''.

=== Join Us! ===
You are welcome to add/edit content to the site after signing up for a user account.
Joining the site only requires a working email address and a name. We will under no circumstance abuse your email address or give it to someone else, it is only used for the initial sign up.

You can sign up [[Special:UserLogin| here]]

* 2011-02-09 Sorry, anonymous ''' account signup has been disabled ''' due to some severe spamming action, will look into a workaround for that later. If you want to help out, then I can create an account for you, just send me an email in that case and give me a little background on what you intend to add.

=== New content rules ===
When adding content there is a restriction that the subject must be about VMware related products, problems or solutions.
For the moment we do not welcome posts with a clear commercial intent where a user is endorsing his or her product.
This rule might change in the future, it is not cast in stone. 

If you have a question about that then send [[User:wila|me]] an email.

[[Category: website]]</text>
    <sha1>cc98327b37c4193ba95c5aec67081133c5fb3f8b</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>1211</id>
    <parentid>1192</parentid>
    <timestamp>2011-03-23T20:59:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2226" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://twitter.com/PowerCLITip @PowerCLITip] Learn #PowerCLI one tweet at a time by following updates from @PowerCLITip #VMware #PowerShell

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

*[http://www.vm4all.com/ Eric Sloof's vm4all VMware Tools Repository]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>1266bd6de169fac2b29fb2629c3cf28fd570b6ec</sha1>
  </revision>
  <revision>
    <id>1213</id>
    <parentid>1211</parentid>
    <timestamp>2013-01-23T17:49:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2155" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://twitter.com/PowerCLITip @PowerCLITip] Learn #PowerCLI one tweet at a time by following updates from @PowerCLITip #VMware #PowerShell

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>853a35a2aebe27ae36b600cf94a3241b86912146</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1212</id>
    <parentid>1205</parentid>
    <timestamp>2013-01-23T17:45:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3714" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since January 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

&lt;s&gt;Starting February 2011, the [http://www.twitter.com/vitoolkit @vitoolkit twitter account] that accompanies this site is also active. It will retweet/tweet about VMware specific code, scripts or info related to the VMware api's. It will NOT be used for anything else, there's not going to be any social or commercial tweets. &lt;/s&gt; Early 2012 the site and twitter account had been put on hold due to some family health issues, which made me focus on that. 
Not sure if the twitter account will be resurrected, but I do expect that the site will be active again in 2013. Guess we'll see.

==== Contribute / help out ====
This is an OPEN wiki site and we encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics, search and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you. 

Search tip:
For searching your search term MUST be at least 4 characters long so searching for "VT" or "ESX" will return nothing while there's still content describing this. Instead try another longer related search term like "BIOS" or "backup" for what you are trying to find.

As extra help, the categories are listed below as well.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware Artwork&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>c470217b65b9fa6bcf7616f760fa23d00981ce22</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>VI-Toolkit:Community portal</title>
  <ns>4</ns>
  <id>529</id>
  <revision>
    <id>1214</id>
    <timestamp>2013-01-23T17:56:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Not sure why, but the content of this page was gone, resurrected it</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1215" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

[[VMware KB articles]]

===Management Virtual Machines===

VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and VMware [[VI Perl Toolkit]] to aide in managing your VI infrastructure.

In vSphere we now use the [[vMA]] appliance, documentation is here http://www.vmware.com/support/developer/vcli/</text>
    <sha1>0b60fa28490944b1127bfde827d0deebda838071</sha1>
  </revision>
  <revision>
    <id>1215</id>
    <parentid>1214</parentid>
    <timestamp>2013-01-23T17:58:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1225" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[Ruby]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

[[VMware KB articles]]

===Management Virtual Machines===

VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and VMware [[VI Perl Toolkit]] to aide in managing your VI infrastructure.

In vSphere we now use the [[vMA]] appliance, documentation is here http://www.vmware.com/support/developer/vcli/</text>
    <sha1>553a5b0f9767a10caef5e4741c3f9451a58046b8</sha1>
  </revision>
  <revision>
    <id>1225</id>
    <parentid>1215</parentid>
    <timestamp>2013-01-24T04:53:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1237" xml:space="preserve">The starting point for any developer is http://www.vmware.com/developer but as there is a overwhelming amount of information available, we are trying to make it easier accessible on this site.

Hopefully we'll succeed at that over time, it is a pretty high goal. It certainly isn't the case yet, but time will tell.

[[SDK]]

[[Java]]

[[Perl]]

[[Python]]

[[Ruby]]

[[PowerShell]]

[[VI Plugin]]

[[scripts]]

[[Projects]]

[[Virtualisation technical articles]]

[[VMware KB articles]]

===Management Virtual Machines===

VMware ESX 3.5 and earlier had the management Service Console, a stripped down RHEL console which was could be used for automating and managing your virtual machines. As of ESXi 3.5 this is no longer available and the future is to move away from this "fat hypervisor". In order to manage your virtual machines in a similar way as before, we now have special virtual machine that come with management software pre-installed. VMware delivers this as a virtual appliances called VMware [[VIMA]] containing [[RCLI]] (Remote CLI) and VMware [[VI Perl Toolkit]] to aide in managing your VI infrastructure.

In vSphere we now use the [[vMA]] appliance, documentation is here http://www.vmware.com/support/developer/vcli/</text>
    <sha1>f13098c6e0e1b3cece6e08cf594b7365ba3c215e</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Ruby</title>
  <ns>0</ns>
  <id>530</id>
  <revision>
    <id>1216</id>
    <timestamp>2013-01-23T18:01:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "  https://github.com/cjohannsen/vco-rest/blob/master/lib/vco-rest.rb    [[Category: Ruby]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="90" xml:space="preserve">

https://github.com/cjohannsen/vco-rest/blob/master/lib/vco-rest.rb


[[Category: Ruby]]</text>
    <sha1>ae701b406b0f53820bb7ac273089a7008753ca04</sha1>
  </revision>
  <revision>
    <id>1217</id>
    <parentid>1216</parentid>
    <timestamp>2013-01-23T18:03:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="36" xml:space="preserve">
[[vco-rest]]


[[Category: Ruby]]</text>
    <sha1>d06214c184a38f88680ff6db02997b4d17ad5684</sha1>
  </revision>
  <revision>
    <id>1219</id>
    <parentid>1217</parentid>
    <timestamp>2013-01-23T18:08:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">
[[vco-rest]]


[[vixen]]


[[Category: Ruby]]</text>
    <sha1>747d7d78135c485bf9a156f6d42f42368535f5e4</sha1>
  </revision>
  <revision>
    <id>1244</id>
    <parentid>1219</parentid>
    <timestamp>2013-07-23T10:50:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="58" xml:space="preserve">
[[vco-rest]]


[[vixen]]

[[rbvmomi]]

[[Category: Ruby]]</text>
    <sha1>b620b6f0c9c8201e326d7fb8a9808daf61e49e61</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Vco-rest</title>
  <ns>0</ns>
  <id>531</id>
  <revision>
    <id>1218</id>
    <timestamp>2013-01-23T18:06:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "====vco-rest==== Author: Christian Johannsen  ====Description==== VMware vCenter Orchestrator gem (unofficial)  This gem captures the main methods using VMware vCenter Orchest..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="268" xml:space="preserve">====vco-rest====
Author: Christian Johannsen 
====Description====
VMware vCenter Orchestrator gem (unofficial)

This gem captures the main methods using VMware vCenter Orchestrator REST API.

====Location====

https://github.com/cjohannsen/vco-rest

[[Category: Ruby]]</text>
    <sha1>121e5990cd7492d8df12d1775f635221ab6471e2</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Vixen</title>
  <ns>0</ns>
  <id>532</id>
  <revision>
    <id>1220</id>
    <timestamp>2013-01-23T18:11:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===vixen=== author: Jeff Weiss ====Description==== Ruby bindings for the VMware VIX API   ====Location==== https://github.com/jeffweiss/vixen  [[Category: Ruby]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="161" xml:space="preserve">===vixen===
author: Jeff Weiss
====Description====
Ruby bindings for the VMware VIX API 

====Location====
https://github.com/jeffweiss/vixen

[[Category: Ruby]]</text>
    <sha1>0e991968785c314814351dc1be1b4703c981286b</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI</title>
  <ns>0</ns>
  <id>524</id>
  <revision>
    <id>1221</id>
    <parentid>1201</parentid>
    <timestamp>2013-01-24T03:47:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4145" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>5669d18b15e4d0e0ba7f7e5ac58dc8d8ab256478</sha1>
  </revision>
  <revision>
    <id>1223</id>
    <parentid>1221</parentid>
    <timestamp>2013-01-24T04:02:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4198" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]


[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>766aeb66482bc35a74b9b7f759528b032a35b5a7</sha1>
  </revision>
  <revision>
    <id>1230</id>
    <parentid>1223</parentid>
    <timestamp>2013-01-24T12:21:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4239" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]


==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>7143fccb0f9c7f4eeb732a8da9b4e830fe942415</sha1>
  </revision>
  <revision>
    <id>1232</id>
    <parentid>1230</parentid>
    <timestamp>2013-01-24T12:35:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4359" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>c852990d8f541c603a3241a11000e99ab7a5d449</sha1>
  </revision>
  <revision>
    <id>1234</id>
    <parentid>1232</parentid>
    <timestamp>2013-01-26T13:17:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4506" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>e1768b2fe9b2fca1313def31d6a43443187b07e4</sha1>
  </revision>
  <revision>
    <id>1235</id>
    <parentid>1234</parentid>
    <timestamp>2013-06-30T23:13:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VM Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4547" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>5e0ca216c0b60b01bce7589f43a21328fb03beac</sha1>
  </revision>
  <revision>
    <id>1238</id>
    <parentid>1235</parentid>
    <timestamp>2013-07-03T12:35:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VM Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4615" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>f4d54a09820b8b57a4b6b4c0186d8e2eb34f5891</sha1>
  </revision>
  <revision>
    <id>1242</id>
    <parentid>1238</parentid>
    <timestamp>2013-07-23T10:39:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4663" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Upgrading your VMFS datastores]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>f3f7a100c5162186da7142756387419d4458a54c</sha1>
  </revision>
  <revision>
    <id>1250</id>
    <parentid>1242</parentid>
    <timestamp>2013-07-23T22:17:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VM Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4727" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools - Part 2 - Create a nested hypervisor]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Upgrading your VMFS datastores]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>8f328db77fe771ab8a9adae97f38c9e2bd63a9e7</sha1>
  </revision>
  <revision>
    <id>1251</id>
    <parentid>1250</parentid>
    <timestamp>2013-07-23T22:17:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VM Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4731" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Upgrading your VMFS datastores]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>e1fa9e4fab771396c1ccc7dad229300b4b9a2110</sha1>
  </revision>
  <revision>
    <id>1253</id>
    <parentid>1251</parentid>
    <timestamp>2013-07-24T17:31:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4775" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Get VMHost Support Bundles]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>69beefb0c3e0581ff33826d0ba043270695b15be</sha1>
  </revision>
  <revision>
    <id>1256</id>
    <parentid>1253</parentid>
    <timestamp>2013-07-29T18:04:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4831" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>3a026b015538c3425b702e294ca76614e8687fb7</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI: Cluster Load</title>
  <ns>0</ns>
  <id>533</id>
  <revision>
    <id>1222</id>
    <timestamp>2013-01-24T03:52:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "=== Cluster Load === author: Ammesiah  ==== Description ==== Displays the load of your cluster as colored bars using ascii art.  ==== Usage ====  Get-ClusterLoad -ClusterName ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="332" xml:space="preserve">=== Cluster Load ===
author: Ammesiah

==== Description ====
Displays the load of your cluster as colored bars using ascii art.

==== Usage ====
 Get-ClusterLoad -ClusterName vCluster01,vCluster02

==== Location ====

http://www.vmdude.fr/en/scripts-en/cluster-load-in-powercli/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>12ff179341bc31e27909f8338526fbc6c1b8a3df</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI: Determine vSwitch vmnic for your VM</title>
  <ns>0</ns>
  <id>534</id>
  <revision>
    <id>1224</id>
    <timestamp>2013-01-24T04:08:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "=== Determine vSwitch vmnic for your VM === author: Matt Boren ==== Description ==== Script that lists all the VMs with vmnic uplink and vSwitch for a selected host.   ==== Us..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1027" xml:space="preserve">=== Determine vSwitch vmnic for your VM ===
author: Matt Boren
==== Description ====
Script that lists all the VMs with vmnic uplink and vSwitch for a selected host.


==== Usage ====
 PS vNuggs:\&gt; Get-VNUplinkNic -VMHostToCheck somehost
  
 Need credentials to connect to VMHost
 Please enter credentials for 'somehost'
 User: root
 Password for user root: *************
 
 VMName         TeamUplink   vSwitch     VMHostName
 ----------     ----------   -------     ---------- 
 Management     n/a          vSwitch0    somehost
 vmk1           vmnic0       vSwitch0    somehost
 vmk0           vmnic0       vSwitch0    somehost
 dev0-vm0       vmnic0       vSwitch0    somehost
 dev0-vm12323   vmnic5       vSwitch0    somehost
 dev0-vm2       vmnic5       vSwitch0    somehost
 dev0-vm32237   vmnic4       vSwitch1    somehost
 dev0-vm9       vmnic8       vSwitch1    somehost
 ...
==== Location ====

http://vnugglets.com/2013/01/determine-vms-uplink-vmnic-on-vswitch.html

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>63c987dd6a81a2fe8e8e718e9ad04e2f3fc43a59</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Python</title>
  <ns>0</ns>
  <id>535</id>
  <revision>
    <id>1226</id>
    <timestamp>2013-01-24T04:53:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with " [[pysphere]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">
[[pysphere]]</text>
    <sha1>41eb71cc9a81765003375b9fddf59793e02fcb53</sha1>
  </revision>
  <revision>
    <id>1227</id>
    <parentid>1226</parentid>
    <timestamp>2013-01-24T04:54:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="35" xml:space="preserve">
[[pysphere]]

[[Category: Python]]</text>
    <sha1>8daa60173629bb60525874bc4fc94c0d7bcabcc8</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Pysphere</title>
  <ns>0</ns>
  <id>536</id>
  <revision>
    <id>1228</id>
    <timestamp>2013-01-24T05:01:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  pysphere === author: Sebastián Tello ==== Description ==== Python API to interact with the vSphere Web Services SDK.  This python SDK provides an easy interface to:  *Co..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="943" xml:space="preserve">===  pysphere ===
author: Sebastián Tello
==== Description ====
Python API to interact with the vSphere Web Services SDK.

This python SDK provides an easy interface to:

*Connect to VMWare's ESX, ESXi, Virtual Center, Virtual Server hosts
*Query hosts, datacenters, resource pools, virtual machines
*VM: Power on, power off, reset, revert to snapshot, get properties, update vmware tools, clone, migrate.
*vSphere 5.0 Guest Operations: create/delete/move files and directories. Upload/download files from the guest system. List/start/stop processes in the guest system.
*Create and delete snapshots
*Hosts statistics and performance monitoring 

And of course, you can use it to access all of the vSphere API through python. 
==== Usage ====
Please see the google.com page below and the project's [http://code.google.com/p/pysphere/w/list wiki]. 
==== Location ====

http://code.google.com/p/pysphere/

[[Category: Python]] [[Category: SDK]]</text>
    <sha1>eda7a0da861d25754457a428bc50b5ae2287521c</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>SDK</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>1229</id>
    <parentid>1194</parentid>
    <timestamp>2013-01-24T06:33:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Addded links to "introduction to vSphere API" pages</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="794" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

[[VMware Icons]]

[[vCenter Orchestrator]]

==== External links ====

[http://blogs.vmware.com/vsphere/2012/02/introduction-to-the-vsphere-api-part-1.html Introduction to the vSphere API Part 1: Overview]

[http://blogs.vmware.com/vsphere/2012/02/introduction-to-the-vsphere-api-part-2-object-model.html Introduction to the vSphere API Part 2: Object Model]


[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's

[http://communities.vmware.com/community/developer/forums/vcloudapi VMware vCloud API forums]

[http://communities.vmware.com/community/beta/vcloudsdkphp VMware vCloud php SDK beta]

[[Category: SDK]]</text>
    <sha1>778ddd4b0ba1de7e92391f119489e00d4ea9c90f</sha1>
  </revision>
  <revision>
    <id>1233</id>
    <parentid>1229</parentid>
    <timestamp>2013-01-26T13:11:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Added excerpt of vCloud Throwdown's plus links from Jake Robinson</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1189" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

[[VMware Icons]]

[[vCenter Orchestrator]]

==== External links ====

[http://blogs.vmware.com/vsphere/2012/02/introduction-to-the-vsphere-api-part-1.html Introduction to the vSphere API Part 1: Overview]

[http://blogs.vmware.com/vsphere/2012/02/introduction-to-the-vsphere-api-part-2-object-model.html Introduction to the vSphere API Part 2: Object Model]


[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's

===== vCloud =====

[http://communities.vmware.com/community/developer/forums/vcloudapi VMware vCloud API forums]

[http://communities.vmware.com/community/beta/vcloudsdkphp VMware vCloud php SDK beta]

[http://geekafterfive.com/2011/11/01/vcloud-apigui-throwdown/ vCloud API/GUI Throwdown (geekafterfive)]
* Hot Cloning
* Change VM networks
* Change disks

[http://geekafterfive.com/2012/02/24/vcloud-apigui-throwdown-part-2/ vCloud API/GUI Throwdown: Part 2 (geekafterfive)]
* Hot Cloning vApps
* Hot Modify connected VM network
* Hot Modify Disk Size
* Hot Modify Org Name!

[[Category: SDK]]</text>
    <sha1>33ddf64b9ec4bd601535f2f97af76e5ee0158cdd</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI: dvPortgroup ports report</title>
  <ns>0</ns>
  <id>537</id>
  <revision>
    <id>1231</id>
    <timestamp>2013-01-24T12:30:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "=== PowerCLI: dvPortgroup ports report === author: Arne Fokkema ==== Description ==== Helps you to create a report of the dvPortgroups used in vCenter.  The report has columns..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="489" xml:space="preserve">=== PowerCLI: dvPortgroup ports report ===
author: Arne Fokkema
==== Description ====
Helps you to create a report of the dvPortgroups used in vCenter.

The report has columns for: dvPortgroup Name, portbinding configuration, total ports configured, total ports in use and total ports left on the dvPortgroup.

==== Usage ====
Please check the link below.

==== Location ====

http://ict-freak.nl/2012/07/06/powercli-dvportgroup-ports-report/

[[Category: PowerCLI]] [[Category: dvSwitch]]</text>
    <sha1>8332d82af1d2d11ef1bb8a9f2a58f1a3d80b9d4f</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI: Get VM Swap Information</title>
  <ns>0</ns>
  <id>538</id>
  <revision>
    <id>1236</id>
    <timestamp>2013-06-30T23:32:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Get VM Swap information === author: Matt Andes ==== Description ==== Retrieves the swap information for a VM, includeing VM name, name of swap file, the datastore it live..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="668" xml:space="preserve">===  Get VM Swap information ===
author: Matt Andes
==== Description ====
Retrieves the swap information for a VM, includeing VM name, name of swap file, the datastore it lives on and the amount of free space on that datastore.

==== Usage ====

This command can be called a couple of different ways. It can take piped input from the Get-VM cmdlet or you can give it the name of a VM and that will work as well.

 Get-VMSwapInfo -VM "VMName"
  
 Get-VMSwapInfo "VMName"
 
 Get-VM | Get-VMSwapInfo

 $vm = Get-VM 
 Get-VMSwapInfo $vm


==== Location ====

http://www.virtual-matt.net/2013/06/get-vm-swap-information/

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>8501f883988f94a68a51d4a5129ed8bbdfc15917</sha1>
  </revision>
  <revision>
    <id>1237</id>
    <parentid>1236</parentid>
    <timestamp>2013-06-30T23:32:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="669" xml:space="preserve">===  Get VM Swap information ===
author: Matt Andes
==== Description ====
Retrieves the swap information for a VM, includeing VM name, name of swap file, the datastore it lives on and the amount of free space on that datastore.

==== Usage ====

This command can be called a couple of different ways. It can take piped input from the Get-VM cmdlet or you can give it the name of a VM and that will work as well.

 Get-VMSwapInfo -VM "VMName"
  
 Get-VMSwapInfo "VMName"
 
 Get-VM | Get-VMSwapInfo
 
 $vm = Get-VM 
 Get-VMSwapInfo $vm


==== Location ====

http://www.virtual-matt.net/2013/06/get-vm-swap-information/

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>2575e4a45dde2f7cd5f65a1c6700adab001ad746</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter</title>
  <ns>0</ns>
  <id>539</id>
  <revision>
    <id>1239</id>
    <timestamp>2013-07-03T12:44:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Luc's home lab series - part 1 - cloning a VM</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="882" xml:space="preserve">===  Home Lab Tools - Clone a VM without vCenter ===
author: Luc Dekens
==== Description ====
In his home lab Luc runs a simple ESXi server as bases and thus he can not use vCenter functionality to cloning a VM.
In order to still use that feature he wrote a few -as he calls "simple"- scripts that give him the cloning functionality as he needs.

There are a few preconditions, such as:
* The source VM must be shut down
* The source VM cannot have any open snapshots.

Also note that the VM does not get customized, so the clone is exactly the same as the original!
==== Usage ====
An example of how to call the function is:

 Clone-MasterVM -MasterName W2K12Core_Base -CloneName Server1 -DatastoreName datastore2 -Register -PowerOn

==== Location ====

http://www.lucd.info/2013/06/30/hl-tools-part-1-clone-a-vm-without-vcenter/

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>f0bbd7f9b2e1906b48d146b80255050f020e5dd8</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Perl</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>1240</id>
    <parentid>1158</parentid>
    <timestamp>2013-07-23T10:16:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Scripts */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="683" xml:space="preserve">==== Learning more about Perl and the SDK ====
[http://communities.vmware.com/docs/DOC-10837 Getting Started with the vSphere SDK for Perl]

[http://www.perl.org/docs.html Perl.org Online Documentation]

[[Install the VI Perl Toolkit on OS X]]

[[Install vGhetto on OS X]]

==== Scripts ====
[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]

[[Listing all VM's in a cluster]]

[[Rename local storage datastore]]

[[Factory Reset of ESXi]]

[[How to run a PERL Script from a vCenter Orchestrator Workflow]]

[[Category: Perl]]</text>
    <sha1>666aa010752bd3e28c14c709f6d91bb10ccece0a</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>How to run a PERL Script from a vCenter Orchestrator Workflow</title>
  <ns>0</ns>
  <id>540</id>
  <revision>
    <id>1241</id>
    <timestamp>2013-07-23T10:21:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  How to run a Perl script from a vCenter Orchestrator workflow === author: Burke Azbill (VCOteam) ==== Description ==== This truly awesome how-to let you see how you can i..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="596" xml:space="preserve">===  How to run a Perl script from a vCenter Orchestrator workflow ===
author: Burke Azbill (VCOteam)
==== Description ====
This truly awesome how-to let you see how you can integrate your perl scripts with vCenter.
You can pass parameters, get results and see the output logged.

Hereby making them available as a workflow to be used and scheduled from within your vCenter.

==== Usage ====
Follow the steps in the article


==== Location ====

http://www.vcoteam.info/learn-vco/how-to-run-a-perl-script-from-a-vcenter-orchestrator-workflow.html

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>1f5882133d5da050f6a50d795b6526f133b4b61a</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI: Upgrading your VMFS datastores</title>
  <ns>0</ns>
  <id>541</id>
  <revision>
    <id>1243</id>
    <timestamp>2013-07-23T10:43:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Upgrading your VMFS datastores with PowerCLI === author: Robert van den Nieuwendijk ==== Description ==== This script gives you the possibility to run in-place upgrades o..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="724" xml:space="preserve">===  Upgrading your VMFS datastores with PowerCLI ===
author: Robert van den Nieuwendijk
==== Description ====
This script gives you the possibility to run in-place upgrades on your VMFS datastores to upgrade them from VMFS-3 to VMFS-5

==== Usage ====
 PowerCLI C:\&gt; Get-Datastore -Name Datastore1 | Upgrade-VmfsDatastore -WhatIf
 What if: Performing operation "Upgrade-VmfsDatastore" on Target "Datastore1".
 PowerCLI C:\&gt; Get-Datastore -Name Datastore1 | Upgrade-VmfsDatastore

 Name FreeSpaceGB CapacityGB
 ---- ----------- ---------- 
 Datastore1 103,861 499,750
==== Location ====

http://rvdnieuwendijk.com/2013/06/05/upgrading-your-vmfs-datastores-with-powercli/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>2a4c8d772514358b5b9be75b5148b67eed106ddf</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Rbvmomi</title>
  <ns>0</ns>
  <id>542</id>
  <revision>
    <id>1245</id>
    <timestamp>2013-07-23T10:55:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Rbvmomi === author: Rich Lane, Christian Dickmann ==== Description ==== Ruby interface to the VMware vSphere API  ==== Usage ====  installgem install rbvmomi   ==== Locat..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="291" xml:space="preserve">===  Rbvmomi ===
author: Rich Lane, Christian Dickmann
==== Description ====
Ruby interface to the VMware vSphere API

==== Usage ====
 installgem install rbvmomi


==== Location ====

https://rubygems.org/gems/rbvmomi

https://github.com/vmware/rbvmomi

[[Category: Ruby]] [[Category: API]]</text>
    <sha1>a9a56a0b3a62502920180a9e1e648194f9511b61</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Vmsvc/getallvms</title>
  <ns>0</ns>
  <id>147</id>
  <revision>
    <id>1246</id>
    <parentid>690</parentid>
    <timestamp>2013-07-23T11:01:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="546" xml:space="preserve">==== vimsh vmsvc/getallvms ====
Usage: getallvms

Get the list of virtual machines on the host.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /vmsvc/getallvms
 Vmid    Name               File                 Guest OS       Version   Annotation
 64     bartPE    [store] BartPE/BartPE.vmx     winXPProGuest     vmx-04
 96     trustix   [store] Trustix/Trustix.vmx   otherLinuxGuest   vmx-04

==== note ====
This command can be used to replace the old -obsolete- ESX vmware-cmd: 
 vmware-cmd -l

[[Category: Vimsh]]</text>
    <sha1>8a2b9c2e9cd85e05012127f37165e60ec03b9735</sha1>
  </revision>
  <revision>
    <id>1247</id>
    <parentid>1246</parentid>
    <timestamp>2013-07-23T11:01:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="547" xml:space="preserve">==== vimsh vmsvc/getallvms ====
Usage: getallvms

Get the list of virtual machines on the host.

==== example output ====
 # vmware-vim-cmd -H 10.10.10.10 -U root -P password /vmsvc/getallvms
 Vmid    Name               File                 Guest OS       Version   Annotation
 64     bartPE    [store] BartPE/BartPE.vmx     winXPProGuest     vmx-04
 96     trustix   [store] Trustix/Trustix.vmx   otherLinuxGuest   vmx-04

==== note ====
This command can be used to replace the old -obsolete- ESX CLI command: 
 vmware-cmd -l

[[Category: Vimsh]]</text>
    <sha1>cbd9f7aadc6ef330279a7e1f4fe7055399dec60a</sha1>
  </revision>
  <revision>
    <id>1248</id>
    <parentid>1247</parentid>
    <timestamp>2013-07-23T11:05:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="540" xml:space="preserve">==== vimsh vmsvc/getallvms ====
Usage: getallvms

Get the list of virtual machines on the host.

==== example output ====
 # vim-cmd -H 10.10.10.10 -U root -P password /vmsvc/getallvms
 Vmid    Name               File                 Guest OS       Version   Annotation
 64     bartPE    [store] BartPE/BartPE.vmx     winXPProGuest     vmx-04
 96     trustix   [store] Trustix/Trustix.vmx   otherLinuxGuest   vmx-04

==== note ====
This command can be used to replace the old -obsolete- ESX CLI command: 
 vmware-cmd -l

[[Category: Vimsh]]</text>
    <sha1>13f0059c03334f472bcf2357591e9d87d0632682</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Vmsvc/power.getstate</title>
  <ns>0</ns>
  <id>197</id>
  <revision>
    <id>1249</id>
    <parentid>371</parentid>
    <timestamp>2013-07-23T13:05:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Example output */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="795" xml:space="preserve">==== vimsh vmsvc/power.getstate ====
Usage: power.getstate vmid

Retrieves the power state of the specified virtual machine.

You can use [[vmsvc/getallvms]] to retrieve the vmid

====Example output====
For a machine that is powered on:
 [/]$ vmsvc/power.getstate 4400
 Retrieved runtime info
 Powered on

For a non existing machine:
 [/]$ vmsvc/power.getstate 123
 (vim.fault.NotFound) {
    dynamicType = &lt;unset&gt;,
    msg = "Unable to find a VM corresponding to "123""
 }

For a suspended machine:
 [/]$ vmsvc/power.getstate 4414
 Retrieved runtime info 
 Suspended

and powered off:
 [/]$ vmsvc/power.getstate 4400
 Retrieved runtime info
 Powered off

==== note ====
This command can be used to replace the old -obsolete- ESX CLI command: 

 vmware-cmd path.vmx getstate

[[Category: Vimsh]]</text>
    <sha1>e920d475aba27fb949b775580192190a7ef82957</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI: HL Tools – Part 2 – Create a nested hypervisor</title>
  <ns>0</ns>
  <id>543</id>
  <revision>
    <id>1252</id>
    <timestamp>2013-07-23T22:24:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Create a nested hypervisor === author: Luc Dekens ==== Description ==== From Luc's Home Lab series, the script to create a nested hypervisor VM. This will let you create ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1072" xml:space="preserve">===  Create a nested hypervisor ===
author: Luc Dekens
==== Description ====
From Luc's Home Lab series, the script to create a nested hypervisor VM.
This will let you create a ESX or HyperV hypervisor VM for your lab so that you can experiment as much as you'd want without breaking anything important.

==== Usage ====
the following example (from his page) displays how-to create 3 nested ESX VM's and boot them after creation.
 $esx = Get-VMHost -Name MyLab
 $pgName = "Internal"
 $pgObj = Get-VirtualPortGroup -Name $pgName
 $pg = 1..4 | %{$pgObj}
 
 $nestedParams = @{
   Name = $null
   VMHost = $esx
   DiskGB = 8
   NumCpu = 2
   MemoryGB = 8
   Portgroup = $pg
   CD = $true
   ISOPath = "[datastore1] ISO/VMware-VMvisor-Installer-5.1.0-799733.x86_64.iso"
   ESXi = $true
 } 
 
 1..3 | %{
   $nestedParams.Name = "ESX$($_)"
   $newesx = New-NestedHypervisor @nestedParams
   Start-VM -VM $newesx -Confirm:$false
 }

==== Location ====

http://www.lucd.info/2013/07/12/hl-tools-part-2-create-a-nested-hypervisor/

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>1351edbb1edc48b4ff6337da7e54cad528957bb9</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>PowerCLI: Get VMHost Support Bundles</title>
  <ns>0</ns>
  <id>544</id>
  <revision>
    <id>1254</id>
    <timestamp>2013-07-24T17:39:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Get VMHost Support Bundles with PowerCLI === author: Conrad Ramos ==== Description ==== Using powerCLI to download the VM Host support bundles so you can troubleshoot the..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="433" xml:space="preserve">===  Get VMHost Support Bundles with PowerCLI ===
author: Conrad Ramos
==== Description ====
Using powerCLI to download the VM Host support bundles so you can troubleshoot the host in case of problems.
==== Usage ====


 get-vmhost | Get-Log -bundle -DestinationPath "C:\Download\Bundle"

==== Location ====

http://www.vnoob.com/2013/06/get-vmhost-support-bundles-with-powercli/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>9f47ec6815c468a0cfd7f59c6890c441d67009aa</sha1>
  </revision>
</page>
<page arvcontinue="20110201103454|1207">
  <title>Vmsvc/message</title>
  <ns>0</ns>
  <id>196</id>
  <revision>
    <id>1255</id>
    <parentid>369</parentid>
    <timestamp>2013-07-29T17:25:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="964" xml:space="preserve">==== vimsh vmsvc/message ====
Usage: message vmid [messageId] [messageChoice]

Replies to the current pending question on the vm.

Starting a VM in for example the virtual infrastructure client or the web client present a question to you.
This question has to be answered before the VM can continue starting up.
When using vim-cmd you don't get this type of question. Instead you are supposed to use this method.

=== Example ===

 # vim-cmd vmsvc/message 23 
 Virtual machine message _vmx1:
 msg.uuid.altered:This virtual machine might have been moved or copied.
 In order to configure certain management and networking features, 
 VMware ESX needs to know if this virtual machine was moved or  copied. 
 
 If you don't know, answer "I copied it". 
 
    0. Cancel (Cancel)
    1. I moved it (I moved it)
    2. I copied it (I copied it) [default]

=== See also ===
http://www.viktorious.nl/2013/07/26/start-a-vm-from-esxi-cli-pauses-forever/

[[Category: Vimsh]]</text>
    <sha1>621994425b5d3f2b5ce5584605c05e1ef00371fb</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: enable SSH and configure ESXi Firewall</title>
  <ns>0</ns>
  <id>545</id>
  <revision>
    <id>1257</id>
    <timestamp>2013-07-29T18:12:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  PowerCLI: Enable SSH and configure ESXi Firewall === author: Arne Fokkema ==== Description ==== By default nowadays a host is not supposed to have SSH enabled as you are ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="969" xml:space="preserve">===  PowerCLI: Enable SSH and configure ESXi Firewall ===
author: Arne Fokkema
==== Description ====
By default nowadays a host is not supposed to have SSH enabled as you are supposed to manage your host via the exposed APIs.
There are however times when it is really convenient to have SSH access. Instead of just opening SSH and disregarding or ignoring the warning this creates, Arne created a PowerCLI script to enable/disable SSH on need.

The script configures SSH to start automatically, it hides the Shell warning message and will then configure the ESXi firewall to allow the connection from a certain IP address. 

==== Usage ====
Change the $cluster and $ip variables to accomodate your environment.
Then copy the script to your PowerCLI session and run it.
 
 $cluster = "&lt;clusterName&gt;"
 $ip = "192.168.1.1"
==== Location ====

http://ict-freak.nl/2013/05/02/powercli-enable-ssh-and-configure-esxi-firewall/

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>d75255be8f389a722aa931efa50ac85b0d8cf0f4</sha1>
  </revision>
  <revision>
    <id>1258</id>
    <parentid>1257</parentid>
    <timestamp>2013-07-29T18:13:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Oops, not perl, but powerCLI</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="973" xml:space="preserve">===  PowerCLI: Enable SSH and configure ESXi Firewall ===
author: Arne Fokkema
==== Description ====
By default nowadays a host is not supposed to have SSH enabled as you are supposed to manage your host via the exposed APIs.
There are however times when it is really convenient to have SSH access. Instead of just opening SSH and disregarding or ignoring the warning this creates, Arne created a PowerCLI script to enable/disable SSH on need.

The script configures SSH to start automatically, it hides the Shell warning message and will then configure the ESXi firewall to allow the connection from a certain IP address. 

==== Usage ====
Change the $cluster and $ip variables to accomodate your environment.
Then copy the script to your PowerCLI session and run it.
 
 $cluster = "&lt;clusterName&gt;"
 $ip = "192.168.1.1"
==== Location ====

http://ict-freak.nl/2013/05/02/powercli-enable-ssh-and-configure-esxi-firewall/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>2853194b182fe5bf60b409244db481f60fddb684</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI</title>
  <ns>0</ns>
  <id>524</id>
  <revision>
    <id>1259</id>
    <parentid>1256</parentid>
    <timestamp>2013-07-29T18:19:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VM Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4887" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>1d22ec7fad7e4ed46622ebcfdca1a3ba7e09f5d9</sha1>
  </revision>
  <revision>
    <id>1261</id>
    <parentid>1259</parentid>
    <timestamp>2013-07-29T22:04:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Networking */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4947" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>22bc25624244271f5d72b9238a914852f29ed663</sha1>
  </revision>
  <revision>
    <id>1264</id>
    <parentid>1261</parentid>
    <timestamp>2013-08-10T13:59:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Networking */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5027" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====
* [[PowerCLI: upgrade from VMFS3 to VMFS5 with no downtime]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>ad2716347400ab776044a0b36f7217801e66ff3f</sha1>
  </revision>
  <revision>
    <id>1265</id>
    <parentid>1264</parentid>
    <timestamp>2013-08-10T13:59:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4979" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====
* [[PowerCLI: upgrade from VMFS3 to VMFS5 with no downtime]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>38ebce244beebc11f402790da04f51455ef9a8e2</sha1>
  </revision>
  <revision>
    <id>1266</id>
    <parentid>1265</parentid>
    <timestamp>2013-08-10T14:00:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Storage */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5028" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: upgrade from VMFS3 to VMFS5 with no downtime]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>7e4d5b53133974e06b59d272af1800b1ed4cdbc3</sha1>
  </revision>
  <revision>
    <id>1267</id>
    <parentid>1266</parentid>
    <timestamp>2013-08-10T14:00:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Storage */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5028" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>09a54c51fc95a68d298e5593a96d316086b5adbe</sha1>
  </revision>
  <revision>
    <id>1269</id>
    <parentid>1267</parentid>
    <timestamp>2013-08-10T14:06:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Storage */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5083" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>8f5d5b652292c87f5622879684424c86995cfd58</sha1>
  </revision>
  <revision>
    <id>1271</id>
    <parentid>1269</parentid>
    <timestamp>2013-08-10T14:13:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Networking */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5161" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>e103a359c37f75785a3c7ddc4874e18f31a8767e</sha1>
  </revision>
  <revision>
    <id>1275</id>
    <parentid>1271</parentid>
    <timestamp>2013-08-10T15:13:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5238" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>f04ef1f9b7f64357c42e3b5a2da55df7c8b1ba99</sha1>
  </revision>
  <revision>
    <id>1277</id>
    <parentid>1275</parentid>
    <timestamp>2013-08-21T04:01:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Storage */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5353" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>dd1189ae9b2bb493d382c58391320ede093c19c9</sha1>
  </revision>
  <revision>
    <id>1280</id>
    <parentid>1277</parentid>
    <timestamp>2013-08-21T04:42:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Networking */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5454" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>07f9f1e376f0aa176600249ab708b099e0a4436a</sha1>
  </revision>
  <revision>
    <id>1281</id>
    <parentid>1280</parentid>
    <timestamp>2013-08-21T04:42:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Networking */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5455" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>67eaf94f5246097b01f44289a7fb2cc3765648f0</sha1>
  </revision>
  <revision>
    <id>1283</id>
    <parentid>1281</parentid>
    <timestamp>2013-09-08T17:45:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* vCloud */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5517" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>f497147ffba90eb5f1389037d6c58d251b9c0274</sha1>
  </revision>
  <revision>
    <id>1286</id>
    <parentid>1283</parentid>
    <timestamp>2013-09-09T09:54:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5576" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* [[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>daba6d8f850df4fe3310998e6fcfa43b38f520bc</sha1>
  </revision>
  <revision>
    <id>1288</id>
    <parentid>1286</parentid>
    <timestamp>2013-09-20T08:01:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Learning VI-Toolkit Powershell */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5827" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>ab576d5bf05a24537af2e9c21c2f9665a38a498c</sha1>
  </revision>
  <revision>
    <id>1302</id>
    <parentid>1288</parentid>
    <timestamp>2014-02-07T05:47:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VM Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5864" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>54754eb34811b077ca182b96252505d324655a80</sha1>
  </revision>
  <revision>
    <id>1304</id>
    <parentid>1302</parentid>
    <timestamp>2014-03-06T08:59:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* vCloud */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5911" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]]</text>
    <sha1>6eeb85ffe0af9cb0fcc9e2b093c2cf0f4492d359</sha1>
  </revision>
  <revision>
    <id>1305</id>
    <parentid>1304</parentid>
    <timestamp>2014-03-06T09:00:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5933" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>10a363faca90f36ec80e3d962132848d0cf7597e</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Change Virtual Machines Guest OS Names</title>
  <ns>0</ns>
  <id>546</id>
  <revision>
    <id>1260</id>
    <timestamp>2013-07-29T18:23:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  PowerCLI: Change Virtual Machines Guest OS Names === author: Rawlinson ==== Description ==== The script displayed here queries the VM name at the host level and will use ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="500" xml:space="preserve">===  PowerCLI: Change Virtual Machines Guest OS Names ===
author: Rawlinson
==== Description ====
The script displayed here queries the VM name at the host level and will use that to set the name of the operating system within the guest OS. The example code here is used for windows guests.

==== Usage ====

Save as a script and run it.

==== Location ====

http://www.punchingclouds.com/2013/06/06/powercli-change-virtual-machines-guest-os-names/

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>19b54fa11e11b63b78b8901e428138e15444a7d9</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Show-vCloudStatsHtml.ps1</title>
  <ns>0</ns>
  <id>547</id>
  <revision>
    <id>1262</id>
    <timestamp>2013-07-29T22:12:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Show-vCloudStatsHtml.ps1 === author: Timo Sugliani ==== Description ==== Timo created a script that generates a single HTML File report of the statistics from your vCloud..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="675" xml:space="preserve">===  Show-vCloudStatsHtml.ps1 ===
author: Timo Sugliani
==== Description ====
Timo created a script that generates a single HTML File report of the statistics from your vCloud environment.

==== Usage ====
Launch the script from the PowerCLI prompt and it will ask for the vCloud Director instance details and credentials.

 PowerCLI DRIVE:\PathToScript&gt; Show-vCloudStatsHtml.ps1

The HTML report will be created at the desktop of the user ($HOME\Desktop)

==== Location ====

http://blog.tsugliani.fr/vcloud/powershell-powercli-script-show-vcloudstatshtml-ps1/

http://tsugliani.github.io/vCloudScripts/index.html#vCloudStatsHtml

[[Category: PowerCLI]] [[Category: vCloud]]</text>
    <sha1>75e1c1de861533a99134178161e21f6f9d5ac83c</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI Oneliners: Storage</title>
  <ns>0</ns>
  <id>495</id>
  <revision>
    <id>1263</id>
    <parentid>1053</parentid>
    <timestamp>2013-08-10T13:50:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Storage */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="531" xml:space="preserve">==== Storage ====
* [http://www.virtu-al.net/2009/07/14/powercli-local-stored-vms-one-liner/ List all VMDK files for VM's stored on local storage]

* [http://www.peetersonline.nl/index.php/vmware/powershell-oneliner-6/ Check the Usage of your datastore]

* [http://thephuck.com/virtualization/powercli-one-liner-to-move-all-vms-on-one-datastore-to-another-and-convert-to-thick-or-thin/ PowerCLI one liner to move all VMs on one datastore to another and convert to thick or thin]

[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>549a43edb00094766912ef47e399cad70b58cbf2</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime</title>
  <ns>0</ns>
  <id>548</id>
  <revision>
    <id>1268</id>
    <timestamp>2013-08-10T14:05:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  ConvertTo-Vmfs5 === author: Timothy J. Patterson ==== Description ==== This script allows you to selectively upgrade a VMFS3 partition to VMFS5 with no downtime.  ==== Us..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="387" xml:space="preserve">===  ConvertTo-Vmfs5 ===
author: Timothy J. Patterson
==== Description ====
This script allows you to selectively upgrade a VMFS3 partition to VMFS5 with no downtime.

==== Usage ====
 PS&gt; Get-Datastore -Name "DS1" | ConvertTo-Vmfs5
==== Location ====

http://timsvirtualworld.com/2013/05/checking-vmfs-version-and-block-sizes-with-powercli/

[[Category: PowerCLI]] [[Category: Storage]]</text>
    <sha1>6294d9c052cac81803362e0dacd05ee0cc2842d7</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Checking VMFS Version and Block Sizes</title>
  <ns>0</ns>
  <id>549</id>
  <revision>
    <id>1270</id>
    <timestamp>2013-08-10T14:09:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  ConvertTo-Vmfs5 === author: Timothy J. Patterson / Luc Dekens ==== Description ==== This script allows you to retrieve the partition info on your storage and get info lik..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="433" xml:space="preserve">===  ConvertTo-Vmfs5 ===
author: Timothy J. Patterson / Luc Dekens
==== Description ====
This script allows you to retrieve the partition info on your storage and get info like block sizes and VMFS version.

==== Usage ====
 PS&gt; Get-Datastore -Name "DS1" | Get-VmfsPartitionInfo
==== Location ====

http://timsvirtualworld.com/2013/05/checking-vmfs-version-and-block-sizes-with-powercli/

[[Category: PowerCLI]] [[Category: Storage]]</text>
    <sha1>622032ee7298bdfaf07fe61624989f536ae5ad1c</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups</title>
  <ns>0</ns>
  <id>550</id>
  <revision>
    <id>1272</id>
    <timestamp>2013-08-10T14:19:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Disabling Netflow with PowerCLI === author: Alan Renouf ==== Description ==== Alan here wrote a script to disable Netflow on a VDPortgroup or a number of VDPortgroups  Th..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="602" xml:space="preserve">===  Disabling Netflow with PowerCLI ===
author: Alan Renouf
==== Description ====
Alan here wrote a script to disable Netflow on a VDPortgroup or a number of VDPortgroups

This may help with a known issue on ESXi 5.1 when Netflow is enabled: http://kb.vmware.com/kb/2042370

He then shows how-to list all VDPortGroups and if Netflow is enabled for those port groups.
==== Usage ====
 # Disable Netfow for a VDPortgroup
 Get-VDPortgroup DPortGroup | Disable-PGNetflow
==== Location ====

http://www.virtu-al.net/2013/07/23/disabling-netflow-with-powercli/

[[Category: PowerCLI]] [[Category: dvSwitch]]</text>
    <sha1>a179ec16c78d1149f92495093276834574727a61</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Perl</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>1273</id>
    <parentid>1240</parentid>
    <timestamp>2013-08-10T14:45:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Scripts */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="729" xml:space="preserve">==== Learning more about Perl and the SDK ====
[http://communities.vmware.com/docs/DOC-10837 Getting Started with the vSphere SDK for Perl]

[http://www.perl.org/docs.html Perl.org Online Documentation]

[[Install the VI Perl Toolkit on OS X]]

[[Install vGhetto on OS X]]

==== Scripts ====
[[Esx scripts]]

[[Adding/updating a custom field to VM]]

[[Add/modify advanced parameter configuration for a VM]]

[[Get status of VMware Tools on all your VM's]]

[[Get number of vCPU's used in cluster]]

[[Listing all VM's in a cluster]]

[[Rename local storage datastore]]

[[Factory Reset of ESXi]]

[[How to run a PERL Script from a vCenter Orchestrator Workflow]]

[[Perl: VMware vSphere Health Check Report]]

[[Category: Perl]]</text>
    <sha1>0ce1aac5898b53a7a290689821fc51721b0dbc6e</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Perl: VMware vSphere Health Check Report</title>
  <ns>0</ns>
  <id>551</id>
  <revision>
    <id>1274</id>
    <timestamp>2013-08-10T14:49:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  VMware vSphere Health Check Report v5.1.0 === author: William Lam ==== Description ==== This script generates a health check report similar to that of [[vmwareHealthCheck..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1497" xml:space="preserve">===  VMware vSphere Health Check Report v5.1.0 ===
author: William Lam
==== Description ====
This script generates a health check report similar to that of [[vmwareHealthCheckScript]] but for the new vSphere release of VMware ESX(i) 4.x/5.x and VMware vCenter 4.x/5.x and it's managed entities. User's can now fully customize the report based on the categories that are of importance to their operating environment, including selecting specific set of ESX(i) hosts and/or Virtual Machines.

==== Usage ====
1) This will collect information about all cluster(s)/host(s) providing vCenter Server:

 ./vmwarevSphereHealthCheck.pl --server VC_SERVER --username VC_USERNAME --password VC_PASSWORD --type vcenter

2) This will collect information about a specific datacenter provided with vCenter Server:

 ./vmwarevSphereHealthCheck.pl --server VC_SERVER --username VC_USERNAME --password VC_PASSWORD --type datacenter --datacenter DATACENTER_NAME

3) This will collect information about a specific cluster provided with vCenter Server:

 ./vmwarevSphereHealthCheck.pl --server VC_SERVER --username VC_USERNAME --password VC_PASSWORD --type cluster --cluster CLUSTER_NAME

4) This will collect information about a specific host provided with ESX/ESXi Server:

 ./vmwarevSphereHealthCheck.pl --server ESX_ESXi_SERVER --username ESX_ESXi_USERNAME --password ESX_ESXi_PASSWORD --type host
 
==== Location ====

https://communities.vmware.com/docs/DOC-9842

[[Category: Perl]] [[Category: Host Management]]</text>
    <sha1>a000281bb788288105634967556ae3a4b07d174a</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Using plink to modify ESXi host configuration files via SSH</title>
  <ns>0</ns>
  <id>552</id>
  <revision>
    <id>1276</id>
    <timestamp>2013-08-10T15:21:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Using plink to modify ESXi host configuration files via SSH from a PowerCLI script === author: Sean Duffy ==== Description ==== Sean came up with the following method to ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1270" xml:space="preserve">===  Using plink to modify ESXi host configuration files via SSH from a PowerCLI script ===
author: Sean Duffy
==== Description ====
Sean came up with the following method to be able to use SSH from within his PowerCLI script:

* Configure host as normal using PowerCLI
* Use PowerCLI to start SSH service on host
* execute plink script to connect to host, run command via SSH, then disconnect
* Use PowerCLI to stop SSH service on host
* Continue with rest of PowerCLI script

==== Usage ====
 # At start of our script we ask for the host's IP or name (this could be automated if you like)
 $hostIP = Read-Host "Enter ESX host IP/dns name: "
 $vmhost = Get-VMHost $hostIP
 
 # Start the SSH service
 $sshService = Get-VmHostService -VMHost $vmhost | Where { $_.Key -eq “TSM-SSH”} 
 Start-VMHostService -HostService $sshService -Confirm:$false
 
 # Use SSH / plink to configure host with some additional script
 cmd /c "plink.exe -ssh -pw HOSTROOTPASSWORD -noagent -m commands.txt root@$hostIP"
 
 # Stop SSH service
 Stop-VMHostService -HostService $sshService -Confirm:$false
==== Location ====

http://www.shogan.co.uk/vmware/using-plink-to-modify-esxi-host-configuration-files-via-ssh-from-a-powercli-script/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>8c1292d3adb595655e5fa2fa1d413ed681a66724</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster</title>
  <ns>0</ns>
  <id>553</id>
  <revision>
    <id>1278</id>
    <timestamp>2013-08-21T04:08:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Set default path selection policies === author: Yuri de Jager ==== Description ====  Yuri uses powerCLI to query and change the current Path Selection Policy (PSP) on his..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="740" xml:space="preserve">===  Set default path selection policies ===
author: Yuri de Jager
==== Description ====

Yuri uses powerCLI to query and change the current Path Selection Policy (PSP) on his new cluster, after that he updates his default PSP settings so that his preference will be applied in the future as well.

==== Usage ====

 Get-Cluster [ClusterName] | Get-VMHost | Get-ScsiLun -LunType disk | Where {$_.MultipathPolicy -ne “RoundRobin”} | Set-ScsiLun -MultipathPolicy “RoundRobin”

See his post for the full details.
==== Location ====

http://yuridejager.wordpress.com/2013/02/07/set-the-path-selection-policy-for-every-device-path-of-every-host-in-your-vsphere-5-05-1-cluster-using-powercli/

[[Category: PowerCLI]] [[Category: Storage]]</text>
    <sha1>5e95dbfe31f2a329dc4744dc3eb01f1c25561115</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI Oneliners: Host Configuration</title>
  <ns>0</ns>
  <id>493</id>
  <revision>
    <id>1279</id>
    <parentid>1154</parentid>
    <timestamp>2013-08-21T04:13:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Host Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1702" xml:space="preserve">==== Host Configuration ====
* [http://www.peetersonline.nl/index.php/vmware/oneliner-service-console-ip-with-powercli/ Oneliner: Service Console IP with PowerCLI]

* [http://www.virtu-al.net/2009/09/21/powercli-one-liners-checking-host-network-information/ List all ESX Hosts and their Service console information]

* [http://www.virtu-al.net/2009/09/21/powercli-one-liners-checking-host-network-information/ List all ESX Hosts and their VMotion Enabled Networks]

* [http://www.peetersonline.nl/index.php/vmware/checking-vmware-ntp-configuration-with-powershell/ Checking VMware NTP configuration with Powershell]

* [http://www.virtu-al.net/2009/08/14/powercli-do-you-have-the-time/ Check that Hosts are using the same NTP Server and that the service is started]

* [http://www.peetersonline.nl/index.php/powershell/oneliner-get-logged-on-users-with-powershell/ Oneliner: Get Logged on Users with Powershell]

* [http://www.virtu-al.net/2009/07/08/powercli-host-hardware-one-liner/ Display Host Hardware information]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Cluster name, ESX host and the total running VM’s on the host]

* [http://ict-freak.nl/2009/07/13/powercli-get-running-vms-per-vmhost-and-more/ Hostname with the least running VM’s on it]

* [http://www.virtu-al.net/2009/08/16/powercli-processor-types/ Check Host processor types]

* [http://www.hypervisor.fr/?p=1687 Move your templates]

* [http://www.vmwarescripting.com/index.php/topic,1302.0.html Add/Change DNS suffix's on your ESX hosts]

* [http://www.virtu-al.net/2013/08/19/simple-host-time-information/ Simple Host Time Information]


[[Category: PowerCLI]][[Category: Host Management]]</text>
    <sha1>471e5eee372095b4565380dafb1f824bea17315a</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration</title>
  <ns>0</ns>
  <id>554</id>
  <revision>
    <id>1282</id>
    <timestamp>2013-08-21T04:48:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Update BPDU setting === author: Magnus Andersson ==== Description ==== Magnus has written two scripts here to assist with using the BPDU configuraton of your ESX host.  T..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="630" xml:space="preserve">===  Update BPDU setting ===
author: Magnus Andersson
==== Description ====
Magnus has written two scripts here to assist with using the BPDU configuraton of your ESX host.

The first script enumerates the current settings of all your hosts and sends you an email with the test results.

The second script updates the current BPDU configuration settings of all your hosts and notifies you with the result of that via email.

==== Usage ====

Configuration options are in the script.

==== Location ====

http://vcdx56.com/2013/05/06/esxi-host-advanced-configuration-using-powercli/

[[Category: PowerCLI]] [[Category: Networking]]</text>
    <sha1>6d4693c2cf78259ae94ecb523c4f9e67d7492e4d</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Install Software in Isolated Virtual Machines</title>
  <ns>0</ns>
  <id>555</id>
  <revision>
    <id>1284</id>
    <timestamp>2013-09-08T17:52:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Install Software in virtual machines leveraging the VIX API === author:  Aidan Dalgleish ==== Description ==== Aidan here is doing something really cool by installing sof..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1052" xml:space="preserve">===  Install Software in virtual machines leveraging the VIX API ===
author:  Aidan Dalgleish
==== Description ====
Aidan here is doing something really cool by installing software directly into virtual machines by using the VIX API.
This means that you actually do not even need to have a network connected to the virtual machine as the software is transferred via VIX and also installed via that same way.

==== Usage ====

 InstallWinPkgInvCloudVM -CIServer $CIServer -CIUser $CIUser -CIPassword $CIPassword CIVApp "MyTestVM" -Org "COE" -SrcPath "C:\Users\Adalgleish\Downloads\npp.6.3.2.installer.exe" -DstPath "C:\Users\Administrator\Downloads\" -Command "C:\Users\Administrator\Downloads\npp.6.3.2.Installer.exe /S" -VIUser $VIUser -VIPassword $VIPassword -GuestUser $GuestUser -GuestPassword $GuestPassword -NonSupportedGuestOveride

Watch the video on his site to see it in action.

==== Location ====

http://vcloudscape.com/2013/05/01/install-software-in-isolated-virtual-machines/

[[Category: PowerCLI]] [[Category: vCloud]][[Category: VIX]]</text>
    <sha1>904f8c345b92ef4f7d8121c2f0b644d204f81071</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>1285</id>
    <parentid>1175</parentid>
    <timestamp>2013-09-08T17:57:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="999" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

Supported on VMware Workstation 6.0.x and up, VMware Server 1.x and up, VMware ESX3.5U2+

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX 1.1 API reference Guide]

[http://www.vmware.com/support/developer/vix-api/vix16_reference/ VMware VIX 1.6 API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

[http://www.virtuallyghetto.com/2013/07/whitepaper-migrating-from-vix-api-to.html Whitepaper: Migrating From VIX API to the vSphere Guest Operations API]

==== Presentations ====

[[VIX API Tech Talk Partner Exchange]]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Vix Java Toolkit]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>a7823753e8abf0173b15f269e7e0becd8876ea62</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Update host from ESXi 5.1 to 5.1 update 1</title>
  <ns>0</ns>
  <id>556</id>
  <revision>
    <id>1287</id>
    <timestamp>2013-09-09T10:11:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Rolling updates === author: Alan Renouf ==== Description ==== Here Alan shows how you can update your hosts using PowerCLI  ==== Usage ==== List hosts and their versions:..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1108" xml:space="preserve">===  Rolling updates ===
author: Alan Renouf
==== Description ====
Here Alan shows how you can update your hosts using PowerCLI

==== Usage ====
List hosts and their versions:
 Get-VMhost | Select name, ConnectionState, Version, Build

Put the host into maintenance mode so that we can install the patch:
 $vmhost = Get-VMhost pod18-esx01a*
 $vmhost | Set-VMhost -State Maintenance

Upload the patch to a datastore
 $ds = $vmhost | Get-Datastore datastore1*
 Copy-DatastoreItem C:\Updates\Update-from-esxi5.1-5.1-update1.zip $ds.datastorebrowserpath -Recurse

Install the patch on the host
 $esxcli = Get-Esxcli -VMHost $vmhost
 $esxcli.software.vib.install("/vmfs/volumes/datastore1/Update-from-esxi5.1-5.1-update1.zip",$false,$true,$true,$false,$false)
and reboot
 Restart-VMhost -VMHost $vmhost -Confirm:$false

Remove the uploaded patch from the datastore
 remove-item ($ds.datastorebrowserpath + "\Update-from-esxi5.1-5.1-update1.zip")

==== Location ====

http://www.virtu-al.net/2013/07/24/updating-from-esxi-5-1-to-esxi-5-1-update1-with-powercli/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>e6817b770c259351f96f8ed907833aa652580039</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>SDK</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>1289</id>
    <parentid>1233</parentid>
    <timestamp>2013-09-20T09:03:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* External links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1309" xml:space="preserve">[[VI Toolkit]]

[[Vassert Linux SDK]]

[[VProbe Toolkit]]

[[VIX]]

[[vimsh]]

[[VMware Virtual Disk Development Kit]]

[[VMware Icons]]

[[vCenter Orchestrator]]

==== External links ====

[http://blogs.vmware.com/vsphere/2012/02/introduction-to-the-vsphere-api-part-1.html Introduction to the vSphere API Part 1: Overview]

[http://blogs.vmware.com/vsphere/2012/02/introduction-to-the-vsphere-api-part-2-object-model.html Introduction to the vSphere API Part 2: Object Model]


[http://www.vmware.com/support/pubs/sdk_pubs.html VMware SDK landing page] a page that lists all of VMware SDK's


[http://professionalvmware.com/2013/08/getting-started-with-vmware-automation Getting Started with VMware Automation]

===== vCloud =====

[http://communities.vmware.com/community/developer/forums/vcloudapi VMware vCloud API forums]

[http://communities.vmware.com/community/beta/vcloudsdkphp VMware vCloud php SDK beta]

[http://geekafterfive.com/2011/11/01/vcloud-apigui-throwdown/ vCloud API/GUI Throwdown (geekafterfive)]
* Hot Cloning
* Change VM networks
* Change disks

[http://geekafterfive.com/2012/02/24/vcloud-apigui-throwdown-part-2/ vCloud API/GUI Throwdown: Part 2 (geekafterfive)]
* Hot Cloning vApps
* Hot Modify connected VM network
* Hot Modify Disk Size
* Hot Modify Org Name!

[[Category: SDK]]</text>
    <sha1>64cb8759cb6196640597c265fbc1c85c772cdee3</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Python</title>
  <ns>0</ns>
  <id>535</id>
  <revision>
    <id>1290</id>
    <parentid>1227</parentid>
    <timestamp>2014-01-30T07:38:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48" xml:space="preserve">
[[pysphere]]

[[pyvmomi]]

[[Category: Python]]</text>
    <sha1>86d9275a99e12422f0127b49a7ca8fa7ca13637a</sha1>
  </revision>
  <revision>
    <id>1292</id>
    <parentid>1290</parentid>
    <timestamp>2014-01-30T07:52:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="67" xml:space="preserve">
[[pysphere]]

[[pyvmomi]]

[[getvmstree.py]]

[[Category: Python]]</text>
    <sha1>3c720e288523401ec64d11dd25ccfc256e25bdce</sha1>
  </revision>
  <revision>
    <id>1295</id>
    <parentid>1292</parentid>
    <timestamp>2014-01-30T08:05:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="81" xml:space="preserve">
[[pysphere]]

[[pyvmomi]]

[[getvmstree.py]]

[[pyxenter]]

[[Category: Python]]</text>
    <sha1>d5ea93fdecd6c4668951865c092fc9d66b603187</sha1>
  </revision>
  <revision>
    <id>1300</id>
    <parentid>1295</parentid>
    <timestamp>2014-02-07T05:34:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="98" xml:space="preserve">
[[pysphere]]

[[pyvmomi]]

[[getvmstree.py]]

[[pyxenter]]

[[tasklist.py]]

[[Category: Python]]</text>
    <sha1>7daef35e6eaded47a5b888d284e38e0bb40babbb</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Pyvmomi</title>
  <ns>0</ns>
  <id>557</id>
  <revision>
    <id>1291</id>
    <timestamp>2014-01-30T07:49:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  pyVmomi === author: VMware ==== Description ==== The official python vSphere API binding for running python scripts that target ESX, ESXi and vCenter  ==== Usage ====  To..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="583" xml:space="preserve">===  pyVmomi ===
author: VMware
==== Description ====
The official python vSphere API binding for running python scripts that target ESX, ESXi and vCenter

==== Usage ====

To get started, check out the examples in the sample folder.

 getallvms.py 	Python program for listing the vms on an ESX / vCenter host
 poweronvm.py 	Python program for powering on vms on a host on which hostd is running


==== Location ====

https://github.com/vmware/pyvmomi

see also:

http://www.virtuallyghetto.com/2013/12/early-xmas-gift-from-vmware-pyvmomi.html

[[Category: Python]] [[Category: SDK]]</text>
    <sha1>4c3418a38b24435901ba2edc159880b5907dde0f</sha1>
  </revision>
  <revision>
    <id>1294</id>
    <parentid>1291</parentid>
    <timestamp>2014-01-30T08:01:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Location */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="621" xml:space="preserve">===  pyVmomi ===
author: VMware
==== Description ====
The official python vSphere API binding for running python scripts that target ESX, ESXi and vCenter

==== Usage ====

To get started, check out the examples in the sample folder.

 getallvms.py 	Python program for listing the vms on an ESX / vCenter host
 poweronvm.py 	Python program for powering on vms on a host on which hostd is running


==== Location ====

https://github.com/vmware/pyvmomi

https://pypi.python.org/pypi/pyvmomi

see also:

http://www.virtuallyghetto.com/2013/12/early-xmas-gift-from-vmware-pyvmomi.html

[[Category: Python]] [[Category: SDK]]</text>
    <sha1>7b5d29d9379861d636c433525c2df455864ffadf</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Getvmstree.py</title>
  <ns>0</ns>
  <id>558</id>
  <revision>
    <id>1293</id>
    <timestamp>2014-01-30T07:58:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  getvmstree.py === author: Timo Sugliani  ==== Description ==== List all of the VMs in a tree similar to how it looks like in the Web client inventory.  ==== Usage ====   ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="481" xml:space="preserve">===  getvmstree.py ===
author: Timo Sugliani 
==== Description ====
List all of the VMs in a tree similar to how it looks like in the Web client inventory.

==== Usage ====

 python getvmstree.py -s vcsa.myserver.local -u user -p password

==== Location ====

http://blog.tsugliani.fr/scripts-and-tips/pyvmomi-finally-vsphere-python-sdk/

and source is here: 

https://github.com/tsugliani/pyvmomi/blob/master/sample/getvmstree.py


[[Category: Python]] [[Category: VM Management]]</text>
    <sha1>e12fe558255b71c3aeff240ddbfc26e358928c54</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Pyxenter</title>
  <ns>0</ns>
  <id>559</id>
  <revision>
    <id>1296</id>
    <timestamp>2014-01-30T08:14:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  pyxenter === author: Kazuki Hasegawa ==== Description ==== Script to manage multiple hypervisors.  With this script you can manage ESXi and Xen Server.  ==== Usage ====  ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="972" xml:space="preserve">===  pyxenter ===
author: Kazuki Hasegawa
==== Description ====
Script to manage multiple hypervisors. 
With this script you can manage ESXi and Xen Server.

==== Usage ====

The examples below are only for ESXi, there are similar examples for Xen. 

Check the link below for details.

List VMs.

 $ esxi list -H servername -u root -p password

VM powered on.

 $ esxi on -H servername -u root -p password [VM name1] [VM name2] ...

Get IPv4 address of VM (it is required to have VMware Tools installed for this to work)

 $ esxi ip -H servername -u root -p password -n [VM name]

Import OVF or OVA file with File path.

 $ esxi import -H servername -u root -p password --file [OVF or OVA File path] [New VM name1] [new VM name2] ...

Import OVA file with URL.

 $ esxi import -H servername -u root -p password --url [OVA URL] [New VM name1] [New VM name2] ...

==== Location ====

https://pypi.python.org/pypi/pyxenter


[[Category: Python]] [[Category: Host Management]]</text>
    <sha1>be8b5936bad0cfcd0b5e0f0c5f91d41382aecc8f</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Rbvmomi</title>
  <ns>0</ns>
  <id>542</id>
  <revision>
    <id>1297</id>
    <parentid>1245</parentid>
    <timestamp>2014-01-30T14:24:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Location */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="292" xml:space="preserve">===  Rbvmomi ===
author: Rich Lane, Christian Dickmann
==== Description ====
Ruby interface to the VMware vSphere API

==== Usage ====
 installgem install rbvmomi


==== Location ====

https://rubygems.org/gems/rbvmomi

https://github.com/vmware/rbvmomi


[[Category: Ruby]] [[Category: SDK]]</text>
    <sha1>09d45ae1b86a7707ce125924a05f4cea762361dc</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Ruby</title>
  <ns>0</ns>
  <id>530</id>
  <revision>
    <id>1298</id>
    <parentid>1244</parentid>
    <timestamp>2014-01-30T14:26:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="67" xml:space="preserve">
[[vco-rest]]


[[vixen]]

[[rbvmomi]]

[[rvc]]

[[Category: Ruby]]</text>
    <sha1>f131f8499d218a32b8171ebbedbb2402b1ba86ab</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Rvc</title>
  <ns>0</ns>
  <id>560</id>
  <revision>
    <id>1299</id>
    <timestamp>2014-01-30T14:37:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Ruby vSphere Console === author: Rich Lane ==== Description ==== A command line interface for vSphere, built via [[RbVmomi]] ==== Usage ====  % rvc 192.168.1.105  usernam..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1201" xml:space="preserve">===  Ruby vSphere Console ===
author: Rich Lane
==== Description ====
A command line interface for vSphere, built via [[RbVmomi]]
==== Usage ====
 % rvc 192.168.1.105
 username: Administrator
 password:
 0 dc (datacenter)
 192.168.1.105:/&gt; cd dc/host/192.168.1.100/
 192.168.1.105:/dc/host/192.168.1.100/&gt; ls
 0 host [192.168.1.100] (host): cpu 2*2*2.81 GHz, memory 2.00 GB
 1 resourcePool [Resources]: cpu 4.35/4.35/normal, mem 0.48/0.48/normal
 192.168.1.105:/dc/host/192.168.1.100/&gt; ls host/vms/
 0 foo: poweredOn
 192.168.1.105:/dc/host/192.168.1.100/&gt; i host/vms/foo
 name: foo
 host: dc/host/192.168.1.100/192.168.1.100
 tools: guestToolsNotRunning 
 VC UUID: 5259d5d2-b767-43c9-db6d-fbf5cc4b6f02
 power: poweredOn
 cpus: 1 
 memory: 128 MB
 nics:
  Network adapter 1: "VM Network" connected 00:0c:29:c6:5d:2a 
 192.168.1.105:/dc/host/192.168.1.100/&gt; off host/vms/foo
 PowerOffVM foo: success
 192.168.1.105:/dc/host/192.168.1.100/&gt; quit

==== Location ====

https://github.com/vmware/rvc

See also:
[http://www.virtuallyghetto.com/2011/04/how-to-install-ruby-vsphere-console-on.html (virtuallyghetto) How to install Ruby vSphere Console on vMA]

[[Category: Ruby]] [[Category: Host Management]]</text>
    <sha1>23fd66d38f0e8bcacfd3b59e2aa0968a4b1805cf</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>Tasklist.py</title>
  <ns>0</ns>
  <id>561</id>
  <revision>
    <id>1301</id>
    <timestamp>2014-02-07T05:41:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  tasklist.py === author: Timo Sugliani  ==== Description ==== Timo made a small script that utilized the [[pyvmomi]] and displays a list of the VMware vCenter recently run..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="523" xml:space="preserve">===  tasklist.py ===
author: Timo Sugliani 
==== Description ====
Timo made a small script that utilized the [[pyvmomi]] and displays a list of the VMware vCenter recently run tasks.

==== Usage ====
Run the script as follows:

 python tasklist.py -s vcenter.fqdn -u username -p password

==== Location ====

http://blog.tsugliani.fr/vsphere/pyvmomi-small-script-to-display-vmware-vcenter-recent-tasks/

https://github.com/tsugliani/pyvmomi/blob/master/sample/tasklist.py

[[Category: Python]] [[Category: Host Management]]</text>
    <sha1>7a097c384286f32157c441b78fd833b3d101f1d6</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Create multiple VMs</title>
  <ns>0</ns>
  <id>562</id>
  <revision>
    <id>1303</id>
    <timestamp>2014-02-07T05:58:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Create multiple VMs === author: Magnus Andersson RTS ==== Description ==== The script can be used to dynamically create a predetermined number of VMs that will be randoml..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="599" xml:space="preserve">===  Create multiple VMs ===
author: Magnus Andersson RTS
==== Description ====
The script can be used to dynamically create a predetermined number of VMs that will be randomly placed on the ESXi host within your cluster.

After creating the VMs they will be powered on automatically.

From the looks of it, the main purpose is stress testing.
==== Usage ====
Change the entries marked in red in the script on his page, see details at his site in the link below.
==== Location ====

http://vcdx56.com/2014/01/30/create-multiple-vms-using-powercli/

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>de5742e6cd7241424174002441765ee25b1f7954</sha1>
  </revision>
</page>
<page arvcontinue="20130729181251|1257">
  <title>PowerCLI: Scriptkit</title>
  <ns>0</ns>
  <id>563</id>
  <revision>
    <id>1306</id>
    <timestamp>2014-03-06T09:19:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  ScriptKit === author: Rynardt Spies ==== Description ==== Rynardt has started working with Powershell and PowerCLI and as a seasoned C++ developer he's already being pret..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3300" xml:space="preserve">===  ScriptKit ===
author: Rynardt Spies
==== Description ====
Rynardt has started working with Powershell and PowerCLI and as a seasoned C++ developer he's already being pretty productive with this. He has been kind enough to start sharing his work in a library that he calls "ScriptKit".
You are welcome to send him scripts to add to the library so that it becomes an easy bases to start looking for scripts for more people.

Currently he has divided up his library in the following two categories, at the time of writing it already contains the following scripts.
===== Configuring =====

  create_vmotion_vmk.ps1 	
Creates up to two vMotion interfaces and configures them with details specified in a CSV file. For a single interface, comment out the entire vmk2 section.
  host_auth_addto_ad_domain.ps1 	
Add hosts in cluster to a specified AD Domain.
  set_vm_max_console_sessions.ps1 	
This script is used to set the maximum remote console sessions allowed on all virtual machines found in the servers.txt file. This is required by many financial industry to prevent more than one concurrent remote console session to a virtual machine in order to an administrator of a VM being shadowed remotely.
  set_vmhost_shell_timeout.ps1 	
Set the ShellTimeOut Setting for all hosts in the specified cluster(s) and restarts the ESXiShell Service. Changes require the SSHShell TSM service to be restarted
  set_vmk_mtu.ps1 	
Updates the MTU size for specified VMKERNEL virtual nics (vmk0, vmk1, vmk2, etc.)
====== Horizon View ======
       set_viewSecurity_extIP.ps1
Updates the External IP address refernece in VMware Horizon View to match the current public IP address of the security server.

Run this script on the View Connection Server
===== Reporting =====
  report_HBAConfig.ps1 	
Report on the HBA Link Speed, HBA Queue Depth, HBA Topology of each ESXi host.
  report_MgmtvMotionIPs.ps1 	
Report on the Management and vMotion IP Addresses (vmk)
  report_ShellTimeOut.ps1 	
Report on the ShellTimeOut Setting for all hosts in specified clusters/DC objects
  report_datastore_space.ps1 	
Script to return all datastores seen in vCenter as well as their capacity, used space and free space.
  report_host_wwn.ps1 	
Report WWN Numbers for hosts specified in $clusters
  report_netConf_CDP.ps1 	
Report the current port group configuration as well as the discovered CDP information.

Handy for comparing actual portgroup config with physical upstream switch config
  report_ntp_syslog.ps1 	
Report the configured NTP Servers as well as the Configured Syslog server
  report_vm_attached_media.ps1 	
Return all CD and Floppy Devices for each VM, including connection state
  report_vm_list.ps1
Reports the Name, vCenter, Datacenter, Cluster, Host and Folder for every virtual machine visible within the PowerCLI session. Also works when connected to multiple VI servers.

Output is saved to a CSV file as specified in $ReportFile 

Helpful in large environments with many vCenter servers.
==== Usage ====

==== Location ====
Rynardt's blog article introducing the scriptkit and asking for help.
http://www.virtualvcp.com/news/197-contribute-to-my-powercli-script-repository-and-help-the-community

Repository:
https://github.com/rynardtspies/ScriptKit


[[Category: PowerCLI]] [[Category: Powershell]]</text>
    <sha1>cb483e4d662e685b8953e4c6f9daa9e240a13f41</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: Scriptkit</title>
  <ns>0</ns>
  <id>563</id>
  <revision>
    <id>1307</id>
    <parentid>1306</parentid>
    <timestamp>2014-03-06T09:23:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3623" xml:space="preserve">===  ScriptKit ===
author: Rynardt Spies
==== Description ====
Rynardt has started working with Powershell and PowerCLI and as a seasoned C++ developer he's already being pretty productive with this. 

He has been kind enough to start sharing his work in a library that he calls "ScriptKit".

You are welcome to send him scripts to add to the library so that it becomes an easy bases to start looking for scripts for more people.

Currently he has divided up his library in the following two categories, at the time of writing it already contains the following scripts.
===== Configuring =====

  create_vmotion_vmk.ps1 	
Creates up to two vMotion interfaces and configures them with details specified in a CSV file. For a single interface, comment out the entire vmk2 section.

  host_auth_addto_ad_domain.ps1 	
Add hosts in cluster to a specified AD Domain.

  set_vm_max_console_sessions.ps1 	
This script is used to set the maximum remote console sessions allowed on all virtual machines found in the servers.txt file. This is required by many financial industry to prevent more than one concurrent remote console session to a virtual machine in order to an administrator of a VM being shadowed remotely.

  set_vmhost_shell_timeout.ps1 	
Set the ShellTimeOut Setting for all hosts in the specified cluster(s) and restarts the ESXiShell Service. Changes require the SSHShell TSM service to be restarted

  set_vmk_mtu.ps1 	
Updates the MTU size for specified VMKERNEL virtual nics (vmk0, vmk1, vmk2, etc.)
====== Horizon View ======
       set_viewSecurity_extIP.ps1
Updates the External IP address refernece in VMware Horizon View to match the current public IP address of the security server.

Run this script on the View Connection Server
===== Reporting =====

  report_HBAConfig.ps1 	
Report on the HBA Link Speed, HBA Queue Depth, HBA Topology of each ESXi host.

  report_MgmtvMotionIPs.ps1 	
Report on the Management and vMotion IP Addresses (vmk)

  report_ShellTimeOut.ps1 	
Report on the ShellTimeOut Setting for all hosts in specified clusters/DC objects

  report_datastore_space.ps1 	
Script to return all datastores seen in vCenter as well as their capacity, used space and free space.

  report_host_wwn.ps1 	
Report WWN Numbers for hosts specified in $clusters

  report_netConf_CDP.ps1 	
Report the current port group configuration as well as the discovered CDP information.

Handy for comparing actual portgroup config with physical upstream switch config

  report_ntp_syslog.ps1 	
Report the configured NTP Servers as well as the Configured Syslog server

  report_vm_attached_media.ps1 	
Return all CD and Floppy Devices for each VM, including connection state

  report_vm_list.ps1
Reports the Name, vCenter, Datacenter, Cluster, Host and Folder for every virtual machine visible within the PowerCLI session. Also works when connected to multiple VI servers.

Output is saved to a CSV file as specified in $ReportFile 

Helpful in large environments with many vCenter servers.
==== Usage ====
Change the variables at the start of the script, you can easily identify them as they start with $

For example, in the Horizon View script you would change

 # Name of the Security Server
 $SecurityServer = "VIEWSecurityServerNameHere"
and for the log:

 $LogFile = "C:\Temp\set_viewSecurity_extIP.log"


==== Location ====
Rynardt's blog article introducing the scriptkit and asking for help.

http://www.virtualvcp.com/news/197-contribute-to-my-powercli-script-repository-and-help-the-community

Repository:

https://github.com/rynardtspies/ScriptKit


[[Category: PowerCLI]] [[Category: Powershell]]</text>
    <sha1>bd7efc0c3ca561485884b0f8ce9307ee45e70114</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>1308</id>
    <parentid>1022</parentid>
    <timestamp>2014-03-25T08:00:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Artwork */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="689" xml:space="preserve">Below are links to VMware related open source projects, which I've found particularly interesting.

[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[VICL, A VMWare Interface Client for Linux]]

[[psVIC, a powershell Virtual Infrastructure Client]]

[[Unattended ESXi installation]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]

[[Xtravirt Visio action pack]]

[[VMToday Visio stencils]]</text>
    <sha1>96de9a36072d2bb4b9c33330a92f126db19b87c7</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>VMToday Visio stencils</title>
  <ns>0</ns>
  <id>564</id>
  <revision>
    <id>1309</id>
    <timestamp>2014-03-25T08:20:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  VMToday Visio Stencils === author: Josh Townsend ==== Description ==== Josh has made a lot of visio stencils that are available from his website that you can use.  These ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1212" xml:space="preserve">===  VMToday Visio Stencils ===
author: Josh Townsend
==== Description ====
Josh has made a lot of visio stencils that are available from his website that you can use.

These stencils have been made by him in his free time, so do be kind and leave a thank you at his site if you found one of them useful.

He has stencils for:

===== Visio 2003 - 2010 =====
* [http://vmtoday.com/wp-content/uploads/sites/11/2014/03/VMware_vCenter_Orchestrator_Shapes.vss vCenter Orchestrator]
* [http://vmtoday.com/wp-content/uploads/sites/11/2013/05/VMtoday-VMware-View-Visio-Stencil.vss VMware View]
* [http://vmtoday.com/wp-content/uploads/sites/11/2013/05/VMtoday-VMware-Icons.vss VMware vSphere Icons]

===== Visio 2013 =====
* [http://vmtoday.com/wp-content/uploads/sites/11/2014/03/VMware_vCenter_Orchestrator_Shapes.vssx vCenter Orchestrator]
* [http://vmtoday.com/wp-content/uploads/sites/11/2013/05/VMtoday-VMware-View-Visio-Stencil.vssx VMware View]
* [http://vmtoday.com/wp-content/uploads/sites/11/2013/05/VMtoday-VMware-Icons-Visio-Stencil.vssx VMware vSphere Icons]


==== Location ====

For more info please see his website at:

http://vmtoday.com/scripts-free-tools/vmware-visio-stencils/

[[Category: Artwork]]</text>
    <sha1>4427ea192968fb0ec95c5b20beb6527aff0a0ac9</sha1>
  </revision>
  <revision>
    <id>1310</id>
    <parentid>1309</parentid>
    <timestamp>2014-03-25T08:21:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1219" xml:space="preserve">===  VMToday Visio Stencils ===
author: Josh Townsend
==== Description ====
Josh has made a lot of visio stencils that are available from his website that you can use.

These stencils have been made by him in his free time, so do be kind and leave a thank you at his site if you found one of them useful.

He has stencils for:

===== Visio 2003 - 2010 =====
* [http://vmtoday.com/wp-content/uploads/sites/11/2014/03/VMware_vCenter_Orchestrator_Shapes.vss vCenter Orchestrator]
* [http://vmtoday.com/wp-content/uploads/sites/11/2013/05/VMtoday-VMware-View-Visio-Stencil.vss VMware View]
* [http://vmtoday.com/wp-content/uploads/sites/11/2013/05/VMtoday-VMware-Icons.vss VMware vSphere Icons]

===== Visio 2013 =====
* [http://vmtoday.com/wp-content/uploads/sites/11/2014/03/VMware_vCenter_Orchestrator_Shapes.vssx vCenter Orchestrator]
* [http://vmtoday.com/wp-content/uploads/sites/11/2013/05/VMtoday-VMware-View-Visio-Stencil.vssx VMware View]
* [http://vmtoday.com/wp-content/uploads/sites/11/2013/05/VMtoday-VMware-Icons-Visio-Stencil.vssx VMware vSphere Icons]


==== Location ====

For more info please see his website at:

http://vmtoday.com/scripts-free-tools/vmware-visio-stencils/

[[Category: VMware Artwork]]</text>
    <sha1>34bc7d95ffcdb8e2ce8a85b98f1a03e7fdd85071</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Vmsvc/reload</title>
  <ns>0</ns>
  <id>205</id>
  <revision>
    <id>1311</id>
    <parentid>865</parentid>
    <timestamp>2014-03-30T12:59:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* External link */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="295" xml:space="preserve">==== vimsh vmsvc/reload ====
Usage: reload vmid

Reload the virtual machine state from afresh.

==== External link ====

* [http://www.boche.net/blog/index.php/2009/05/02/force-vcenter-server-update-to-reflect-vmx-changes/ Force vCenter Server update to reflect vmx changes]

[[Category: Vimsh]]</text>
    <sha1>d0009e15546c21b17da713cdbf45997f85529a65</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1312</id>
    <parentid>1212</parentid>
    <timestamp>2014-03-30T15:55:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Contribute / help out */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3799" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since January 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

&lt;s&gt;Starting February 2011, the [http://www.twitter.com/vitoolkit @vitoolkit twitter account] that accompanies this site is also active. It will retweet/tweet about VMware specific code, scripts or info related to the VMware api's. It will NOT be used for anything else, there's not going to be any social or commercial tweets. &lt;/s&gt; Early 2012 the site and twitter account had been put on hold due to some family health issues, which made me focus on that. 
Not sure if the twitter account will be resurrected, but I do expect that the site will be active again in 2013. Guess we'll see.

==== Contribute / help out ====
This is an OPEN wiki site, but you have to sign up for editing as we got severely hit by spammers in the past.

We do encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics, search and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you. 

Search tip:
For searching your search term MUST be at least 4 characters long so searching for "VT" or "ESX" will return nothing while there's still content describing this. Instead try another longer related search term like "BIOS" or "backup" for what you are trying to find.

As extra help, the categories are listed below as well.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware Artwork&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>93b467a7abb578d6f02862c0923e835beb9cf89b</sha1>
  </revision>
  <revision>
    <id>1313</id>
    <parentid>1312</parentid>
    <timestamp>2014-03-30T15:55:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Welcome */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3211" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since January 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

==== Contribute / help out ====
This is an OPEN wiki site, but you have to sign up for editing as we got severely hit by spammers in the past.

We do encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics, search and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you. 

Search tip:
For searching your search term MUST be at least 4 characters long so searching for "VT" or "ESX" will return nothing while there's still content describing this. Instead try another longer related search term like "BIOS" or "backup" for what you are trying to find.

As extra help, the categories are listed below as well.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware Artwork&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>468af2228271aa25fc7dbdd84589f93d70f6d722</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>MediaWiki:Sidebar</title>
  <ns>8</ns>
  <id>5</id>
  <revision>
    <id>1314</id>
    <parentid>36</parentid>
    <timestamp>2014-03-30T16:05:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="170" xml:space="preserve">* navigation
** mainpage|mainpage-description
** portal-url|portal
** recentchanges-url|recentchanges
** resources|Resources
** randompage-url|randompage
** helppage|help</text>
    <sha1>6f482ff1259a785f23e01a441d21c76f50a027dc</sha1>
  </revision>
  <revision>
    <id>1341</id>
    <parentid>1314</parentid>
    <timestamp>2014-04-25T12:09:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="175" xml:space="preserve">* navigation
** mainpage|mainpage-description
** portal-url|portal
** recentchanges-url|recentchanges
** resources|Resources
** randompage-url|randompage
** Help:Contents|help</text>
    <sha1>7e8a2246e73920ff9233471b564c4941512ec127</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Protecting ESX VMFS Stores with Automation</title>
  <ns>0</ns>
  <id>445</id>
  <revision>
    <id>1315</id>
    <parentid>887</parentid>
    <timestamp>2014-03-30T16:54:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Added a few small changes to make the format correct so that it is clear the article with the contents is at Mike La Spina's blog not here.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1331" xml:space="preserve">===  factoryResetESXi.pl ===
author: Mike La Spina

==== Description ====

Some time ago Mike shared some interesting information about VMFS volumes that he found using direct analysis in his blog named [http://blog.laspina.ca/roller/Ubiquitous/entry/understanding_vmfs_volumes Understanding VMFS volumes]. 

This spawned some discussions on the VMware Community forums and it became apparent that an automated backup of the critical VMFS info could be useful in the event of an undesirable security event that impacts our system availability. 

By creating a simple backup script process we can provide the ability to recover much more quickly from such events. In this howto guide we will enable this process with a cron job using the existing /etc/cron.daily/ job location directory. 

We simply need to copy an automation script to this location and it will run daily. Or if your change rate is less frequent maybe the /etc/cron.weekly location is more suitable.  ...


==== Location ====

[http://blog.laspina.ca/roller/Ubiquitous/entry/understanding_vmfs_volumes Ubiquitous: Protecting ESX VMFS Stores with Automation]

See also:
[http://blog.laspina.ca/roller/Ubiquitous/entry/additional_vmfs_backup_automation_script Ubiquitous: Additional VMFS Backup Automation script features]

[[Category: Bash]] [[Category: Forensics]]</text>
    <sha1>4cd79fbe67f862b624f15c47d5d4db9bb52ecc8f</sha1>
  </revision>
  <revision>
    <id>1316</id>
    <parentid>1315</parentid>
    <timestamp>2014-03-30T16:55:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* factoryResetESXi.pl */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1302" xml:space="preserve">author: Mike La Spina

==== Description ====

Some time ago Mike shared some interesting information about VMFS volumes that he found using direct analysis in his blog named [http://blog.laspina.ca/roller/Ubiquitous/entry/understanding_vmfs_volumes Understanding VMFS volumes]. 

This spawned some discussions on the VMware Community forums and it became apparent that an automated backup of the critical VMFS info could be useful in the event of an undesirable security event that impacts our system availability. 

By creating a simple backup script process we can provide the ability to recover much more quickly from such events. In this howto guide we will enable this process with a cron job using the existing /etc/cron.daily/ job location directory. 

We simply need to copy an automation script to this location and it will run daily. Or if your change rate is less frequent maybe the /etc/cron.weekly location is more suitable.  ...


==== Location ====

[http://blog.laspina.ca/roller/Ubiquitous/entry/understanding_vmfs_volumes Ubiquitous: Protecting ESX VMFS Stores with Automation]

See also:
[http://blog.laspina.ca/roller/Ubiquitous/entry/additional_vmfs_backup_automation_script Ubiquitous: Additional VMFS Backup Automation script features]

[[Category: Bash]] [[Category: Forensics]]</text>
    <sha1>cf6c432b690183b7fc63def00dcba6986a4d51e1</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>User:Wila</title>
  <ns>2</ns>
  <id>229</id>
  <revision>
    <id>1317</id>
    <parentid>439</parentid>
    <timestamp>2014-03-30T18:05:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="327" xml:space="preserve">See the [[VI-Toolkit:About |about page]] if you want to know more about me :)

If you want to have a user account or have a question about the site then please do let me know.

You can reach me by email by using my username here and sending it to the domain of this site or contact me via [http://www.twitter.com/wilva twitter]</text>
    <sha1>d745d69440153bdea3263c93f516d8db6a344c89</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>1318</id>
    <parentid>1079</parentid>
    <timestamp>2014-03-30T18:08:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Things to do */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2524" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* &lt;s&gt; Add daily backup to another machine&lt;/s&gt; weekly is fine
* &lt;s&gt;Add proper category pages. Partly done &lt;/s&gt; 
* &lt;s&gt;Add "what's new" to the main page&lt;/s&gt; use [[Special:RecentChanges]] link at top of page instead.
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* &lt;s&gt;Fix theme template / settings so that we can edit per paragraph as well&lt;/s&gt;
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* &lt;s&gt;Find a better way to present what's available on the site, improve ways to restructure the data. &lt;/s&gt; The support for category tree at the main page now gives a much easier way to navigate the site. But it never hurts to find better ways as this doesn't scale too well (look at the vimsh category for example)
* Improve main page
* Add example code
* &lt;s&gt;Add a theme for mobile phones, so it is easier to read the content&lt;/s&gt; Disabled the plugin as it was hopelessly out of date, I think the current theme is rather OK on mobile, but no phone to test now.

==== Things to make our mind up about ====

* Does the site need a forum? &lt;- No, you can use the talk page if you have a comment or contact me directly. Maybe in a later incarnation.
* Does the site need an instant messager type of control ? &lt;- No, use twitter @wilva for contacting me or use email wila under the site's domain name.
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ? &lt;- No, we don't host much code on the site right now. Pretty much all of the code snippets are located elsewhere and copying those over to this site makes no sense as it will only complicate things.
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ? Probably ;)

[[Category: website]]</text>
    <sha1>4018b1d77d008f35cd39a4ace5d1fd0772c6d46f</sha1>
  </revision>
  <revision>
    <id>1319</id>
    <parentid>1318</parentid>
    <timestamp>2014-03-30T18:09:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Things to do */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2539" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* &lt;s&gt; Add daily backup to another machine&lt;/s&gt; weekly is fine
* &lt;s&gt;Add proper category pages. Partly done &lt;/s&gt; 
* &lt;s&gt;Add "what's new" to the main page&lt;/s&gt; use [[Special:RecentChanges Recent changes]] link at top of page instead.
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* &lt;s&gt;Fix theme template / settings so that we can edit per paragraph as well&lt;/s&gt;
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* &lt;s&gt;Find a better way to present what's available on the site, improve ways to restructure the data. &lt;/s&gt; The support for category tree at the main page now gives a much easier way to navigate the site. But it never hurts to find better ways as this doesn't scale too well (look at the vimsh category for example)
* Improve main page
* Add example code
* &lt;s&gt;Add a theme for mobile phones, so it is easier to read the content&lt;/s&gt; Disabled the plugin as it was hopelessly out of date, I think the current theme is rather OK on mobile, but no phone to test now.

==== Things to make our mind up about ====

* Does the site need a forum? &lt;- No, you can use the talk page if you have a comment or contact me directly. Maybe in a later incarnation.
* Does the site need an instant messager type of control ? &lt;- No, use twitter @wilva for contacting me or use email wila under the site's domain name.
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ? &lt;- No, we don't host much code on the site right now. Pretty much all of the code snippets are located elsewhere and copying those over to this site makes no sense as it will only complicate things.
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ? Probably ;)

[[Category: website]]</text>
    <sha1>a3320ccfcdd48fd69a92b50ee44d3abe06e9ae1f</sha1>
  </revision>
  <revision>
    <id>1320</id>
    <parentid>1319</parentid>
    <timestamp>2014-03-30T18:11:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Things to do */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2539" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* &lt;s&gt; Add daily backup to another machine&lt;/s&gt; weekly is fine
* &lt;s&gt;Add proper category pages. Partly done &lt;/s&gt; 
* &lt;s&gt;Add "what's new" to the main page&lt;/s&gt; use [[Special:RecentChanges|Recent changes]] link at top of page instead.
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* &lt;s&gt;Fix theme template / settings so that we can edit per paragraph as well&lt;/s&gt;
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* &lt;s&gt;Find a better way to present what's available on the site, improve ways to restructure the data. &lt;/s&gt; The support for category tree at the main page now gives a much easier way to navigate the site. But it never hurts to find better ways as this doesn't scale too well (look at the vimsh category for example)
* Improve main page
* Add example code
* &lt;s&gt;Add a theme for mobile phones, so it is easier to read the content&lt;/s&gt; Disabled the plugin as it was hopelessly out of date, I think the current theme is rather OK on mobile, but no phone to test now.

==== Things to make our mind up about ====

* Does the site need a forum? &lt;- No, you can use the talk page if you have a comment or contact me directly. Maybe in a later incarnation.
* Does the site need an instant messager type of control ? &lt;- No, use twitter @wilva for contacting me or use email wila under the site's domain name.
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ? &lt;- No, we don't host much code on the site right now. Pretty much all of the code snippets are located elsewhere and copying those over to this site makes no sense as it will only complicate things.
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* Would it be better to change our url to https://wiki.vi-toolkit.com ? Probably ;)

[[Category: website]]</text>
    <sha1>b58c53544003e8504021e9921e4b515a92f2595d</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: Snap reminder</title>
  <ns>0</ns>
  <id>478</id>
  <revision>
    <id>1321</id>
    <parentid>983</parentid>
    <timestamp>2014-03-31T04:31:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="712" xml:space="preserve">author: Alan Renouf
==== Description ====
Snapshots are a great feature for virtual machines, but leaving them open for a long time is unwanted for a number of reasons. 

Alan has written a script here that checks your hosts for virtual machines which have open snapshots for more as 2 weeks. The scripts then finds out who created them and as extra bonus even automatically sends the offender an email based on the email address in their Active Directory subscription.


==== Location ====

http://www.virtu-al.net/2009/06/22/powercli-snapreminder/

Extended version by Steve Schofield:

http://www.iislogs.com/steveschofield/vmware-snapshot-reminder-script

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>dc6611c87de0e3b34dbc70d3da6c242e69f2c93b</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI</title>
  <ns>0</ns>
  <id>524</id>
  <revision>
    <id>1322</id>
    <parentid>1305</parentid>
    <timestamp>2014-03-31T04:35:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5977" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]
===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>8d0797e47485bc81b05df1680448136c034b457f</sha1>
  </revision>
  <revision>
    <id>1324</id>
    <parentid>1322</parentid>
    <timestamp>2014-04-07T06:57:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* not categorized */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5883" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

===== VM Configuration =====

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>03e4ea086a70f602063317f8bd9174d064a0ae6d</sha1>
  </revision>
  <revision>
    <id>1325</id>
    <parentid>1324</parentid>
    <timestamp>2014-04-07T06:58:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VM Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5978" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

===== VM Configuration =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>62cd3876f5db63f5f2e7320479ae397a9c8d2a30</sha1>
  </revision>
  <revision>
    <id>1326</id>
    <parentid>1325</parentid>
    <timestamp>2014-04-07T07:00:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Learning VI-Toolkit Powershell */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6086" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm, still a great idea, but crossed out as you as reader probably should not spend time on clicking through it.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [[PowerCLI: Oneliners]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

===== VM Configuration =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>e91096e01be8f4d5eddfd902ac48fddcead78520</sha1>
  </revision>
  <revision>
    <id>1327</id>
    <parentid>1326</parentid>
    <timestamp>2014-04-07T07:00:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* not categorized */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6059" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm, still a great idea, but crossed out as you as reader probably should not spend time on clicking through it.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

===== VM Configuration =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>b0cde19c474d476c01da816e622a1b027da6558d</sha1>
  </revision>
  <revision>
    <id>1328</id>
    <parentid>1327</parentid>
    <timestamp>2014-04-07T07:01:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* PowerCLI Oneliners */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6086" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm, still a great idea, but crossed out as you as reader probably should not spend time on clicking through it.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

===== VM Configuration =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>3eab213a78455340bdd9d0b5353c11e1fffb2ec7</sha1>
  </revision>
  <revision>
    <id>1329</id>
    <parentid>1328</parentid>
    <timestamp>2014-04-07T07:37:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Storage */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6120" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm, still a great idea, but crossed out as you as reader probably should not spend time on clicking through it.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6973 HBA Load Balancer]

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

===== VM Configuration =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>73e2f82f1362c277c4bf6f412e4fcf0e992ef036</sha1>
  </revision>
  <revision>
    <id>1330</id>
    <parentid>1329</parentid>
    <timestamp>2014-04-07T07:37:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* not categorized */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6053" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm, still a great idea, but crossed out as you as reader probably should not spend time on clicking through it.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====
===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

===== VM Configuration =====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

===== Host Management =====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>d7a44e69c23e132a18cc0f656057fc292fb6b2c4</sha1>
  </revision>
  <revision>
    <id>1333</id>
    <parentid>1330</parentid>
    <timestamp>2014-04-07T08:10:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* PowerCLI scripts */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6136" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm, still a great idea, but crossed out as you as reader probably should not spend time on clicking through it.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====

===== integration =====

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

* [[PowerCLI: WebPowerCLI, run scripts from your browser]]

===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]


==== VM Configuration ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

==== Host Management ====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>41c8d6ef332fcf710f86042e524d24bf989d04e3</sha1>
  </revision>
  <revision>
    <id>1335</id>
    <parentid>1333</parentid>
    <timestamp>2014-04-14T08:43:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6203" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]


* &lt;s&gt;[[Powershell CMDLET list]] (thank you Alan Renouf for the idea and initial work)&lt;/s&gt; Doesn't contain much atm, still a great idea, but crossed out as you as reader probably should not spend time on clicking through it.

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====

===== integration =====

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

* [[PowerCLI: WebPowerCLI, run scripts from your browser]]

===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]


==== VM Configuration ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

==== Host Management ====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

* [[PowerCLI: Update ESXi Root Password with Password Generator]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>aec643bbab3faf280188f100a1f0b1934249a855</sha1>
  </revision>
  <revision>
    <id>1338</id>
    <parentid>1335</parentid>
    <timestamp>2014-04-14T09:02:21Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Learning VI-Toolkit Powershell */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6110" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]

* [https://www.vmware.com/support/developer/PowerCLI/PowerCLI55R2/html/index.html VMware's PowerCLI 5.5 R2 online cmdlet reference]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====

===== integration =====

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

* [[PowerCLI: WebPowerCLI, run scripts from your browser]]

===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]


==== VM Configuration ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

==== Host Management ====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

* [[PowerCLI: Update ESXi Root Password with Password Generator]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>1e1a451ead6cedd792224263ffb7fd1aebc72387</sha1>
  </revision>
  <revision>
    <id>1345</id>
    <parentid>1338</parentid>
    <timestamp>2014-04-26T08:56:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6151" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]

* [https://www.vmware.com/support/developer/PowerCLI/PowerCLI55R2/html/index.html VMware's PowerCLI 5.5 R2 online cmdlet reference]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====

===== integration =====

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

* [[PowerCLI: WebPowerCLI, run scripts from your browser]]

===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]


==== VM Configuration ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

==== Host Management ====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

===== Integration with ESXi shell =====

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update ESXi Root Password with Password Generator]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>f4fc24f9dd7fce2dafc0557dc38b855eeaa7bdda</sha1>
  </revision>
  <revision>
    <id>1346</id>
    <parentid>1345</parentid>
    <timestamp>2014-04-26T11:14:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6222" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]

* [https://www.vmware.com/support/developer/PowerCLI/PowerCLI55R2/html/index.html VMware's PowerCLI 5.5 R2 online cmdlet reference]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====

===== integration =====

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

* [[PowerCLI: WebPowerCLI, run scripts from your browser]]

===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]


==== VM Configuration ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

==== Host Management ====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

* [[PowerCLI: ESXi 5.0 / ESXi 5.1 Host Backup &amp; Restore GUI Utility]]

===== Integration with ESXi shell =====

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update ESXi Root Password with Password Generator]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>ddc7ea99913644c91813e20774db393ba17a56ef</sha1>
  </revision>
  <revision>
    <id>1348</id>
    <parentid>1346</parentid>
    <timestamp>2014-04-26T11:39:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Integration with ESXi shell */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6275" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]

* [https://www.vmware.com/support/developer/PowerCLI/PowerCLI55R2/html/index.html VMware's PowerCLI 5.5 R2 online cmdlet reference]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====

===== integration =====

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

* [[PowerCLI: WebPowerCLI, run scripts from your browser]]

===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]


==== VM Configuration ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

==== Host Management ====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

* [[PowerCLI: ESXi 5.0 / ESXi 5.1 Host Backup &amp; Restore GUI Utility]]

===== Integration with ESXi shell =====

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update ESXi Root Password with Password Generator]]

* [[PowerCLI: enable SSH GUI for vSphere clusters]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>1956de520e4eee18a08a6b77da750a4e27b36fee</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: VM stats and Google Charts</title>
  <ns>0</ns>
  <id>565</id>
  <revision>
    <id>1323</id>
    <timestamp>2014-03-31T04:41:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  VM stats using PowerCLI and Google Charts  === author: Paolo Pepe ==== Description ====  The article displays a great example on how-to use powerCLI to generate an HTML p..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="655" xml:space="preserve">===  VM stats using PowerCLI and Google Charts  ===
author: Paolo Pepe
==== Description ====

The article displays a great example on how-to use powerCLI to generate an HTML page and fancy graphic charts using Google charts.

==== Usage ====
Example usage of Get-Stat powerCLI command:
 Get-Stat -Entity (Get-VMHost -Name 10.0.1.62 | Get-VM | Where-Object PowerState -match "PoweredOn") -Stat $stat -Start (Get-Date).AddHours(-24) -MaxSamples (10) -IntervalMins 10 | Measure-Object Value -Average  
==== Location ====

http://hostilecoding.blogspot.com/2014/03/vmware-vm-stats-using-powercli-and.html


[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>2abcd4a4ba9bca75fa96a87b8440b30dd6500cbd</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: Upgrading your VMFS datastores</title>
  <ns>0</ns>
  <id>541</id>
  <revision>
    <id>1331</id>
    <parentid>1243</parentid>
    <timestamp>2014-04-07T07:51:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="745" xml:space="preserve">===  Upgrading your VMFS datastores with PowerCLI ===
author: Robert van den Nieuwendijk
==== Description ====
This script gives you the possibility to run in-place upgrades on your VMFS datastores to upgrade them from VMFS-3 to VMFS-5

==== Usage ====
 PowerCLI C:\&gt; Get-Datastore -Name Datastore1 | Upgrade-VmfsDatastore -WhatIf
 What if: Performing operation "Upgrade-VmfsDatastore" on Target "Datastore1".
 PowerCLI C:\&gt; Get-Datastore -Name Datastore1 | Upgrade-VmfsDatastore

 Name FreeSpaceGB CapacityGB
 ---- ----------- ---------- 
 Datastore1 103,861 499,750
==== Location ====

http://rvdnieuwendijk.com/2013/06/05/upgrading-your-vmfs-datastores-with-powercli/

[[Category: PowerCLI]] [[Category: Host Management]][[Category: Storage]]</text>
    <sha1>262be9496c6ac85637ba2bee623c011d8a6e04af</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: HBA Load Balancer</title>
  <ns>0</ns>
  <id>566</id>
  <revision>
    <id>1332</id>
    <timestamp>2014-04-07T08:04:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Fixed the broken link to the HBA Loadbalancer script from Rob Mokkink</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="734" xml:space="preserve">===  HBA Load Balancing ===
author: Rob Mokkink
==== Description ====

Rob Mokkink has made a script to balance LUNs over different HBA’s.
In short it:
* Sets the Path Management Policy to fixed
* Sets odd luns to a preferred path of vmhba1
* Sets even luns to a preferred path of vmhba2

==== Usage ====
The script uses integrated authentication. 

That means, the account running the script should have sufficient rights in virtualcenter. 

There's a line in the script that specifies the virtualcenter host.

==== Location ====

http://virtualfuture.info/2008/07/vmware-hba-loadbalancer-script/

[https://communities.vmware.com/thread/156302 VMware communities: storage-path script]


[[Category: PowerCLI]] [[Category: Storage]]</text>
    <sha1>5bbfe56ccb37d7170d8bbbc40e46fd04e9b95507</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: WebPowerCLI, run scripts from your browser</title>
  <ns>0</ns>
  <id>567</id>
  <revision>
    <id>1334</id>
    <timestamp>2014-04-07T08:18:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  WebPowerCLI  === author: Paolo Pepe ==== Description ==== WebPowerCLI allows you to run PowerCLI commands via your web browser.  A major advantage of running PowerCLI thi..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1124" xml:space="preserve">===  WebPowerCLI  ===
author: Paolo Pepe
==== Description ====
WebPowerCLI allows you to run PowerCLI commands via your web browser.

A major advantage of running PowerCLI this way is that you can write and run scripts virtually from any platform.

===== Features =====

*Run PowerCLI from web browser.
*PowerCLI cmdlet autocomplete.
*Click to add cmdlet. Full syntax for any PowerCLI cmdlet.
*Every cmdlet has a link to the official VMware documentation.
*Easy to extend, you can put your own PowerCLI scripts in the "ps" folder in order to use them directly from WebPowerCLI.
*EsxCLI support.

==== Usage ====

The first cmdlet of your scripts must always be Connect-VIServer (...) in order to establish a connection to the vCenter Server or directly to an ESXi host.

For example:

 Connect-VIServer -Server &lt;vcenter_ip_address&gt; -User &lt;username&gt; -Password &lt;password&gt;

After that... well do go and check out Paolo's page below, it has all the screenshots and directions to use it.

==== Location ====

http://hostilecoding.blogspot.com/2014/02/vmware-webpowercli.html


[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>5d5910b758fd30c77157cf4132ce2fe6377c7e57</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: Update ESXi Root Password with Password Generator</title>
  <ns>0</ns>
  <id>568</id>
  <revision>
    <id>1336</id>
    <timestamp>2014-04-14T08:52:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  PowerCLI – Update ESXi Root Password with Password Generator === author: Jonathan Frappier ==== Description ==== This script gives you the possibility to automatically ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="780" xml:space="preserve">===  PowerCLI – Update ESXi Root Password with Password Generator ===
author: Jonathan Frappier
==== Description ====
This script gives you the possibility to automatically generate a new password for the specified user on each host in the cluster you connect to.

==== Usage ====
The script prompts you for:
* Name of the vCenter Server
* Name of the cluster
* Name of the account you want to change
* Current password for the account to change

After that it will change the password of the user within that cluster and change the details into the Change-HostPasswords.csv file in the format:
 Date, Host, Password, Result
==== Location ====

http://www.virtxpert.com/powercli-update-esxi-root-password-password-generator/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>8ecfafa02ab2be1fd5b5850bd3e35738955da6c5</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Category:PowerCLI</title>
  <ns>14</ns>
  <id>454</id>
  <revision>
    <id>1337</id>
    <parentid>993</parentid>
    <timestamp>2014-04-14T08:56:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="204" xml:space="preserve">Software written in [[PowerCLI]]. [[PowerCLI]] is the SDK software library for managing vSphere hosts.

There's more scripts on the [[PowerShell]] page that have not been explicitly tagged as [[PowerCLI]]</text>
    <sha1>e6e8610151276e62fc75df53a0f4b2b07843d295</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>VI Toolkit for windows</title>
  <ns>0</ns>
  <id>11</id>
  <revision>
    <id>1339</id>
    <parentid>863</parentid>
    <timestamp>2014-04-14T09:05:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1036" xml:space="preserve">'' Note: Obsolete use [[PowerCLI]] instead ''

==== VI Toolkit for windows ====

The official [http://www.vmware.com/support/developer/windowstoolkit/ VMware VI Toolkit for windows landing page] for accessing the Virtual Infrastructure API using [[PowerShell]] or .net

==== VI Toolkit extensions ====

For this you'll need to upgrade to [http://www.microsoft.com/downloads/details.aspx?familyid=C913AEAB-D7B4-4BB1-A958-EE6D7FE307BC&amp;displaylang=en PowerShell 2 CTP3] and the code is at:
http://www.codeplex.com/vitoolkitextensions

See this NTPRO.nl article for details:
[http://www.ntpro.nl/blog/archives/741-Enabling-the-VI-Toolkit-Extensions.html Enabling the VI Toolkit Extensions]

==== VI Toolkit for .net ====

The VI Toolkit for .NET is a .NET library designed to bring object-oriented design to the VI API by transforming managed object references into first class objects, as well as providing helpful method, property, and class abstractions.

http://sourceforge.net/projects/vitfordotnet/

[[Category:SDK]] [[Category:.net]]</text>
    <sha1>bfcdd59e1e8f43567b6027beaaf6b6f76e294ea9</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Learning Powershell</title>
  <ns>0</ns>
  <id>511</id>
  <revision>
    <id>1340</id>
    <parentid>1128</parentid>
    <timestamp>2014-04-14T09:07:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="583" xml:space="preserve">* [[BEGINNERS PAGE | Beginners page]]

* [http://technet.microsoft.com/en-us/library/hh848794.aspx Microsoft Cmdlet reference]


==== Powershell books ====

* [http://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=df8ed469-9007-401c-85e7-46649a32d0e0 Microsoft Windows PowerShell Quick Reference (Feb 2010)]

* [http://blog.sapien.com/index.php/2009/12/01/free-windows-powershell-ebook/ Sapien technologies Free windows Powershell eBook]

==== Powershell Cmdlet Deep Dive ====

* [[Jonathan Medd's Powershell 2.0 One Cmdlet at a time]]


[[Category: Powershell]]</text>
    <sha1>d85e285f0c0b2de4eff9657ad8b940be5632e72f</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>1342</id>
    <parentid>1109</parentid>
    <timestamp>2014-04-25T12:12:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VMware vimsh */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3048" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[Vimsh]] Help documentation and general tips

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]

[[Performing emergency shut down of VM's on ESX]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

[[APC/APCUPSD ESX/ESXi Host shutdown script]]

==== Perl scripts ====
[[Recover vmx from log file]]

==== AppleScript ====

[http://communities.vmware.com/thread/122793 AppleScript to Run Virtual Machine and switch to Full Screen View or Unity View at Login]

==== Javascript ====
[[Ghetto vCenter 4.0 Unattended Installer]]

==== In the pipeline ====
[[External scripts that are not processed yet]]</text>
    <sha1>5847639ef337a0a9f92e64e5fcf0b566bd768284</sha1>
  </revision>
  <revision>
    <id>1343</id>
    <parentid>1342</parentid>
    <timestamp>2014-04-25T12:13:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* ESX Service Console */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3060" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

[[esxcli]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[Vimsh]] Help documentation and general tips

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]

[[Performing emergency shut down of VM's on ESX]]


==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

[[APC/APCUPSD ESX/ESXi Host shutdown script]]

==== Perl scripts ====
[[Recover vmx from log file]]

==== AppleScript ====

[http://communities.vmware.com/thread/122793 AppleScript to Run Virtual Machine and switch to Full Screen View or Unity View at Login]

==== Javascript ====
[[Ghetto vCenter 4.0 Unattended Installer]]

==== In the pipeline ====
[[External scripts that are not processed yet]]</text>
    <sha1>02888f706e5dcea4af53d43b511bc3280e978532</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Esxcli</title>
  <ns>0</ns>
  <id>569</id>
  <revision>
    <id>1344</id>
    <timestamp>2014-04-25T12:15:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "  === Disable the firewall === Disable the firewall completely.   esxcli network firewall set --enabled false"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false</text>
    <sha1>4f6c848a9681ef239a83ded156d72b70bbcfb51d</sha1>
  </revision>
  <revision>
    <id>1352</id>
    <parentid>1344</parentid>
    <timestamp>2014-04-26T14:04:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="371" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false


=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>01277537c491009e9ccd93b02751b6cbc457610b</sha1>
  </revision>
  <revision>
    <id>1353</id>
    <parentid>1352</parentid>
    <timestamp>2014-04-26T14:04:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* resources */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="378" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false


=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>f7f39c29437c213b29dd1842238823af30898b88</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: ESXi 5.0 / ESXi 5.1 Host Backup &amp; Restore GUI Utility</title>
  <ns>0</ns>
  <id>570</id>
  <revision>
    <id>1347</id>
    <timestamp>2014-04-26T11:23:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Host Backup &amp; Restore utility === author: Sean Duffy ==== Description ==== This utility allows you to backup your host configuration to a file and then restore the config..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="667" xml:space="preserve">===  Host Backup &amp; Restore utility ===
author: Sean Duffy
==== Description ====
This utility allows you to backup your host configuration to a file and then restore the configuration at another host.
Sean has released several updates since his first 1.0 release, he's currently at version 1.3

Please note that this does not back up your virtual machines!

==== Usage ====
Download the script from his page and run:

 .\ESXi5-Backup-Restore-Utility-1.3.ps1
Then follow the steps on the screen in the GUI.

==== Location ====

http://www.shogan.co.uk/vmware/esxi-5-0-host-backup-restore-gui-utility-powercli-based/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>10f7a17e06041ee48d0bfe497c17b5943e47b4bd</sha1>
  </revision>
  <revision>
    <id>1351</id>
    <parentid>1347</parentid>
    <timestamp>2014-04-26T13:59:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Location */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="837" xml:space="preserve">===  Host Backup &amp; Restore utility ===
author: Sean Duffy
==== Description ====
This utility allows you to backup your host configuration to a file and then restore the configuration at another host.
Sean has released several updates since his first 1.0 release, he's currently at version 1.3

Please note that this does not back up your virtual machines!

==== Usage ====
Download the script from his page and run:

 .\ESXi5-Backup-Restore-Utility-1.3.ps1
Then follow the steps on the screen in the GUI.

==== Location ====

http://www.shogan.co.uk/vmware/esxi-5-0-host-backup-restore-gui-utility-powercli-based/

alternative script (totally unrelated, but have to put it somewhere):

[http://poshcode.org/4036 get-ESXiHostConfigBackup by Jimmy Hester on powershell code repository]

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>18fb212eedbd86a4f6fb2b75cd0166e113ec846d</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>PowerCLI: enable SSH GUI for vSphere clusters</title>
  <ns>0</ns>
  <id>571</id>
  <revision>
    <id>1349</id>
    <timestamp>2014-04-26T11:43:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  The VirtAdmin SSH Tool for vSphere Clusters === author: James Green ==== Description ==== Using this GUI powerCLI tool you can simply switch SSH support on/off for all of..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="464" xml:space="preserve">===  The VirtAdmin SSH Tool for vSphere Clusters ===
author: James Green
==== Description ====
Using this GUI powerCLI tool you can simply switch SSH support on/off for all of the hosts in a cluster managed by vCenter.

==== Usage ====
run the script, fill in your vCenter URL and the cluster you want to enable/disable SSH for.
==== Location ====

http://www.virtadmin.com/virtadmin-ssh-tool-vsphere-clusters/

[[Category: PowerCLI]] [[Category: Host Management]]</text>
    <sha1>187cd2611d1a2c51325e850cdf529d0130943696</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>VMware KB articles</title>
  <ns>0</ns>
  <id>528</id>
  <revision>
    <id>1350</id>
    <parentid>1208</parentid>
    <timestamp>2014-04-26T13:46:43Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VMware KB articles */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1223" xml:space="preserve">==== VMware KB articles ====

There's very interesting code specific Knowledge Base articles to be found. 

[http://kb.vmware.com/kb/1033447 Recommended values in the soapAction field when forming Soap Requests for vSphere API]

[http://kb.vmware.com/kb/1007289 Changing or blocking the default ports 80 (http) and 443 (https) on ESX hosts]


[http://kb.vmware.com/kb/738107 What is the syntax for vmware-cmd createsnapshot?]

[http://kb.vmware.com/kb/1019561 Collecting VIX diagnostic information]

[http://kb.vmware.com/kb/1026554 Enabling logging for Likewise agents on ESX/ESXi 4.1]

[http://kb.vmware.com/kb/1033317 Recording ESX or ESXi VMkernel state with vsi_traverse]

[http://kb.vmware.com/kb/1031785 Checking cpuinfo information on an ESXi host]


Most of Williams articles can be considered "Knowledge base" type of articles, so just adding them here (might be easier to just add a link to the site, read all his posts!)

[http://www.virtuallyghetto.com/2012/06/ovf-runtime-environment.html Get OVF Runtime Environment for vApp via VMware Tools or ISO]

[http://www.virtuallyghetto.com/2012/06/how-to-copy-vms-directly-between-esxi.html Copy VMs Directly Between ESXi Hosts Without Shared Storage using ovftool]</text>
    <sha1>84056a42f569b7ecef4d81007019f6b69052ef89</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Ruby</title>
  <ns>0</ns>
  <id>530</id>
  <revision>
    <id>1354</id>
    <parentid>1298</parentid>
    <timestamp>2014-04-27T09:53:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="383" xml:space="preserve">=== projects ===
[[vco-rest]]

[[vixen]]

[[rbvmomi]]

[[rvc]]

=== useful resources ===

[http://www.virtuallyghetto.com/2013/02/exploring-vcloud-api-using-ruby.html Exploring the vCloud API Using Ruby]

[http://www.virtuallyghetto.com/2013/02/exploring-vcloud-networking-security.html Exploring the vCloud Networking &amp; Security API Using Ruby (virtuallyghetto)]

[[Category: Ruby]]</text>
    <sha1>621fe1e22ae01bb58d7230f55a5d189a093e2ede</sha1>
  </revision>
  <revision>
    <id>1355</id>
    <parentid>1354</parentid>
    <timestamp>2014-04-27T09:54:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* useful resources */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="401" xml:space="preserve">=== projects ===
[[vco-rest]]

[[vixen]]

[[rbvmomi]]

[[rvc]]

=== useful resources ===

[http://www.virtuallyghetto.com/2013/02/exploring-vcloud-api-using-ruby.html Exploring the vCloud API Using Ruby (virtuallyghetto)]

[http://www.virtuallyghetto.com/2013/02/exploring-vcloud-networking-security.html Exploring the vCloud Networking &amp; Security API Using Ruby (virtuallyghetto)]

[[Category: Ruby]]</text>
    <sha1>8f7aec6c3aba797ee87f68e0185a08a13a4388b5</sha1>
  </revision>
</page>
<page arvcontinue="20140306092303|1307">
  <title>Build host vmware kernel modules</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>1356</id>
    <parentid>1101</parentid>
    <timestamp>2014-06-19T22:11:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3476" xml:space="preserve">====Integrated modules build script sometimes fails====
The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

====The solution====
You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm -f /etc/vmware/not_configured 

====Preconditions for the script to work====
You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko


If you get error "Icon name must be set." then you can fix that by adding the parameter for that to vmware-modconfig:

 vmware-modconfig --icon="vmware-workstation"

If you get error "Application name must be set" then you can fix that by adding the parameter to set that:

 vmware-modconfig --appname="VMware Workstation"

====Alternative solution====
Of course there is still a vmware application available that you can use for this as well.
[http://communities.vmware.com/people/birdie Birdie] came up with a smart alternative so you can keep things like they used to be by creating an alias for the modconfig with the correct parameters to run it in the console.
 alias vmware-config.pl='vmware-modconfig --console --install-all'

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>e19ac467021cd9bdb8f11269a426fd9592b053c4</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Build host vmware kernel modules</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>1357</id>
    <parentid>1356</parentid>
    <timestamp>2014-06-19T22:34:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4135" xml:space="preserve">====Integrated modules build script sometimes fails====
The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

====The solution====
You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm -f /etc/vmware/not_configured 

====Preconditions for the script to work====
You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko


If you get error "Icon name must be set." then you can fix that by adding the parameter for that to vmware-modconfig:

 vmware-modconfig --icon="vmware-workstation"

If you get error "Application name must be set" then you can fix that by adding the parameter to set that:

 vmware-modconfig --appname="VMware Workstation"

If there are still problems then vmware-modconfig tells you where it writes out a log, it helps to read it for example:
  vmware-modconfig  --icon="vmware-workstation"  --appname="VMware Workstation"
  Logging to /root/tmp/vmware-root/modconfig-2221.log

Check that file!
In my case for example it says:
 failed to find /lib/modules/3.12.xx/build/include/linux/version.h

That's because in later versions the version.h file has been moved (smart move!) to another location.
So in order to get past that you have to add a symbolic link (replace)

 # ln -s /usr/src/`uname -r`/include/generated/uapi/linux/version.h /usr/src/`uname -r`/include/linux/version.h

====Alternative solution====
Of course there is still a vmware application available that you can use for this as well.
[http://communities.vmware.com/people/birdie Birdie] came up with a smart alternative so you can keep things like they used to be by creating an alias for the modconfig with the correct parameters to run it in the console.
 alias vmware-config.pl='vmware-modconfig --console --install-all'

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>d1da527bab6b61bc222833c3e07794fcde06c378</sha1>
  </revision>
  <revision>
    <id>1396</id>
    <parentid>1357</parentid>
    <timestamp>2015-10-12T10:30:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4392" xml:space="preserve">====Integrated modules build script sometimes fails====
The kernel modules script  on linux hosts VMware Player version 2.5 and VMware Workstation 6.5.x has received a graphical user interface. 
Because of this it provides a much smoother end user experience when the user upgrades to a newer version of the kernel.
Unless there's a dependency on which it breaks.
In that case you might get the error 

 VMware Player is installed, but it has not been (correctly) configured for your running kernel. To (re-)configure it, your system administrator must find and run "vmware-config.pl"...

Unfortunately there is no vmware-config.pl script anymore, that's a left over from the previous version.

Lucky enough [http://communities.vmware.com/people/Noel Noel] on the vmware forums has created a script to resolve this which can be found here [http://communities.vmware.com/message/1088282#1088282 6.5 Segfault in 6.5 beta]

====The solution====
You must run the following script with root privileges

 #!/bin/bash
 
 cd ~
 rm -rf vmware-modules
 mkdir vmware-modules
 cd vmware-modules
 find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
 mkdir -p /lib/modules/`uname -r`/misc
 rm -f /lib/modules/`uname -r`/misc/{vmblock.ko,vmci.ko,vmmon.ko,vmnet.ko,vsock.ko}
 cd vmblock-only; make; cd ..; cp -p vmblock.o /lib/modules/`uname -r`/misc/vmblock.ko
 cd vmci-only; make; cd ..; cp -p vmci.o /lib/modules/`uname -r`/misc/vmci.ko
 cd vmmon-only; make; cd ..; cp -p vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
 cd vmnet-only; make; cd ..; cp -p vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
 #cd vmppuser-only; make; cd ..; cp -p vmppuser.o /lib/modules/`uname -r`/misc/vmppuser.ko
 cd vsock-only; make; cd ..; cp -p vsock.o /lib/modules/`uname -r`/misc/vsock.ko
 depmod -a
 service vmware restart
 #If a new install, remove the not_configured tag or the error will keep coming back
 rm -f /etc/vmware/not_configured 

====Preconditions for the script to work====
You will have to get your kernel-headers before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, your folder with kernel modules should look like this:
 $ ls -l /lib/modules/`uname -r`/misc
 total 376
 -rw-r--r-- 1 root root 36509 2008-12-07 01:07 vmblock.ko
 -rw-r--r-- 1 root root 95745 2008-12-07 01:07 vmci.ko
 -rw-r--r-- 1 root root 118128 2008-12-07 01:07 vmmon.ko
 -rw-r--r-- 1 root root 79897 2008-12-07 01:07 vmnet.ko
 -rw-r--r-- 1 root root 34834 2008-12-07 01:07 vsock.ko


If you get error "Icon name must be set." then you can fix that by adding the parameter for that to vmware-modconfig:

 vmware-modconfig --icon="vmware-workstation"

If you get error "Application name must be set" then you can fix that by adding the parameter to set that:

 vmware-modconfig --appname="VMware Workstation"

If there are still problems then vmware-modconfig tells you where it writes out a log, it helps to read it for example:
  vmware-modconfig  --icon="vmware-workstation"  --appname="VMware Workstation"
  Logging to /root/tmp/vmware-root/modconfig-2221.log

Check that file!
In my case for example it says:
 failed to find /lib/modules/3.12.xx/build/include/linux/version.h

That's because in later versions the version.h file has been moved (smart move!) to another location.
So in order to get past that you have to add a symbolic link (replace)

 # ln -s /usr/src/`uname -r`/include/generated/uapi/linux/version.h /usr/src/`uname -r`/include/linux/version.h

Note that your OS might just have the kernel-devel packages installed and in that case you might have to replace `uname -r` in the above with linux. 
Eg:
 # ln -s /usr/src/linux/include/generated/uapi/linux/version.h /usr/src/linux/include/linux/version.h

====Alternative solution====
Of course there is still a vmware application available that you can use for this as well.
[http://communities.vmware.com/people/birdie Birdie] came up with a smart alternative so you can keep things like they used to be by creating an alias for the modconfig with the correct parameters to run it in the console.
 alias vmware-config.pl='vmware-modconfig --console --install-all'

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>84c38c4b49f70c119a5a43b380e7974f239e0ef5</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Esxcli</title>
  <ns>0</ns>
  <id>569</id>
  <revision>
    <id>1358</id>
    <parentid>1353</parentid>
    <timestamp>2014-06-19T22:41:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Disable the firewall */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="594" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>bd7e2a41dca6a48f389bbef806c622ceea45bbb1</sha1>
  </revision>
  <revision>
    <id>1359</id>
    <parentid>1358</parentid>
    <timestamp>2014-06-22T22:48:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* install a vib file */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1054" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib


=== enable 2GB Sparse disks ===
By default the 2GB Sparse disk format is disabled since -I think- ESXi version 5.x
If you try to import a disk in 2GB disk format you'll get the following error:
 # vmkfstools -i /vmfs/volumes/storage/myVM/myVM.vmdk -d thin myVM.vmdk
 Failed to open '/vmfs/volumes/storage/myVM/myVM.vmdk': The system cannot find the file specified (25).

You can enable the 2GB disk format by using:
 esxcli system module load -m multiextent

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>5ed5c679d41a1b314cb37617bfa3a8de33579239</sha1>
  </revision>
  <revision>
    <id>1360</id>
    <parentid>1359</parentid>
    <timestamp>2014-06-22T22:50:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* enable 2GB Sparse disks */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1141" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib


=== enable 2GB Sparse disks ===
By default the 2GB Sparse disk format is disabled since -I think- ESXi version 5.x
If you try to import a disk in 2GB disk format you'll get the following error:
 # vmkfstools -i /vmfs/volumes/storage/myVM/myVM.vmdk -d thin myVM.vmdk
 Failed to open '/vmfs/volumes/storage/myVM/myVM.vmdk': The system cannot find the file specified (25).

Test if you have sparse format enabled:
 esxcli system module list | grep multiextent

You can enable the 2GB disk format by using:
 esxcli system module load -m multiextent

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>1169b556ab0a48bff2c6727ce344ec139ef2ac5a</sha1>
  </revision>
  <revision>
    <id>1361</id>
    <parentid>1360</parentid>
    <timestamp>2014-06-25T19:28:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* enable 2GB Sparse disks */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1344" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib


=== enable 2GB Sparse disks ===
By default the 2GB Sparse disk format is disabled since -I think- ESXi version 5.x
If you try to import a disk in 2GB disk format you'll get the following error:
 # vmkfstools -i /vmfs/volumes/storage/myVM/myVM.vmdk -d thin myVM.vmdk
 Failed to open '/vmfs/volumes/storage/myVM/myVM.vmdk': The system cannot find the file specified (25).

Test if you have sparse format enabled:
 esxcli system module list | grep multiextent

You can enable the 2GB disk format by using:
 esxcli system module load -m multiextent


=== advanced settings list ===
Remind yourself of your changed system advanced settings by using:
 esxcli system settings advanced list -d

from: https://twitter.com/AtherBeg/status/481743367957934080

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>895404a52da30363de66a452f4970f29b2557daa</sha1>
  </revision>
  <revision>
    <id>1369</id>
    <parentid>1361</parentid>
    <timestamp>2014-08-26T17:40:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* enable 2GB Sparse disks */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1536" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib


=== enable 2GB Sparse disks ===
By default the 2GB Sparse disk format is disabled since -I think- ESXi version 5.x
If you try to import a disk in 2GB disk format you'll get the following error:
 # vmkfstools -i /vmfs/volumes/storage/myVM/myVM.vmdk -d thin myVM.vmdk
 Failed to open '/vmfs/volumes/storage/myVM/myVM.vmdk': The system cannot find the file specified (25).

Test if you have sparse format enabled:
 esxcli system module list | grep multiextent
If sparse format is not enabled you get no output, if it is enabled, the output is like:
  # esxcli system module list | grep multiextent 
 multiextent                         true        true

You can enable the 2GB disk format by using:
 esxcli system module load -m multiextent

=== advanced settings list ===
Remind yourself of your changed system advanced settings by using:
 esxcli system settings advanced list -d

from: https://twitter.com/AtherBeg/status/481743367957934080

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>d407e75eecccd70e44030ccaf1ebd875d0199b18</sha1>
  </revision>
  <revision>
    <id>1370</id>
    <parentid>1369</parentid>
    <timestamp>2014-08-26T17:40:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* enable 2GB Sparse disks */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1538" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib


=== enable 2GB Sparse disks ===
By default the 2GB Sparse disk format is disabled since ESXi version 5.1 and higher.
If you try to import a disk in 2GB disk format you'll get the following error:
 # vmkfstools -i /vmfs/volumes/storage/myVM/myVM.vmdk -d thin myVM.vmdk
 Failed to open '/vmfs/volumes/storage/myVM/myVM.vmdk': The system cannot find the file specified (25).

Test if you have sparse format enabled:
 esxcli system module list | grep multiextent
If sparse format is not enabled you get no output, if it is enabled, the output is like:
  # esxcli system module list | grep multiextent 
 multiextent                         true        true

You can enable the 2GB disk format by using:
 esxcli system module load -m multiextent

=== advanced settings list ===
Remind yourself of your changed system advanced settings by using:
 esxcli system settings advanced list -d

from: https://twitter.com/AtherBeg/status/481743367957934080

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>adc3524b50d3de358d6e7e2c5555ec36b893a719</sha1>
  </revision>
  <revision>
    <id>1383</id>
    <parentid>1370</parentid>
    <timestamp>2015-02-26T17:09:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* advanced settings list */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2079" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib


=== enable 2GB Sparse disks ===
By default the 2GB Sparse disk format is disabled since ESXi version 5.1 and higher.
If you try to import a disk in 2GB disk format you'll get the following error:
 # vmkfstools -i /vmfs/volumes/storage/myVM/myVM.vmdk -d thin myVM.vmdk
 Failed to open '/vmfs/volumes/storage/myVM/myVM.vmdk': The system cannot find the file specified (25).

Test if you have sparse format enabled:
 esxcli system module list | grep multiextent
If sparse format is not enabled you get no output, if it is enabled, the output is like:
  # esxcli system module list | grep multiextent 
 multiextent                         true        true

You can enable the 2GB disk format by using:
 esxcli system module load -m multiextent

=== advanced settings list ===
Remind yourself of your changed system advanced settings by using:
 esxcli system settings advanced list -d

from: https://twitter.com/AtherBeg/status/481743367957934080

=== Getting UUID ===

There are two main UUID’s in ESXi, well technically more but let’s just stick to these two :) System and Hardware UUID

from: https://twitter.com/lamw/status/570971985871654913

==== System UUID ====
UUID shown in esxcfg-info &amp; esx.conf is the "System” UUID

You can easily get ESXi “System” UUID via
 esxcli system uuid get

==== Hardware UUID ====
UUID shown from vSphere API including PowerCLI is showing the "Hardware" UUID

You can easily get ESXi “Hardware” UUID via 
 esxcli hardware platform get

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>5bf94238dc914e3492ce9128083dae350af17c63</sha1>
  </revision>
  <revision>
    <id>1384</id>
    <parentid>1383</parentid>
    <timestamp>2015-03-15T18:38:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Hardware UUID */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2326" xml:space="preserve">

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib


=== enable 2GB Sparse disks ===
By default the 2GB Sparse disk format is disabled since ESXi version 5.1 and higher.
If you try to import a disk in 2GB disk format you'll get the following error:
 # vmkfstools -i /vmfs/volumes/storage/myVM/myVM.vmdk -d thin myVM.vmdk
 Failed to open '/vmfs/volumes/storage/myVM/myVM.vmdk': The system cannot find the file specified (25).

Test if you have sparse format enabled:
 esxcli system module list | grep multiextent
If sparse format is not enabled you get no output, if it is enabled, the output is like:
  # esxcli system module list | grep multiextent 
 multiextent                         true        true

You can enable the 2GB disk format by using:
 esxcli system module load -m multiextent

=== advanced settings list ===
Remind yourself of your changed system advanced settings by using:
 esxcli system settings advanced list -d

from: https://twitter.com/AtherBeg/status/481743367957934080

=== Getting UUID ===

There are two main UUID’s in ESXi, well technically more but let’s just stick to these two :) System and Hardware UUID

from: https://twitter.com/lamw/status/570971985871654913

==== System UUID ====
UUID shown in esxcfg-info &amp; esx.conf is the "System” UUID

You can easily get ESXi “System” UUID via
 esxcli system uuid get

==== Hardware UUID ====
UUID shown from vSphere API including PowerCLI is showing the "Hardware" UUID

You can easily get ESXi “Hardware” UUID via 
 esxcli hardware platform get

==== setup 64-Node VSAN 6.0 Cluster ====

If you want to setup 64-Node VSAN 6.0 Cluster, make sure to run following &amp; reboot: 

 esxcli system settings advanced set -o /VSAN/goto11 -i 1

source: https://twitter.com/lamw/status/568095961156689920

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>fe38338ab50d3bcaea63a3db5a93638e5049279e</sha1>
  </revision>
  <revision>
    <id>1386</id>
    <parentid>1384</parentid>
    <timestamp>2015-04-07T09:37:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2459" xml:space="preserve">
[http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.dcli.cmdref.doc%2Fintro.html vSphere 6.0 official esxcli reference]

=== Disable the firewall ===
Disable the firewall completely.

 esxcli network firewall set --enabled false

=== Install a patch bundle ===

 esxcli software vib install -d /vmfs/volumes/yourvolumename/patch/patch.zip


=== install a vib file ===

 esxcli software vib install -v /vmfs/volumes/yourvolumename/patch/patch.vib


=== enable 2GB Sparse disks ===
By default the 2GB Sparse disk format is disabled since ESXi version 5.1 and higher.
If you try to import a disk in 2GB disk format you'll get the following error:
 # vmkfstools -i /vmfs/volumes/storage/myVM/myVM.vmdk -d thin myVM.vmdk
 Failed to open '/vmfs/volumes/storage/myVM/myVM.vmdk': The system cannot find the file specified (25).

Test if you have sparse format enabled:
 esxcli system module list | grep multiextent
If sparse format is not enabled you get no output, if it is enabled, the output is like:
  # esxcli system module list | grep multiextent 
 multiextent                         true        true

You can enable the 2GB disk format by using:
 esxcli system module load -m multiextent

=== advanced settings list ===
Remind yourself of your changed system advanced settings by using:
 esxcli system settings advanced list -d

from: https://twitter.com/AtherBeg/status/481743367957934080

=== Getting UUID ===

There are two main UUID’s in ESXi, well technically more but let’s just stick to these two :) System and Hardware UUID

from: https://twitter.com/lamw/status/570971985871654913

==== System UUID ====
UUID shown in esxcfg-info &amp; esx.conf is the "System” UUID

You can easily get ESXi “System” UUID via
 esxcli system uuid get

==== Hardware UUID ====
UUID shown from vSphere API including PowerCLI is showing the "Hardware" UUID

You can easily get ESXi “Hardware” UUID via 
 esxcli hardware platform get

==== setup 64-Node VSAN 6.0 Cluster ====

If you want to setup 64-Node VSAN 6.0 Cluster, make sure to run following &amp; reboot: 

 esxcli system settings advanced set -o /VSAN/goto11 -i 1

source: https://twitter.com/lamw/status/568095961156689920

=== resources ===

VMware Front Experience:

[http://www.v-front.de/2013/01/how-to-write-your-own-esxcli-plugin.html How to write your own esxcli plugin]

[http://www.v-front.de/2013/01/release-esxcli-plugin-to-run-arbitrary.html esxcli plugin to run shell commands]</text>
    <sha1>ab28dbc95ffbe11958295b153a67848ae072bde7</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Dmidecode</title>
  <ns>0</ns>
  <id>459</id>
  <revision>
    <id>1362</id>
    <parentid>996</parentid>
    <timestamp>2014-07-14T12:57:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8915" xml:space="preserve">from the man command: 

Reformatting dmidecode(8), please wait...
DMIDECODE(8)                                                      DMIDECODE(8)

==== NAME ====
       dmidecode - DMI table decoder

Note: In vSphere 5.x this command no longer exists and you have to use
       smbiosDump
instead.

==== SYNOPSIS ====
       dmidecode [OPTIONS]

==== DESCRIPTION ====
dmidecode  is a tool for dumping a computerâs DMI (some say SMBIOS) table contents in a human-readable format. This table contains a description  of  the  systemâs  hardware  components,  as well as other useful pieces of information such as serial numbers and BIOS revision.  Thanks to  this  table,  you  can  retrieve this information without having to probe for the actual hardware.  While this is a good point in terms  of report  speed  and  safeness, this also makes the presented information possibly unreliable.

The DMI table doesnât only describe what the system is  currently  made of,  it  also  can  report the possible evolutions (such as the fastest supported CPU or the maximal amount of memory supported).

SMBIOS stands for System Management BIOS, while DMI stands for  Desktop Management  Interface. Both standards are tightly related and developed by the DMTF (Desktop Management Task Force).

As you run it, dmidecode will try to locate the DMI table. If  it  succeeds, it will then parse this table and display a list of records like
this one:

       Handle 0x0002
           DMI type 2, 8 bytes.
           Base Board Information
               Manufacturer: Intel
               Product Name: C440GX+
               Version: 727281-001
               Serial Number: INCY92700942


Each record has:

* A handle. This is a unique identifier, which allows records to reference  each  other.  For  example, processor records usually reference cache memory records using their handles.

* A type. The SMBIOS specification defines different types of  elements a  computer  can  be  made  of. In this example, the type is 2, which means that the record contains "Base Board Information".

* A size. Each record has a 4-byte header (2 for the handle, 1 for  the type,  1  for  the  size),  the rest is used by the record data. This value doesn't take text strings into account (these are placed at the end of the record), so the actual length of the record may be (and is often) greater than the displayed value.

* Decoded values. The information presented of course  depends  on  the type of record. Here, we learn about the boardâs manufacturer, model, version and serial number.

OPTIONS
       -d, --dev-mem FILE
              Read memory from device FILE (default: /dev/mem)

       -q, --quiet
              Be less verbose. Unknown, inactive and OEM-specific entries  are
              not displayed. Meta-data and handle references are hidden. Mutuâ
              ally exclusive with --dump.

       -s, --string KEYWORD
              Only display the value of the DMI string identified by  KEYWORD.
              KEYWORD  must be a keyword from the following list: bios-vendor,
              bios-version,  bios-release-date,  system-manufacturer,  system-
              product-name,  system-version,  system-serial-number, baseboard-
              manufacturer, baseboard-product-name,  baseboard-version,  baseâ
              board-serial-number,  baseboard-asset-tag, chassis-manufacturer,
              chassis-version, chassis-serial-number, chassis-asset-tag,  proâ
              cessor-manufacturer,  processor-version.   Each  keyword  correâ
              sponds to a given DMI type and a given offset within this  entry
              type.   Not all strings may be meaningful or even defined on all
              systems. Some keywords may return more than one result  on  some
              systems  (e.g.   processor-version on a multi-processor system).
              If KEYWORD is not provided or not valid, a  list  of  all  valid
              keywords  is  printed  and  dmidecode exits with an error.  This
              option cannot be used  more  than  once,  and  implies  --quiet.
              Mutually exclusive with --type and --dump.

       -t, --type TYPE
              Only  display the entries of type TYPE. TYPE can be either a DMI
              type number, or a comma-separated list of  type  numbers,  or  a
              keyword  from the following list: bios, system, baseboard, chasâ
              sis, processor, memory, cache, connector, slot. Refer to the DMI
              TYPES  section  below  for details.  If this option is used more
              than once, the set of displayed entries will be the union of all
              the  given  types.  If TYPE is not provided or not valid, a list
              of all valid keywords is printed and  dmidecode  exits  with  an
              error.  Mutually exclusive with --string.

       -u, --dump
              Do  not  decode  the entries, dump their contents as hexadecimal
              instead.  Note that this is still a text output, no binary  data
              will  be thrown upon you. The strings attached to each entry are
              displayed as both hexadecimal and ASCII. This option  is  mainly
              useful  for  debugging.   Mutually  exclusive  with  --quiet and
              --string.

       -h, --help
              Display usage information and exit

       -V, --version
              Display the version and exit

DMI TYPES
       The SMBIOS specification defines the following DMI types:

       Type   Information
       ----------------------------------------
          0   BIOS
          1   System
          2   Base Board
          3   Chassis
          4   Processor
          5   Memory Controller
          6   Memory Module
          7   Cache
          8   Port Connector
          9   System Slots
         10   On Board Devices
         11   OEM Strings
         12   System Configuration Options
         13   BIOS Language
         14   Group Associations
         15   System Event Log
         16   Physical Memory Array
         17   Memory Device
         18   32-bit Memory Error
         19   Memory Array Mapped Address
         20   Memory Device Mapped Address
         21   Built-in Pointing Device
         22   Portable Battery
         23   System Reset
         24   Hardware Security
         25   System Power Controls
         26   Voltage Probe
         27   Cooling Device
         28   Temperature Probe
         29   Electrical Current Probe
         30   Out-of-band Remote Access
         31   Boot Integrity Services
         32   System Boot
         33   64-bit Memory Error
         34   Management Device
         35   Management Device Component
         36   Management Device Threshold Data
         37   Memory Channel
         38   IPMI Device
         39   Power Supply

       Additionally, type 126 is used for disabled entries,  type  127  is  an
       end-of-table  marker,  and  types 128 to 255 are for OEM-specific data.
       dmidecode will display these entries  by  default,  but  cannot  decode
       them.

       Keywords can be used instead of type numbers with --type.  Each keyword
       is equivalent to a list of type numbers:

       Keyword     Types
       ------------------------------
       bios        0, 13
       system      1, 12, 15, 23, 32
       baseboard   2, 10
       chassis     3
       processor   4
       memory      5, 6, 16, 17
       cache       7
       connector   8
       slot        9

       Keywords are matched case-insensitively. The  following  command  lines
       are equivalent:

* dmidecode --type 0 --type 13

* dmidecode --type 0,13

* dmidecode --type 0 --type 13

* dmidecode --type 0,13

* dmidecode --type bios

* dmidecode --type BIOS

FILES
       /dev/mem

BUGS
       More often than not, information contained in the DMI tables is inaccuâ
       rate, incomplete or simply wrong.

AUTHORS
       Alan Cox, Jean Delvare

SEE ALSO
       biosdecode(8), mem(4), ownership(8), vpddecode(8)

dmidecode                         August 2005                     DMIDECODE(8)


==== Example output ====

Here's a snippet of output on an ESX host when displaying memory info:

 Handle 0x0028
        DMI type 17, 27 bytes.
        Memory Device
                Array Handle: 0x0025
                Error Information Handle: No Error
                Total Width: 76 bits
                Data Width: 72 bits
                Size: 1024 MB
                Form Factor: DIMM
                Set: 1
                Locator: DIMM 2A
                Bank Locator: Bank0 Bank1
                Type: DDR
                Type Detail: Synchronous
                Speed: 266 MHz (3.8 ns)
                Manufacturer: Not Specified
                Serial Number: Not Specified
                Asset Tag: Not Specified
                Part Number: Not Specified

[[Category: CLI]]</text>
    <sha1>9e243e7fdb6f45f6237157945fba09832b0932dc</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Build ESX drivers</title>
  <ns>0</ns>
  <id>421</id>
  <revision>
    <id>1363</id>
    <parentid>821</parentid>
    <timestamp>2014-08-06T16:08:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1664" xml:space="preserve">[http://communities.vmware.com/people/nick.couchman Nick Couchman] has started a topic on how-to build your own ESX/ESXi drivers using linux sources and the freely GPL code from VMware and he has been successful in doing so.

==== Required components ====
In order to do this you need to get yourself the following components:
* The code of the module that you want to add support for
* CentOS 3.9 in a virtual machine build environment is going to be the easiest way to get going, you can use the [http://isoredirect.centos.org/centos/3/isos/i386/ latest update] from the [http://www.centos.org centOS] web site.
* The [http://www.vmware.com/download/vi/open_source.html GPL components] from ESX. Here's a link to the [http://download3.vmware.com/software/vi/VMware-esx-public-source-3.5.0-123630.tar.gz ESX3.5 Update 3] sources.
 

''' Beware that VMware will NOT support your configuration with home-grown drivers '''


==== External links ====
* The communities thread [http://communities.vmware.com/thread/188244 GPL Components - build ESX Drivers?]
* The project at sourceforge [https://sourceforge.net/projects/open-vdrivers/ open-vdrivers]


At the time of writing this, the project has not released any sources, yet, but it has these entries on the wiki:

[http://open-vdrivers.wiki.sourceforge.net/intro Wiki - Intro]

[http://open-vdrivers.wiki.sourceforge.net/Getting_Started Wiki - Getting started]

[http://blogs.emulex.com/implementers/2014/07/29/native-mode-driver-vmware-vsphere-esxi-55/ Emulex.com blog article about native mode drivers for vSphere ESXi 5.5]

[[Category: ESX]] [[Category: ESXi]] [[Category: Hypervisor]] [[Category: VMware OSS]]</text>
    <sha1>42f1dc4fe5c22b06bb6e5dfe245a9eda591e8c0f</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>1364</id>
    <parentid>1213</parentid>
    <timestamp>2014-08-18T15:36:14Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* VMware Developer targeted sites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2229" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://twitter.com/PowerCLITip @PowerCLITip] Learn #PowerCLI one tweet at a time by following updates from @PowerCLITip #VMware #PowerShell

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>2aef1f7a9332185fd13eec2d22a1024cff756f74</sha1>
  </revision>
  <revision>
    <id>1385</id>
    <parentid>1364</parentid>
    <timestamp>2015-03-31T15:38:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* VMware Developer targeted sites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2303" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://twitter.com/PowerCLITip @PowerCLITip] Learn #PowerCLI one tweet at a time by following updates from @PowerCLITip #VMware #PowerShell

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>9dd5d5346d2748bd67bb7a358ffd64908a28118e</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Vmkfstools</title>
  <ns>0</ns>
  <id>572</id>
  <revision>
    <id>1365</id>
    <timestamp>2014-08-23T15:48:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "Command for directly working with the virtual disk at host level.  With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BAC..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3794" xml:space="preserve">Command for directly working with the virtual disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
 OPTIONS FOR FILE SYSTEMS:
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
 OPTIONS FOR VIRTUAL DISKS:
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
 OPTIONS FOR DEVICES:
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help

=== Usage ===
=== Options ===
=== Examples ===
Export a VM disk in 2GB chunks, note that since ESXi 5.x the 2GB sparse driver is disabled.
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk


 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.


dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

 vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86


=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>020d50233e5ac937b655da7d0e339e06b145ba90</sha1>
  </revision>
  <revision>
    <id>1366</id>
    <parentid>1365</parentid>
    <timestamp>2014-08-23T15:51:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4025" xml:space="preserve">Command for directly working with the virtual disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
Export a VM disk in 2GB chunks, note that since ESXi 5.x the 2GB sparse driver is disabled.
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk


 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.


dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

 vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86


=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>dd84f06622aaa0ad186f8d42c2bb2a43355446ef</sha1>
  </revision>
  <revision>
    <id>1367</id>
    <parentid>1366</parentid>
    <timestamp>2014-08-23T15:58:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4424" xml:space="preserve">Command for directly working with the (virtual) disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks. 
Beware that if you are working with a virtual disk that in most cases the virtual machine itself should be shut down.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
Export a VM disk in 2GB chunks, note that since ESXi 5.x the 2GB sparse driver is disabled.
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk

 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.


dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 # vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

Example:
 # vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86

Reclaim disk space by returning unused blocks of data in the virtual disk to the host OS. This will only work if your virtual disk is of type thin.

Example:
 # vmkfstools --punchzero myvm.vmdk
 vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 
 Hole Punching: 3% done.


=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>d8f9163341c3221ad07d86b070cb4b6cff1c1e90</sha1>
  </revision>
  <revision>
    <id>1368</id>
    <parentid>1367</parentid>
    <timestamp>2014-08-26T17:38:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Examples */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4423" xml:space="preserve">Command for directly working with the (virtual) disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks. 
Beware that if you are working with a virtual disk that in most cases the virtual machine itself should be shut down.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
Export a VM disk in 2GB chunks, note that since ESXi 5.1+ the 2GB sparse driver is disabled.
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk

 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.


dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 # vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

Example:
 # vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86

Reclaim disk space by returning unused blocks of data in the virtual disk to the host OS. This will only work if your virtual disk is of type thin.

Example:
 # vmkfstools --punchzero myvm.vmdk
 vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 
 Hole Punching: 3% done.

=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>c2c9e2d9f21cd94d283b567fe919dc3075fe8274</sha1>
  </revision>
  <revision>
    <id>1371</id>
    <parentid>1368</parentid>
    <timestamp>2014-08-26T17:42:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Examples */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4458" xml:space="preserve">Command for directly working with the (virtual) disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks. 
Beware that if you are working with a virtual disk that in most cases the virtual machine itself should be shut down.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
Export a VM disk in 2GB chunks, note that since [[Esxcli#enable_2GB_Sparse_disks|ESXi 5.1+ the 2GB sparse driver is disabled]].
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk

 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.


dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 # vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

Example:
 # vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86

Reclaim disk space by returning unused blocks of data in the virtual disk to the host OS. This will only work if your virtual disk is of type thin.

Example:
 # vmkfstools --punchzero myvm.vmdk
 vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 
 Hole Punching: 3% done.

=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>bf6513b293ea34cb9a481a82294649f148e81a93</sha1>
  </revision>
  <revision>
    <id>1372</id>
    <parentid>1371</parentid>
    <timestamp>2014-11-27T21:15:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Examples */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5820" xml:space="preserve">Command for directly working with the (virtual) disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks. 
Beware that if you are working with a virtual disk that in most cases the virtual machine itself should be shut down.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
==== Export a VM disk ====
Export a VM disk in 2GB chunks, note that since [[Esxcli#enable_2GB_Sparse_disks|ESXi 5.1+ the 2GB sparse driver is disabled]].
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk

==== Check or repair a disk ====
 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

==== Set a UUID ====
 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.

==== dumpfs ====
dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 # vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
==== activehosts ==== 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

Example:
 # vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86
==== punchzero ====
Since vSphere 5.1 there's an option to shrink disks besides the normally required storage vmotion.

With the guest shut down you can run vmkfstools with the punchzero option. 

Reclaim disk space by returning unused blocks of data in the virtual disk to the host OS. 
Note that this will only work if your virtual disk is of type thin.
You will also need to zero out the unused blocks of data in the guest OS.

For a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].
Run it as
 sdelete -z c:
Note that the -z option is needed as of sdelete version 1.6

For a linux based VM, run a command like:
 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill
to zero out the unused space. 
Note of warning that you should stop database -and other disk intensive- services before running the above.


Example:
 # vmkfstools --punchzero disk.vmdk
 vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 
 Hole Punching: 3% done.


After you're done and list the VM from within the console, it looks like nothing has changed, in this example the disk is 10GB in size.
 # ls -lh *.vmdk
 -rw-------    1 root     root       10.0G Nov 27 20:58 disk-flat.vmdk
 -rw-------    1 root     root         527 Nov 27 21:02 disk.vmdk

If you use the command du however then you can see the difference:
 # du -hs *.vmdk
 4.3G    disk-flat.vmdk
 0       disk.vmdk

You can also use the vSphere Client data browser to see the effect of reclaiming disk space

=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>7394aa58fbb30af4c72138013a25e5d672f0f681</sha1>
  </revision>
  <revision>
    <id>1406</id>
    <parentid>1372</parentid>
    <timestamp>2016-08-24T12:17:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* punchzero */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6497" xml:space="preserve">Command for directly working with the (virtual) disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks. 
Beware that if you are working with a virtual disk that in most cases the virtual machine itself should be shut down.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
==== Export a VM disk ====
Export a VM disk in 2GB chunks, note that since [[Esxcli#enable_2GB_Sparse_disks|ESXi 5.1+ the 2GB sparse driver is disabled]].
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk

==== Check or repair a disk ====
 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

==== Set a UUID ====
 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.

==== dumpfs ====
dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 # vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
==== activehosts ==== 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

Example:
 # vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86
==== punchzero ====
Since vSphere 5.1 there's an option to shrink disks besides the normally required storage vmotion.

With the guest shut down you can run vmkfstools with the punchzero option. 

Reclaim disk space by returning unused blocks of data in the virtual disk to the host OS. 

Note that this will only work if your virtual disk is of type thin.

Before running it you will also need to zero out the unused blocks of data in the guest OS.

For a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].
Run it as
 sdelete -z c:
Note that the -z option is needed as of sdelete version 1.6

For a linux based VM, run a command like:
 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill
to zero out the unused space. 

Note of warning that you should stop database -and other disk intensive- services before running the above.


Example:
 # vmkfstools --punchzero disk.vmdk
 vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 
 Hole Punching: 3% done.


After you're done and list the VM from within the console, it looks like nothing has changed, in this example the disk is 10GB in size.
 # ls -lh *.vmdk
 -rw-------    1 root     root       10.0G Nov 27 20:58 disk-flat.vmdk
 -rw-------    1 root     root         527 Nov 27 21:02 disk.vmdk

If you use the command du however then you can see the difference:
 # du -hs *.vmdk
 4.3G    disk-flat.vmdk
 0       disk.vmdk

You can also use the vSphere Client data browser to see the effect of reclaiming disk space.

If you try to run this command against a VM living on NFS storage you might end up seeing the following error:
 vmkfstools --punchzero myvmdk.vmdk
 Not a supported filesystem type

The error is a bit confusing as you might expect vmkfstools to talk about the guest OS here, but it is actually reporting that NFS does not support the punchzero option. 

Your solution is to either move the vmdk by hand to storage not located on VMFS or use storage vmotion to migrate to non NFS storage. On moving using storage vmotion, the zero data is already being discarded. So you can just storage vmotion back afterwards and you have reclaimed the lost disk space.

=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>194e68e505e70a28cb40a0bc5565c7620ef6e171</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Scripts</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>1373</id>
    <parentid>1343</parentid>
    <timestamp>2014-12-05T18:05:42Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* bash scripts */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3098" xml:space="preserve">==== Documentation ====

===== ESX Service Console =====
[[RTFM ESX 3.x Service Console Guide]]

[http://download3.vmware.com/vmworld/2006/tac9685.pdf Command Line Interface Tips and Tricks for VMware ESX Server 2 and 3]

[http://www.vmreference.com/vi3-card/ VI3 reference card]

[[ESX CLI Commands]]

[[esxcli]]

===== VMware API =====
[http://www.vmware.com/support/developer/scripting-API/API-2.3-Release-Notes.html VMware ESX 2.3 scripting API users manual]

===== VMware vimsh =====
[http://knowledge.xtravirt.com/white-papers/scripting.html Xtravirt scripting papers about vimsh among others]

[[Vimsh]] Help documentation and general tips

===== VMware RCLI =====

What is VMware [[RCLI]]?&lt;br&gt;
The VMware Infrastructure Remote CLI provides a command-line interface for datacenter management from a remote server. This interface is fully supported on ESX 3.5 Update 2 and ESXi Update 2. Download it [http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2 here]

[[ESX3i Remote CLI documentation]]

===== VMware VI Perl Toolkit =====

[http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/perl_toolkit_utilities_idx.html VI Perl Toolkit command documentation]

===== VMware VIMA =====

What is VMware VIMA?
http://www.vmware.com/support/developer/vima/

Why use VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340611,00.html

How to setup VMware VIMA? http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1340917,00.html#

===== VIX/vmrun =====
Using vmrun one can automate ESX3.5/ESXi virtual machines as well as virtual machines on VMware Server 2.0 and VMware Worstation 6.0

What is VMware VIX and why use it? http://blogs.vmware.com/vix/2008/07/what-is-vix-and.html

What is VMware vmrun? http://blogs.vmware.com/vix/2008/12/managing-vm-guests-using-vmrun.html 

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun command documentation]


== '''Scripts:''' ==

==== vmrun scripts ====

Scripts to execute to automate actions in your guest.

[[vmrun batch file execution]]

[[vmrun return all IPs for running VMs]]


==== bash scripts ====

[[build host vmware kernel modules]]

[[build guest vmware kernel modules]]

[[Linked Clones for ESX 3.x+]]

[[Linked Clones for ESXi]]

[[Custom my-vmware-cmd management script]]

[[locate all VMs with NPIV WWN for ESX]]

[[locate all VMs with NPIV WWN for ESXi]]

[[locate all VMs with RDMs for ESX and ESXi]]

[[Free VM backup solution for ESX and ESXi]]

[[Performing emergency shut down of VM's on ESX]]

==== RCLI &amp; VI Perl Toolkit scripts ====

[[Free VM Clone utility for ESX and ESXi]]

[["Quick" migration utility for VM(s) on ESX and ESXi]]

[[VMware Health Check Report]]

[[APC/APCUPSD ESX/ESXi Host shutdown script]]

==== Perl scripts ====
[[Recover vmx from log file]]

==== AppleScript ====

[http://communities.vmware.com/thread/122793 AppleScript to Run Virtual Machine and switch to Full Screen View or Unity View at Login]

==== Javascript ====
[[Ghetto vCenter 4.0 Unattended Installer]]

==== In the pipeline ====
[[External scripts that are not processed yet]]</text>
    <sha1>fe56a41d5794e8f514e530b20f426c3ac0ad40cb</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Build guest vmware kernel modules</title>
  <ns>0</ns>
  <id>573</id>
  <revision>
    <id>1374</id>
    <timestamp>2014-12-05T18:23:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "====Pre built modules are sometimes not enough==== When you select "install VMware Tools" then your VMware product will try to install the available vmware modules. If you run..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2028" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
    sudo apt-get install build-essential linux-headers-`uname -r`  
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.
====Preconditions for the script to work====

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>c89f7114ef80e5d25a73bc644bd7a26ff31de17e</sha1>
  </revision>
  <revision>
    <id>1375</id>
    <parentid>1374</parentid>
    <timestamp>2014-12-05T19:23:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* The solution */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2345" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
    sudo apt-get install build-essential linux-headers-`uname -r`  
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>c84db3763c55e26e8b618f0884a43a3dcfc63c1c</sha1>
  </revision>
  <revision>
    <id>1376</id>
    <parentid>1375</parentid>
    <timestamp>2014-12-05T19:25:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Preconditions for the script to work */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2615" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
    sudo apt-get install build-essential linux-headers-`uname -r`  
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>5008d3d280c1d3a1a6d8b102beb0e119fd449e6e</sha1>
  </revision>
  <revision>
    <id>1377</id>
    <parentid>1376</parentid>
    <timestamp>2014-12-05T19:26:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* The solution */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2620" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>6a93e2089a32b72d7f3b97377efe3ea77e551720</sha1>
  </revision>
  <revision>
    <id>1378</id>
    <parentid>1377</parentid>
    <timestamp>2014-12-05T19:34:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3128" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently being installed:
* vmci - inter-VM and host interface
* vmhgfs - shared folders
* vsock - 
* vmxnet3 - virtual network adapter
* pvscsi - paravirtual scsi
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* /usr/bin/vmware-toolbox-cmd
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>819f7cc0569868b15c654d7177aa6704378fd033</sha1>
  </revision>
  <revision>
    <id>1379</id>
    <parentid>1378</parentid>
    <timestamp>2014-12-05T20:13:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3473" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently available:
* vmhgfs - shared folders
* vmxnet3 - virtual network adapter
* vmw_balloon - balloon memory driver
* vmw_pvscsi - paravirtual scsi
* vmwgfx - accelerated graphics
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* vgauth - Guest Authentication
* vmw_vmci - inter-VM and host interface
* vmw_vsock_vmci_transport - 
* vsock - virtual sockets

There's also a number of additional commands/scripts to enable other features
* /usr/bin/vmware-toolbox-cmd - shrink, upgrade, statistics, version, timesync, run scripts on power operations, power operations, control devices
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>4628f7cb81bca132f3d6a72a7f1bf2b764280d6b</sha1>
  </revision>
  <revision>
    <id>1380</id>
    <parentid>1379</parentid>
    <timestamp>2014-12-05T22:07:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3830" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently available:
* vmhgfs - shared folders
* vmxnet3 - virtual network adapter
* vmmemctl - memory
* vmw_balloon - balloon memory driver
* vmw_pvscsi - paravirtual scsi
* vmwgfx - accelerated graphics
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* vmsync -
* vgauth - Guest Authentication
* vmw_vmci - inter-VM and host interface
* vmw_vsock_vmci_transport - 
* vsock - virtual sockets

There's also a number of additional commands/scripts to enable other features
* /usr/bin/vmware-toolbox-cmd - shrink, upgrade, statistics, version, timesync, run scripts on power operations, power operations, control devices
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste. Running this will start the vmtoolsd daemon in /usr/lib/vmware-tools/sbin64
* /usr/lib/vmware-tools/sbin64/vmware-checkvm - prints VMware software version
* /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader 
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>1a1acf6d730d427aa4ca82e233a2722c2e625fd8</sha1>
  </revision>
  <revision>
    <id>1381</id>
    <parentid>1380</parentid>
    <timestamp>2014-12-05T22:23:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3899" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently available:
* vmhgfs - shared folders
* vmxnet3 - virtual network adapter
* vmmemctl - memory
* vmw_balloon - balloon memory driver
* vmw_pvscsi - paravirtual scsi
* vmwgfx - accelerated graphics
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* vmsync -
* vgauth - Guest Authentication
* vmw_vmci - inter-VM and host interface
* vmw_vsock_vmci_transport - 
* vsock - virtual sockets

There's also a number of additional commands/scripts to enable other features
* /usr/bin/vmware-toolbox-cmd - shrink, upgrade, statistics, version, timesync, run scripts on power operations, power operations, control devices
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste. Running this will start the vmtoolsd daemon in /usr/lib/vmware-tools/sbin64
* /usr/lib/vmware-tools/sbin64/vmware-checkvm - prints VMware software version
* /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader option --install-all will actually build all of your modules as well.
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>2af88ade69ec83df4c42d107c0361d6163b84750</sha1>
  </revision>
  <revision>
    <id>1382</id>
    <parentid>1381</parentid>
    <timestamp>2014-12-10T10:41:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4150" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently available:
* vmhgfs - shared folders
* vmxnet3 - virtual network adapter
* vmmemctl - memory
* vmw_balloon - balloon memory driver
* vmw_pvscsi - paravirtual scsi
* vmwgfx - accelerated graphics
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* vmsync -
* vgauth - Guest Authentication
* vmw_vmci - inter-VM and host interface
* vmw_vsock_vmci_transport - 
* vsock - virtual sockets

Interesting tidbit, the reason that there's a "vmw_" prefix means it is VMware only and if there's no prefix, like vsock, then it is because it is a hypervisor-independent interface. See [https://communities.vmware.com/thread/497086 (1)] for details

There's also a number of additional commands/scripts to enable other features
* /usr/bin/vmware-toolbox-cmd - shrink, upgrade, statistics, version, timesync, run scripts on power operations, power operations, control devices
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste. Running this will start the vmtoolsd daemon in /usr/lib/vmware-tools/sbin64
* /usr/lib/vmware-tools/sbin64/vmware-checkvm - prints VMware software version
* /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader option --install-all will actually build all of your modules as well.
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>cc04e7e87d7c7eee1f8058b31a32c14d935abed5</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Vmware-vim-cmd</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>1387</id>
    <parentid>951</parentid>
    <timestamp>2015-04-11T18:03:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Vmware-vim-cmd */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="874" xml:space="preserve">==== Vmware-vim-cmd ====

The command line version of the [[vimsh]] command.
This can be used in your scripts and replaces the alternative 
 vimsh -n -e &lt;command&gt;

so now you can use:
 vmware-vim-cmd &lt;command&gt;
or nowadays use the shorter:
 vim-cmd &lt;command&gt;

 Usage: /usr/lib/vmware/hostd/vmware-vim-cmd [options]... command [cmd_arg1] [cmd_arg2] ...
 
 Options:
   -h           Display this help message and exit
   -v           Display version information and exit
   -H &lt;host&gt;    Host name to connect
   -O &lt;port&gt;    Port number to connect
   -U &lt;user&gt;    User name to use for login
   -P &lt;pass&gt;    Password to use for login
   -d &lt;level&gt;   Show verbose debug output. (info, verbose, trivia)

Use the help command to get information on the commands available.

   /usr/lib/vmware/hostd/vmware-vim-cmd help [command]


[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>b2fc22c1f8bfde48c4d8e1d4c20dd1e26f3220a3</sha1>
  </revision>
  <revision>
    <id>1388</id>
    <parentid>1387</parentid>
    <timestamp>2015-04-11T18:05:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="968" xml:space="preserve">==== Vmware-vim-cmd ====

The command line version of the [[vimsh]] command.
This can be used in your scripts and replaces the alternative 
 vimsh -n -e &lt;command&gt;

so now you can use:
 vmware-vim-cmd &lt;command&gt;
or nowadays use the shorter:
 vim-cmd &lt;command&gt;

 Usage: vmware-vim-cmd [options]... command [cmd_arg1] [cmd_arg2] ...
 
 Options:
   -h           Display this help message and exit
   -v           Display version information and exit
   -H &lt;host&gt;    Host name to connect
   -O &lt;port&gt;    Port number to connect
   -U &lt;user&gt;    User name to use for login
   -P &lt;pass&gt;    Password to use for login
   -d &lt;level&gt;   Show verbose debug output. (info, verbose, trivia)

Use the help command to get information on the commands available.

   vmware-vim-cmd help [command]

Possible locations of the binary are:
(legacy)
 /usr/lib/vmware/hostd/vmware-vim-cmd 
(current)
 /usr/bin/vmware-vim-cmd
 /usr/bin/vim-cmd
[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>cce9eba52d40b3c7556530896d9d9ce71c27f854</sha1>
  </revision>
  <revision>
    <id>1389</id>
    <parentid>1388</parentid>
    <timestamp>2015-04-11T18:05:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="964" xml:space="preserve">==== Vmware-vim-cmd ====

The command line version of the [[vimsh]] command.
This can be used in your scripts and replaces the alternative 
 vimsh -n -e &lt;command&gt;

so now you can use:
 vmware-vim-cmd &lt;command&gt;
or nowadays use the shorter:
 vim-cmd &lt;command&gt;

 Usage: vmware-vim-cmd [options]... command [cmd_arg1] [cmd_arg2] ...
 
 Options:
   -h           Display this help message and exit
   -v           Display version information and exit
   -H &lt;host&gt;    Host name to connect
   -O &lt;port&gt;    Port number to connect
   -U &lt;user&gt;    User name to use for login
   -P &lt;pass&gt;    Password to use for login
   -d &lt;level&gt;   Show verbose debug output. (info, verbose, trivia)

Use the help command to get information on the commands available.

   vmware-vim-cmd help [command]

Possible locations of the binary are:
(legacy)
 /usr/lib/vmware/hostd/vmware-vim-cmd 
(current)
 /usr/bin/vmware-vim-cmd
 /bin/vim-cmd
[[Category: ESX]][[Category: SDK]][[Category: Vimsh]]</text>
    <sha1>d12538c5576929fdecfa447b9ec5831e35759d7d</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Recover vmx from log file</title>
  <ns>0</ns>
  <id>414</id>
  <revision>
    <id>1390</id>
    <parentid>781</parentid>
    <timestamp>2015-05-25T21:10:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Update to parse and retrieve vmx file from current vmware.log files.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2667" xml:space="preserve">=== Recover vmx from log file ===
On the VMware community forums, [http://communities.vmware.com/people/etung Eric Tung] has devised a little jewel of code that automates recreating a vmx file from a recent vmware.log file.

This is possible as on every boot of a virtual machine, the vmware.log gets a copy from your virtual hardware settings written out into the vmware.log logfile along with some extra information such as the date and time this VM was run.
The script extracts the relevant part for you and eliminates the risk of making a typo while doing this by hand.
It is written in perl, just a few lines long and shows the true power of what a bit of perl can do for you :)

==== vmxRecover.pl code ====

As of Fusion 4, the format of the vmware.log has changed. Here's the script for parsing log files from before Fusion 4

 #!/usr/bin/perl
 use strict;
 use warnings;  
 
 if ($#ARGV != 0) {
    print "Recovers .vmx files from .log files. Usage:\n";
    print "$0 logfile &gt; vmxfile\n\n";
    exit;
 }
 
 while (&lt;&gt;) {
    # Scan until we reach the config section
    if (/: vmx\| DICT --- CONFIGURATION/) { last; }
 }
 
 while (&lt;&gt;) {
    if (/: vmx\| DICT --- \S/) { last; } # Keep going until the next section
    s/^.*: vmx\| DICT\s*//;    # Strip off the leading timestamp and other stuff
    s/\r//;                    # Get rid of any \r's that may have somehow snuck in
    s/([^=]*=) (.*)/$1 "$2"/;  # Quote the value
    print;
 }

New version to use for vmware.log files starting from Fusion 4:

 #!/usr/bin/perl
 use strict;
 use warnings;
 
 if ($#ARGV != 0) {
    print "Recovers .vmx files from .log files. Usage:\n";
    print "$0 logfile &gt; vmxfile\n\n";
    exit;
 }
 
 while (&lt;&gt;) {
    # Scan until we reach the config section
    if (/: DICT --- CONFIGURATION/) { last; }
 }
 
 while (&lt;&gt;) {
    if (/: DICT --- \S/) { last; } # Keep going until the next section
    s/^.*: DICT\s*//;    # Strip off the leading timestamp and other stuff
    s/\r//;                    # Get rid of any \r's that may have somehow snuck in
    s/([^=]*=) (.*)/$1 "$2"/;  # Quote the value
    print;
 }

==== Usage ====
Say you want to recreate a the virtual hardware configuration for a VMware virtual machine "Windows XP.vmx" then you'd call it like this:
 vmxRecover.pl vmware.log &gt; "Windows XP.vmx"


==== External links ====
* The original post [http://communities.vmware.com/message/1029971#1029971 Not a Valid Virtual Machine Configuration...]
* The script [http://communities.vmware.com/servlet/JiveServlet/download/1029971-12847/vmxRecover.pl.zip?tstart=0&amp;start=15 vmxRecover.pl.zip]
* Eric's site http://www.koiproductions.com

[[Category: Perl]]</text>
    <sha1>7988f1b3a3ef3c29fc89fd017638acd3a4749217</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Projects</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>1391</id>
    <parentid>1308</parentid>
    <timestamp>2015-06-09T17:47:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Artwork */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="741" xml:space="preserve">Below are links to VMware related open source projects, which I've found particularly interesting.

[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[VICL, A VMWare Interface Client for Linux]]

[[psVIC, a powershell Virtual Infrastructure Client]]

[[Unattended ESXi installation]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]

[[Xtravirt Visio action pack]]

[[VMToday Visio stencils]]

[[Darryl Cauldwell VMware vSphere Visio Stencils]]</text>
    <sha1>d3e0900488a4a2bc1c60d288d2b6fca6f98ceb94</sha1>
  </revision>
  <revision>
    <id>1392</id>
    <parentid>1391</parentid>
    <timestamp>2015-06-09T17:50:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Artwork */ oops that was just a link to Maish's stencils</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="689" xml:space="preserve">Below are links to VMware related open source projects, which I've found particularly interesting.

[[iMKS Remote Console]]

[[VMGL]]

[[Vix_Virtuozo_Suite]]

[[Build ESX drivers]]

[[VMI Linux]]

[[libView]]

[[open-vm-tools]]

[[Open Source VMFS Driver]]

[[Protecting ESX VMFS Stores with Automation]]

[[VMware View Open Client]]

[[Parasite, debug your GTK+ applications]]

[[VICL, A VMWare Interface Client for Linux]]

[[psVIC, a powershell Virtual Infrastructure Client]]

[[Unattended ESXi installation]]

==== Artwork ====

[[Veeam VMware visio stencils]]

[[VMguru Visio stencils]]

[[VIOPS VMware Icons and diagrams]]

[[Xtravirt Visio action pack]]

[[VMToday Visio stencils]]</text>
    <sha1>96de9a36072d2bb4b9c33330a92f126db19b87c7</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>VIOPS VMware Icons and diagrams</title>
  <ns>0</ns>
  <id>469</id>
  <revision>
    <id>1393</id>
    <parentid>1204</parentid>
    <timestamp>2015-06-09T17:56:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1067" xml:space="preserve">Visio stencils made from the artwork as released by the official VMware branding team.
Can be used for documentation, now also includes vSphere artwork.


[http://viops.vmware.com/home/docs/DOC-1514  VIOPS: Visio Stencils for vSphere]
and
http://viops.vmware.com/home/docs/DOC-1338

Unfortunately these visio stencils have disappeared, even after asking the VMTN team about this a couple of months ago, they are still gone.

An alternative can be found here: [http://technodrone.blogspot.com/2009/12/my-visio-stencils-again.html Technodrone: My Visio stencils again (2009)] 

Update on Maish's his Visio stencils: [http://technodrone.blogspot.com/2010/12/visio-stencils-happy-holiday-to-you-all.html New vSphere vision stencils (2010)]

To be fair, forget the above links, go directly to this one from Maish as it has all of the above stencils as well [http://technodrone.blogspot.com/2013/04/vmware-visio.html Technodrone VMware visio stencils]

For more alternative visio templates, see the category below for more or search for visio.

[[Category: VMware Artwork]]</text>
    <sha1>587e2b1090de8946925ada51972aca1fe18b939a</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>PowerCLI</title>
  <ns>0</ns>
  <id>524</id>
  <revision>
    <id>1394</id>
    <parentid>1348</parentid>
    <timestamp>2015-06-17T10:29:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Storage */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6359" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]

* [https://www.vmware.com/support/developer/PowerCLI/PowerCLI55R2/html/index.html VMware's PowerCLI 5.5 R2 online cmdlet reference]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====

===== integration =====

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

* [[PowerCLI: WebPowerCLI, run scripts from your browser]]

===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]


==== VM Configuration ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

==== Host Management ====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU's used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

* [[PowerCLI: ESXi 5.0 / ESXi 5.1 Host Backup &amp; Restore GUI Utility]]

===== Integration with ESXi shell =====

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update ESXi Root Password with Password Generator]]

* [[PowerCLI: enable SSH GUI for vSphere clusters]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

* [https://labs.vmware.com/flings/powercli-cmdlet-for-nfs PowerCLI cmdlet for NFS]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>8c533aab065b1e921334b9a19c94340fc741d73f</sha1>
  </revision>
  <revision>
    <id>1404</id>
    <parentid>1394</parentid>
    <timestamp>2015-11-29T20:10:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Host Management */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6361" xml:space="preserve">PowerCLI is the "new' name for what used to be called the Virtual Infrastructure Toolkit, or VI Toolkit in short.
In order to manage your virtual infrastructure on windows using scripts you will most likely want to use the [[VI Toolkit for windows]] and [[PowerShell]]

==== Learning VI-Toolkit Powershell ====

* [[Virtu-Al: Lesson 1 Time Source]]

* [[Virtu-Al: Lesson 2 Service and Firewall Configuration]]

* [[Virtu-Al: Lesson 3 Networking]]

* [[Virtu-Al: Lesson 4 Portgroups]]

* [https://www.vmware.com/support/developer/PowerCLI/PowerCLI55R2/html/index.html VMware's PowerCLI 5.5 R2 online cmdlet reference]

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell -- Frequently Asked Questions]

* [http://communities.vmware.com/message/1381785 PowerCLI Poster with all the available cmdlets]
* [http://blogs.vmware.com/vipowershell/2012/09/powercli-5-1-poster.html PowerCLI 5.1 Poster]

* [http://communities.vmware.com/docs/DOC-12014 Workshop and demo scripts by Carter Shanklin]

* [http://blogs.vmware.com/vipowershell/2010/11/vmworld-2010-powercli-lab-manual-for-your-reading-pleasure-alton-yu.html VMworld 2010 PowerCLI lab manual]

* [http://read.virtualizeplanet.com/?p=138 VirtualizePlanet PowerCLI lessons by Ricky El-Qasem]

* [http://www.petri.co.il/vmware-vsphere-powercli-getting-started.htm Getting Started with vSphere PowerCLI (Petri.co.il)]
===== PowerCLI videos =====

* [[Patching ESX with PowerCLI 4.0 U1]]
* [[Invoke-VM with PowerCLI 4.0 U1]]
* [http://professionalvmware.com/2012/04/vbrownbag-follow-up-powercli-201-w-jake-robinson/ #vBrownBag Follow-Up – PowerCLI 201 w/ Jake Robinson]

==== PowerCLI Oneliners ====
[http://www.peetersonline.nl/index.php/about/ Hugo Peeters] started with posting so called oneliners to indicate how powerful the VI-Toolkit on Powershell is. After a while this got picked up by others as sort of a sport to see if you can do it in one line. Below is a collection of links with oneliners from great powershell scripters. These pages now contains links to oneliners from [http://www.peetersonline.nl/index.php/about/ Hugo Peeters], [http://www.virtu-al.net Alan Renouf], [http://get-admin.com get-admin.com] and [http://ict-freak.nl Arne Fokkema] 

* [[PowerCLI Oneliners: Statistics]]
* [[PowerCLI Oneliners: Events]]
* [[PowerCLI Oneliners: Host Configuration]]
* [[PowerCLI Oneliners: VM Configuration]]
* [[PowerCLI Oneliners: Storage]]
* [http://vwiki.co.uk/ESX_PowerCLI_One-Liners ESX PowerCLI One-Liners (vWiki)]

* [[PowerCLI: Oneliners]]

==== PowerCLI scripts  ====

===== integration =====

* [[Introduction to scripting vi using perl or powershell]]

* [[Manage VMware Server with PowerShell]]

* [[Introduction to the vSphere SDK in Java and C#]]

* [http://blogs.vmware.com/vipowershell/2009/09/how-to-run-powercli-scripts-from-vcenter-alarms.html How to run PowerCLI scripts from vCenter alarms]

* [[PowerCLI: WebPowerCLI, run scripts from your browser]]

===== not categorized =====

* [http://communities.vmware.com/docs/DOC-6972 Deploy and Redeploy vm's (from templates) from a .csv]

* [http://communities.vmware.com/docs/DOC-9610 Resourcepool Reservation Script]

* [http://communities.vmware.com/docs/DOC-7090 Add/Remove active directory user accounts who belong to a particular security group on all ESX hosts]

* [http://mikedatl.typepad.com/mikedvirtualization/2008/10/quick-migration.html Quick migration]

* [[Out-Dataset Cmdlet]]


==== VM Configuration ====

* [http://virtualfuture.info/2008/07/powershell-remove-connected-iso/ Remove connected iso's]

* [[Restart VMware Tools on all Windows VM's]]

* [[PowerCLI: Update VMwaretools without a reboot]]

* [[PowerCLI: Add configuration details to VMX]]

* [[PowerCLI: Scripted edit of a VMX file]]

* [[PowerCLI: Get Virtual Machine disk usage]]

* [[PowerCLI: Set CPU Identification Mask]]

* [[PowerCLI: Force a VM to enter BIOS setup on next boot]]

* [[PowerCLI: Set VM Snapshot location]]

* [[PowerCLI: Resolving improper memory limits on your virtual machines]]

* [[PowerCLI: Dump virtual machine info as XML]]

* [[PowerCLI: Match VM and Windows hard disks]]

* [[PowerCLI: Determine vSwitch vmnic for your VM]]

* [[PowerCLI: Get VM Swap Information]]

* [[PowerCLI: HL Tools – Part 1 – Clone a VM without vCenter]]

* [[PowerCLI: HL Tools – Part 2 – Create a nested hypervisor]]

* [[PowerCLI: Change Virtual Machines Guest OS Names]]

* [[PowerCLI: Create multiple VMs]]

==== Host Management ====

* [[PowerCLI: Report every VM added to vCenter in the last 30 days]]

* [[PowerCLI: Get Virtual Machine total size]]

* [[PowerCLI: Export and import customization profiles]]

* [[PowerCLI: Export Task and eventlogs to file using TaskHistoryCollector]]

* [[PowerCLI: Snap reminder]]

* [[PowerCLI: Daily Report]]

* [[PowerCLI: Get number of vCPU%27s used in cluster]]

* [[PowerCLI: Factory reset of ESXi]]

* [[PowerCLI: Cluster Load]]

* [[PowerCLI: Get VMHost Support Bundles]]

* [[PowerCLI: Update host from ESXi 5.1 to 5.1 update 1]]

* [[PowerCLI: VM stats and Google Charts]]

* [[PowerCLI: ESXi 5.0 / ESXi 5.1 Host Backup &amp; Restore GUI Utility]]

===== Integration with ESXi shell =====

* [[PowerCLI: Using plink to modify ESXi host configuration files via SSH]]

* [[PowerCLI: enable SSH and configure ESXi Firewall]]

* [[PowerCLI: Update ESXi Root Password with Password Generator]]

* [[PowerCLI: enable SSH GUI for vSphere clusters]]

==== Storage ====

*[[PowerCLI: HBA Load Balancer]]

* [[PowerCLI: Upgrading your VMFS datastores]]

* [[PowerCLI: Upgrade from VMFS3 to VMFS5 with no downtime]]

* [[PowerCLI: Checking VMFS Version and Block Sizes]]

* [[PowerCLI: Set the Path Selection Policy for every device path of every host in your vSphere 5.0/5.1 cluster]]

* [https://labs.vmware.com/flings/powercli-cmdlet-for-nfs PowerCLI cmdlet for NFS]

==== Networking ====
* [[PowerCLI: Verify and change the existing Bridge Protocol Data Unit (BPDU) Filter configuration]]

===== dvSwitch =====
* [[PowerCLI: dvPortgroup ports report]]
* [[PowerCLI: Disable Netflow for a VDPortgroup or a number of VDPortGroups]]

==== vCloud ====

* [[PowerCLI: Show-vCloudStatsHtml.ps1]]
* [[PowerCLI: Install Software in Isolated Virtual Machines]]

==== libraries ====
* [[PowerCLI: Scriptkit]]

[[Category: Powershell]][[Category: VI-Toolkit]][[Category: PowerCLI]]</text>
    <sha1>16a9a284d8dd19bc67b7891b7a2f8cac62f6945e</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Python</title>
  <ns>0</ns>
  <id>535</id>
  <revision>
    <id>1395</id>
    <parentid>1300</parentid>
    <timestamp>2015-07-13T08:50:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="107" xml:space="preserve">
[[pysphere]]

[[pyvmomi]]

[[getvmstree.py]]

[[pyxenter]]

[[tasklist.py]]

[[PVC]]

[[Category: Python]]</text>
    <sha1>66178114840a36b357f17f266e11a6ae15511f24</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Vmrun</title>
  <ns>0</ns>
  <id>470</id>
  <revision>
    <id>1397</id>
    <parentid>957</parentid>
    <timestamp>2015-11-22T13:00:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9179" xml:space="preserve">vmrun is a command line utility that can be used to run certain automation tasks easily.
It is easy to make it part of a script and do things like start a particular VM, create a snapshot, run a program in the guest, etcetera.


==== Limitations while running the VM in the GUI ====
There are some things you can't do things while the VM is open in the UI, but other things should work.

Things you can do:
* Power off the VM
* Suspend the VM
* Create a snapshot 
* Revert to a snapshot (need to verify)
* Pause and unpause the VM
* Power on the VM using the 'gui' option
* Perform guest operations (runProgramInGuest, listDirectoryInGuest, etc.)
* Start and stop recording
* Mount the Tools installer
* Run any vProbes commands
* Change the shared folder settings (add, remove, enable) of a running VM.

Things you cannot do:
* Upgrade the VM's virtual hardware
* Power on the VM using the 'nogui' option 
* Change the shared folder settings (add, remove, enable) of a powered off or suspended VM

==== Command line help contents ====
  C:\Program Files (x86)\VMware\VMware Workstation\vmrun
  
  vmrun version 1.15.1 build-3160714
  
  Usage: vmrun [AUTHENTICATION-FLAGS] COMMAND [PARAMETERS]
  
  
  AUTHENTICATION-FLAGS
  --------------------
  These must appear before the command and any command parameters.
  
     -h &lt;hostName&gt;  (not needed for Workstation)
     -P &lt;hostPort&gt;  (not needed for Workstation)
     -T &lt;hostType&gt; (ws|server|server1|fusion|esx|vc|player)
       for example, use '-T server' for Server 2.0
                    use '-T server1' for Server 1.0
                    use '-T ws' for VMware Workstation
                    use '-T ws-shared' for VMware Workstation (shared mode)
                    use '-T esx' for VMware ESX
                    use '-T vc' for VMware vCenter Server
     -u &lt;userName in host OS&gt;  (not needed for Workstation)
     -p &lt;password in host OS&gt;  (not needed for Workstation)
     -vp &lt;password for encrypted virtual machine&gt;
     -gu &lt;userName in guest OS&gt;
     -gp &lt;password in guest OS&gt;
  
  
  POWER COMMANDS           PARAMETERS           DESCRIPTION
  --------------           ----------           -----------
  start                    Path to vmx file     Start a VM or Team
                           [gui|nogui]
  
  stop                     Path to vmx file     Stop a VM or Team
                           [hard|soft]
  
  reset                    Path to vmx file     Reset a VM or Team
                           [hard|soft]
  
  suspend                  Path to vmx file     Suspend a VM or Team
                           [hard|soft]
  
  pause                    Path to vmx file     Pause a VM
  
  unpause                  Path to vmx file     Unpause a VM
  
  
  SNAPSHOT COMMANDS        PARAMETERS           DESCRIPTION
  -----------------        ----------           -----------
  listSnapshots            Path to vmx file     List all snapshots in a VM
                           [showTree]
  
  snapshot                 Path to vmx file     Create a snapshot of a VM
                           Snapshot name
  
  deleteSnapshot           Path to vmx file     Remove a snapshot from a VM
                           Snapshot name
                           [andDeleteChildren]
  
  revertToSnapshot         Path to vmx file     Set VM state to a snapshot
                           Snapshot name
  
  
  GUEST OS COMMANDS        PARAMETERS           DESCRIPTION
  -----------------        ----------           -----------
  runProgramInGuest        Path to vmx file     Run a program in Guest OS
                           [-noWait]
                           [-activeWindow]
                           [-interactive]
                           Complete-Path-To-Program
                           [Program arguments]
  
  fileExistsInGuest        Path to vmx file     Check if a file exists in Guest OS
  
                           Path to file in guest
  
  directoryExistsInGuest   Path to vmx file     Check if a directory exists in Guest OS
                           Path to directory in guest
  
  setSharedFolderState     Path to vmx file     Modify a Host-Guest shared folder
                           Share name
                           Host path
                           writable | readonly
  
  addSharedFolder          Path to vmx file     Add a Host-Guest shared folder
                           Share name
                           New host path
  
  removeSharedFolder       Path to vmx file     Remove a Host-Guest shared folder
                           Share name
  
  enableSharedFolders      Path to vmx file     Enable shared folders in Guest
                           [runtime]
  
  disableSharedFolders     Path to vmx file     Disable shared folders in Guest
                           [runtime]
  
  listProcessesInGuest     Path to vmx file     List running processes in Guest OS
  
  
  killProcessInGuest       Path to vmx file     Kill a process in Guest OS
                           process id
  
  runScriptInGuest         Path to vmx file     Run a script in Guest OS
                           [-noWait]
                           [-activeWindow]
                           [-interactive]
                           Interpreter path
                           Script text
  
  deleteFileInGuest        Path to vmx file     Delete a file in Guest OS
  Path in guest
  
  createDirectoryInGuest   Path to vmx file     Create a directory in Guest OS
  Directory path in guest
  
  deleteDirectoryInGuest   Path to vmx file     Delete a directory in Guest OS
  Directory path in guest
  
  CreateTempfileInGuest    Path to vmx file     Create a temporary file in Guest OS
  
  listDirectoryInGuest     Path to vmx file     List a directory in Guest OS
                           Directory path in guest
  
  CopyFileFromHostToGuest  Path to vmx file     Copy a file from host OS to guest OS
  Path on host             Path in guest
  
  
  CopyFileFromGuestToHost  Path to vmx file     Copy a file from guest OS to host OS
  Path in guest            Path on host
  
  
  renameFileInGuest        Path to vmx file     Rename a file in Guest OS
                           Original name
                           New name
  
  captureScreen            Path to vmx file     Capture the screen of the VM to a local file
  Path on host
  
  writeVariable            Path to vmx file     Write a variable in the VM state
                           [runtimeConfig|guestEnv|guestVar]
                           variable name
                           variable value
  
  readVariable             Path to vmx file     Read a variable in the VM state
                           [runtimeConfig|guestEnv|guestVar]
                           variable name
  
  getGuestIPAddress        Path to vmx file     Gets the IP address of the guest
                           [-wait]
  
  
  GENERAL COMMANDS         PARAMETERS           DESCRIPTION
  ----------------         ----------           -----------
  list                                          List all running VMs
  
  upgradevm                Path to vmx file     Upgrade VM file format, virtual hw
  
  
  installTools             Path to vmx file     Install Tools in Guest
  
  checkToolsState          Path to vmx file     Check the current Tools state
  
  register                 Path to vmx file     Register a VM
  
  unregister               Path to vmx file     Unregister a VM
  
  listRegisteredVM                              List registered VMs
  
  deleteVM                 Path to vmx file     Delete a VM
  
  clone                    Path to vmx file     Create a copy of the VM
                           Path to destination vmx file
                           full|linked
                           [-snapshot=Snapshot Name]
                           [-cloneName=Name]
 
  
  Examples:
 
  Starting a virtual machine with Workstation on a Windows host
     vmrun -T ws start "c:\my VMs\myVM.vmx"
  
  Stopping a virtual machine on an ESX host
     vmrun -T esx -h https://myHost.com/sdk -u hostUser -p hostPassword stop "[storage1] vm/myVM.vmx"
  
  Running a program in a virtual machine with Workstation on a Windows host with Windows guest
     vmrun -T ws -gu guestUser -gp guestPassword runProgramInGuest "c:\my VMs\myVM.vmx" "c:\Program Files\myProgram.exe"
  
  Running a program in a virtual machine with Server on a Linux host with Linux guest
     vmrun -T server -h https://myHost.com:8333/sdk -u hostUser -p hostPassword -gu guestUser -gp guestPassword runProgramInGuest "[standard] vm/myVM.vmx" /usr/bin/X11/xclock -display :0
  
  Creating a snapshot of a virtual machine with Workstation on a Windows host
     vmrun -T ws snapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Reverting to a snapshot with Workstation on a Windows host
     vmrun -T ws revertToSnapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Deleting a snapshot with Workstation on a Windows host
     vmrun -T ws deleteSnapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Enabling Shared Folders with Workstation on a Windows host
     vmrun -T ws enableSharedFolders "c:\my VMs\myVM.vmx"


[[Category: VIX]]</text>
    <sha1>3bc9d768a38d3ac91a2be850cbcb53553c795418</sha1>
  </revision>
  <revision>
    <id>1398</id>
    <parentid>1397</parentid>
    <timestamp>2015-11-22T13:01:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Command line help contents */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9225" xml:space="preserve">vmrun is a command line utility that can be used to run certain automation tasks easily.
It is easy to make it part of a script and do things like start a particular VM, create a snapshot, run a program in the guest, etcetera.


==== Limitations while running the VM in the GUI ====
There are some things you can't do things while the VM is open in the UI, but other things should work.

Things you can do:
* Power off the VM
* Suspend the VM
* Create a snapshot 
* Revert to a snapshot (need to verify)
* Pause and unpause the VM
* Power on the VM using the 'gui' option
* Perform guest operations (runProgramInGuest, listDirectoryInGuest, etc.)
* Start and stop recording
* Mount the Tools installer
* Run any vProbes commands
* Change the shared folder settings (add, remove, enable) of a running VM.

Things you cannot do:
* Upgrade the VM's virtual hardware
* Power on the VM using the 'nogui' option 
* Change the shared folder settings (add, remove, enable) of a powered off or suspended VM

==== Command line help contents ====
Output VMware Workstation 12.01 help of vmrun
  C:\Program Files (x86)\VMware\VMware Workstation\vmrun
  
  vmrun version 1.15.1 build-3160714
  
  Usage: vmrun [AUTHENTICATION-FLAGS] COMMAND [PARAMETERS]
  
  
  AUTHENTICATION-FLAGS
  --------------------
  These must appear before the command and any command parameters.
  
     -h &lt;hostName&gt;  (not needed for Workstation)
     -P &lt;hostPort&gt;  (not needed for Workstation)
     -T &lt;hostType&gt; (ws|server|server1|fusion|esx|vc|player)
       for example, use '-T server' for Server 2.0
                    use '-T server1' for Server 1.0
                    use '-T ws' for VMware Workstation
                    use '-T ws-shared' for VMware Workstation (shared mode)
                    use '-T esx' for VMware ESX
                    use '-T vc' for VMware vCenter Server
     -u &lt;userName in host OS&gt;  (not needed for Workstation)
     -p &lt;password in host OS&gt;  (not needed for Workstation)
     -vp &lt;password for encrypted virtual machine&gt;
     -gu &lt;userName in guest OS&gt;
     -gp &lt;password in guest OS&gt;
  
  
  POWER COMMANDS           PARAMETERS           DESCRIPTION
  --------------           ----------           -----------
  start                    Path to vmx file     Start a VM or Team
                           [gui|nogui]
  
  stop                     Path to vmx file     Stop a VM or Team
                           [hard|soft]
  
  reset                    Path to vmx file     Reset a VM or Team
                           [hard|soft]
  
  suspend                  Path to vmx file     Suspend a VM or Team
                           [hard|soft]
  
  pause                    Path to vmx file     Pause a VM
  
  unpause                  Path to vmx file     Unpause a VM
  
  
  SNAPSHOT COMMANDS        PARAMETERS           DESCRIPTION
  -----------------        ----------           -----------
  listSnapshots            Path to vmx file     List all snapshots in a VM
                           [showTree]
  
  snapshot                 Path to vmx file     Create a snapshot of a VM
                           Snapshot name
  
  deleteSnapshot           Path to vmx file     Remove a snapshot from a VM
                           Snapshot name
                           [andDeleteChildren]
  
  revertToSnapshot         Path to vmx file     Set VM state to a snapshot
                           Snapshot name
  
  
  GUEST OS COMMANDS        PARAMETERS           DESCRIPTION
  -----------------        ----------           -----------
  runProgramInGuest        Path to vmx file     Run a program in Guest OS
                           [-noWait]
                           [-activeWindow]
                           [-interactive]
                           Complete-Path-To-Program
                           [Program arguments]
  
  fileExistsInGuest        Path to vmx file     Check if a file exists in Guest OS
  
                           Path to file in guest
  
  directoryExistsInGuest   Path to vmx file     Check if a directory exists in Guest OS
                           Path to directory in guest
  
  setSharedFolderState     Path to vmx file     Modify a Host-Guest shared folder
                           Share name
                           Host path
                           writable | readonly
  
  addSharedFolder          Path to vmx file     Add a Host-Guest shared folder
                           Share name
                           New host path
  
  removeSharedFolder       Path to vmx file     Remove a Host-Guest shared folder
                           Share name
  
  enableSharedFolders      Path to vmx file     Enable shared folders in Guest
                           [runtime]
  
  disableSharedFolders     Path to vmx file     Disable shared folders in Guest
                           [runtime]
  
  listProcessesInGuest     Path to vmx file     List running processes in Guest OS
  
  
  killProcessInGuest       Path to vmx file     Kill a process in Guest OS
                           process id
  
  runScriptInGuest         Path to vmx file     Run a script in Guest OS
                           [-noWait]
                           [-activeWindow]
                           [-interactive]
                           Interpreter path
                           Script text
  
  deleteFileInGuest        Path to vmx file     Delete a file in Guest OS
  Path in guest
  
  createDirectoryInGuest   Path to vmx file     Create a directory in Guest OS
  Directory path in guest
  
  deleteDirectoryInGuest   Path to vmx file     Delete a directory in Guest OS
  Directory path in guest
  
  CreateTempfileInGuest    Path to vmx file     Create a temporary file in Guest OS
  
  listDirectoryInGuest     Path to vmx file     List a directory in Guest OS
                           Directory path in guest
  
  CopyFileFromHostToGuest  Path to vmx file     Copy a file from host OS to guest OS
  Path on host             Path in guest
  
  
  CopyFileFromGuestToHost  Path to vmx file     Copy a file from guest OS to host OS
  Path in guest            Path on host
  
  
  renameFileInGuest        Path to vmx file     Rename a file in Guest OS
                           Original name
                           New name
  
  captureScreen            Path to vmx file     Capture the screen of the VM to a local file
  Path on host
  
  writeVariable            Path to vmx file     Write a variable in the VM state
                           [runtimeConfig|guestEnv|guestVar]
                           variable name
                           variable value
  
  readVariable             Path to vmx file     Read a variable in the VM state
                           [runtimeConfig|guestEnv|guestVar]
                           variable name
  
  getGuestIPAddress        Path to vmx file     Gets the IP address of the guest
                           [-wait]
  
  
  GENERAL COMMANDS         PARAMETERS           DESCRIPTION
  ----------------         ----------           -----------
  list                                          List all running VMs
  
  upgradevm                Path to vmx file     Upgrade VM file format, virtual hw
  
  
  installTools             Path to vmx file     Install Tools in Guest
  
  checkToolsState          Path to vmx file     Check the current Tools state
  
  register                 Path to vmx file     Register a VM
  
  unregister               Path to vmx file     Unregister a VM
  
  listRegisteredVM                              List registered VMs
  
  deleteVM                 Path to vmx file     Delete a VM
  
  clone                    Path to vmx file     Create a copy of the VM
                           Path to destination vmx file
                           full|linked
                           [-snapshot=Snapshot Name]
                           [-cloneName=Name]
 
  
  Examples:
 
  Starting a virtual machine with Workstation on a Windows host
     vmrun -T ws start "c:\my VMs\myVM.vmx"
  
  Stopping a virtual machine on an ESX host
     vmrun -T esx -h https://myHost.com/sdk -u hostUser -p hostPassword stop "[storage1] vm/myVM.vmx"
  
  Running a program in a virtual machine with Workstation on a Windows host with Windows guest
     vmrun -T ws -gu guestUser -gp guestPassword runProgramInGuest "c:\my VMs\myVM.vmx" "c:\Program Files\myProgram.exe"
  
  Running a program in a virtual machine with Server on a Linux host with Linux guest
     vmrun -T server -h https://myHost.com:8333/sdk -u hostUser -p hostPassword -gu guestUser -gp guestPassword runProgramInGuest "[standard] vm/myVM.vmx" /usr/bin/X11/xclock -display :0
  
  Creating a snapshot of a virtual machine with Workstation on a Windows host
     vmrun -T ws snapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Reverting to a snapshot with Workstation on a Windows host
     vmrun -T ws revertToSnapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Deleting a snapshot with Workstation on a Windows host
     vmrun -T ws deleteSnapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Enabling Shared Folders with Workstation on a Windows host
     vmrun -T ws enableSharedFolders "c:\my VMs\myVM.vmx"


[[Category: VIX]]</text>
    <sha1>9cce0e13bc3b38874601e2c677bff171c255a20f</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Vmware-vdiskmanager</title>
  <ns>0</ns>
  <id>574</id>
  <revision>
    <id>1399</id>
    <timestamp>2015-11-22T16:39:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "== vmware-vdiskmanager ==   With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as: * shrink * defragment * repair  =..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4151" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* shrink
* defragment
* repair

=== Peculiarities ===

VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This should also work much better since Fusion 8 / Workstation 12.0

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>1bedeb968183520ed34e086201525b7a1941d0cc</sha1>
  </revision>
  <revision>
    <id>1400</id>
    <parentid>1399</parentid>
    <timestamp>2015-11-22T16:46:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Peculiarities */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4715" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* shrink
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This should also work much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a desctructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>5fe2dbffd16041f56a46b893ac163a6cd0374103</sha1>
  </revision>
  <revision>
    <id>1405</id>
    <parentid>1400</parentid>
    <timestamp>2016-01-12T12:18:18Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Peculiarities */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4919" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* shrink
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This should also work much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a desctructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

* The remote host fusion in Fusion 8 and Workstation 12 via the -h option is broken. See also [https://communities.vmware.com/thread/527749 BUG: vmware-vdiskmanager does not accept advertised -h option]

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>053f610b36217a2d0e33a662a777fb02684421d4</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Open-vm-tools</title>
  <ns>0</ns>
  <id>427</id>
  <revision>
    <id>1401</id>
    <parentid>832</parentid>
    <timestamp>2015-11-29T19:53:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Open Virtual Machine Tools */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="648" xml:space="preserve">==== Open Virtual Machine Tools ====


The Open Virtual Machine Tools (open-vm-tools) are the open source implementation of VMware Tools.

The Open Virtual Machine Tools project aims to provide a suite of open source virtualization utilities and drivers to improve the functionality and user experience of virtualization. The project currently runs in guest operating systems under VMware hypervisors.

Project page: https://github.com/vmware/open-vm-tools

===== old links =====
* [http://sourceforge.net/projects/open-vm-tools/ sourceforge open-vm-tools project page]

* [http://open-vm-tools.sourceforge.net/ homepage]

[[Category: VMware OSS]]</text>
    <sha1>99fa45bf9df168688c329291c0e3f255ee4de893</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1402</id>
    <parentid>1313</parentid>
    <timestamp>2015-11-29T19:56:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Statistics, search and navigation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2932" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since January 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

==== Contribute / help out ====
This is an OPEN wiki site, but you have to sign up for editing as we got severely hit by spammers in the past.

We do encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then have a look [[VI-Toolkit:Users| here]]

==== Statistics, search and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you. 

As extra help, the categories are listed below as well.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware Artwork&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>b1c6fa893bb6d314e11ec51aba81efbf485cff75</sha1>
  </revision>
</page>
<page arvcontinue="20140619223432|1357">
  <title>BEGINNERS PAGE</title>
  <ns>0</ns>
  <id>433</id>
  <revision>
    <id>1403</id>
    <parentid>976</parentid>
    <timestamp>2015-11-29T20:06:40Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="995" xml:space="preserve">Looking to Get-Started with the VI Toolkit ?

Check out the below links to find useful resources or add your own:

* [http://communities.vmware.com/docs/DOC-4210 Managing VMware with PowerShell FAQ]
* [http://www.virtu-al.net/2009/02/23/vi-toolkit-quick-reference-guide/ VI Toolkit Quick Reference Guide]
* [http://www.icomasoft.com/products/vi-powerscripter/powercli-reference-card.html PowerCLI Quick Reference Card]
* [http://web.archive.org/web/20100515114006/http://vinternals.com/powercli-mastery vinternals: PowerCLI mastery]
* [http://keithhill.spaces.live.com/blog Keith hill blog]
* [http://blogs.vmware.com/files/vi-toolkit-lab----vmworld-europe-2009.pdf VI Toolkit lab VMworld europe 2009]

Podcasts you should listen to:

* [http://get-scripting.blogspot.com/ Get-Scripting Podcast] by [[Alan Renouf]] and [[Jonathan Medd]]
* [http://powerscripting.wordpress.com/ PowerScripting Podcast] by [[Jonathan Walz]] and [[Hal Rottenberg]]

Add your own Tips here:

[[Category: Powershell]]</text>
    <sha1>539fb388aaee80c515d3417c8c1560551a9f78ed</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>1407</id>
    <parentid>1385</parentid>
    <timestamp>2016-11-09T21:25:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* VMware Developer targeted sites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2346" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://twitter.com/PowerCLITip @PowerCLITip] Learn #PowerCLI one tweet at a time by following updates from @PowerCLITip #VMware #PowerShell

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [http://chitchat.at.infoseek.co.jp/vmware/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>ec142967cab174bc10a7d177639636274c20bacf</sha1>
  </revision>
  <revision>
    <id>1408</id>
    <parentid>1407</parentid>
    <timestamp>2016-11-09T21:33:17Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Sites with code */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2350" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://communities.vmware.com/blogs/DeveloperCenter VMware Communities Developer Center blog] Soon to be replaced with:

* [http://blogs.vmware.com/developer NEW VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://twitter.com/PowerCLITip @PowerCLITip] Learn #PowerCLI one tweet at a time by following updates from @PowerCLITip #VMware #PowerShell

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>68c638e09d37b593394d83bfe701f2280a298c1f</sha1>
  </revision>
  <revision>
    <id>1409</id>
    <parentid>1408</parentid>
    <timestamp>2016-11-09T21:35:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VMware Developer targeted sites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2222" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/vipowershell VMware powershell blog]

* [http://blogs.vmware.com/developer VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://twitter.com/PowerCLITip @PowerCLITip] Learn #PowerCLI one tweet at a time by following updates from @PowerCLITip #VMware #PowerShell

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>96282245f43df475e92200fec389c02ea46223af</sha1>
  </revision>
  <revision>
    <id>1410</id>
    <parentid>1409</parentid>
    <timestamp>2016-11-09T21:35:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VMware Developer targeted sites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2217" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [http://blogs.vmware.com/developer VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://twitter.com/PowerCLITip @PowerCLITip] Learn #PowerCLI one tweet at a time by following updates from @PowerCLITip #VMware #PowerShell

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>0f49fce49bd1c2c95fc52ed3d95996cd3e8d84df</sha1>
  </revision>
  <revision>
    <id>1411</id>
    <parentid>1410</parentid>
    <timestamp>2016-11-09T21:38:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VMware Developer targeted sites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2135" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [http://blogs.vmware.com/developer VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

* [http://devcheatsheet.com/ Developer Cheat Sheet]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>5275ea1fb531959d730155ec33db8675fc0a8111</sha1>
  </revision>
  <revision>
    <id>1412</id>
    <parentid>1411</parentid>
    <timestamp>2016-11-09T21:40:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Sites with code */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2082" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [http://blogs.vmware.com/developer VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

* [http://robertbchase.blogspot.com/ Robert Chase's Blog VMware info]

[[Category: website]]</text>
    <sha1>215bed89454045541cb4158c8f1ae55a6964cfdb</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>VI-Toolkit:Privacy policy</title>
  <ns>4</ns>
  <id>575</id>
  <revision>
    <id>1413</id>
    <timestamp>2016-11-09T21:47:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "The only thing we collect are webserver logs and those are rotated after a while.  In other words we do not collect ANY visitor info."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="133" xml:space="preserve">The only thing we collect are webserver logs and those are rotated after a while.

In other words we do not collect ANY visitor info.</text>
    <sha1>ac657d45d00a106e026ae4bbcaacbb18daa60cbb</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>VI-Toolkit:General disclaimer</title>
  <ns>4</ns>
  <id>576</id>
  <revision>
    <id>1414</id>
    <timestamp>2016-11-09T21:48:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "All scripts, code and tips belong to the authors mentioned.  Any use of the provided information is at your own risk."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="117" xml:space="preserve">All scripts, code and tips belong to the authors mentioned.

Any use of the provided information is at your own risk.</text>
    <sha1>141080bc006d1d8c883ab5c947f73b291683721a</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>Vmware-vdiskmanager</title>
  <ns>0</ns>
  <id>574</id>
  <revision>
    <id>1415</id>
    <parentid>1405</parentid>
    <timestamp>2016-11-15T10:12:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Peculiarities */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5131" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* shrink
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This should also work much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a desctructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

* The remote host fusion in Fusion 8 and Workstation 12 via the -h option is broken. See also [https://communities.vmware.com/thread/527749 BUG: vmware-vdiskmanager does not accept advertised -h option]

* VMware Player does not come with this tool, but in case of need you can download the [https://developercenter.vmware.com/web/sdk/60/vddk Virtual Disk Development Kit] which does include a copy of the program.

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>1857136930f20c54df6334953e994d0953c5c55c</sha1>
  </revision>
  <revision>
    <id>1416</id>
    <parentid>1415</parentid>
    <timestamp>2016-11-15T10:13:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Peculiarities */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5138" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* shrink
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This should also work much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a desctructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

* The remote host fusion in Fusion 8 and Workstation 12 via the -h option is broken. See also [https://communities.vmware.com/thread/527749 BUG: vmware-vdiskmanager does not accept advertised -h option]

* VMware Player does not come with this tool, but in case of need you can download the [https://developercenter.vmware.com/web/sdk/60/vddk Virtual Disk Development Kit (VDDK)] which does include a copy of the program.

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>a5d7881c978deb00785207d5ba5da698a67d249c</sha1>
  </revision>
  <revision>
    <id>1417</id>
    <parentid>1416</parentid>
    <timestamp>2016-11-15T13:15:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* vmware-vdiskmanager */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5174" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* [[Shrink guest on hosted platform|shrink]]
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This should also work much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a desctructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

* The remote host fusion in Fusion 8 and Workstation 12 via the -h option is broken. See also [https://communities.vmware.com/thread/527749 BUG: vmware-vdiskmanager does not accept advertised -h option]

* VMware Player does not come with this tool, but in case of need you can download the [https://developercenter.vmware.com/web/sdk/60/vddk Virtual Disk Development Kit (VDDK)] which does include a copy of the program.

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>08c8ea4d996df9fb1d2b64f9739ce120b4abf9c9</sha1>
  </revision>
  <revision>
    <id>1427</id>
    <parentid>1417</parentid>
    <timestamp>2016-12-27T13:28:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* External links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5789" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* [[Shrink guest on hosted platform|shrink]]
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This should also work much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a desctructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

* The remote host fusion in Fusion 8 and Workstation 12 via the -h option is broken. See also [https://communities.vmware.com/thread/527749 BUG: vmware-vdiskmanager does not accept advertised -h option]

* VMware Player does not come with this tool, but in case of need you can download the [https://developercenter.vmware.com/web/sdk/60/vddk Virtual Disk Development Kit (VDDK)] which does include a copy of the program.

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== Split disks ===

Up until Workstation 11 / Fusion 7 a split disk would never be larger as 2GB.

Due to the virtual disk sizes growing and the extra limitations - such as max open files - that could be hit with larger disks, this is no longer the case for split virtual disks. 

Nowadays the split disk size (= extent size) depends on the size you have set your virtual disk to be.

The new split disk scheme


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

 
=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>6151b7e911a872218e92709a15217391c5384b35</sha1>
  </revision>
  <revision>
    <id>1428</id>
    <parentid>1427</parentid>
    <timestamp>2016-12-27T13:32:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Peculiarities */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5777" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* [[Shrink guest on hosted platform|shrink]]
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This works much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a destructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

* The remote host fusion in Fusion 8 and Workstation 12 via the -h option is broken. See also [https://communities.vmware.com/thread/527749 BUG: vmware-vdiskmanager does not accept advertised -h option]

* VMware Player does not come with this tool, but in case of need you can download the [https://developercenter.vmware.com/web/sdk/60/vddk Virtual Disk Development Kit (VDDK)] which does include a copy of the program.

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== Split disks ===

Up until Workstation 11 / Fusion 7 a split disk would never be larger as 2GB.

Due to the virtual disk sizes growing and the extra limitations - such as max open files - that could be hit with larger disks, this is no longer the case for split virtual disks. 

Nowadays the split disk size (= extent size) depends on the size you have set your virtual disk to be.

The new split disk scheme


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

 
=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>5276bf40abc8045107f70f62d19da7675257feda</sha1>
  </revision>
  <revision>
    <id>1429</id>
    <parentid>1428</parentid>
    <timestamp>2016-12-27T13:36:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Split disks */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6025" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* [[Shrink guest on hosted platform|shrink]]
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This works much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a destructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

* The remote host fusion in Fusion 8 and Workstation 12 via the -h option is broken. See also [https://communities.vmware.com/thread/527749 BUG: vmware-vdiskmanager does not accept advertised -h option]

* VMware Player does not come with this tool, but in case of need you can download the [https://developercenter.vmware.com/web/sdk/60/vddk Virtual Disk Development Kit (VDDK)] which does include a copy of the program.

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== Split disks ===

Up until Workstation 11 / Fusion 7 a split disk would never be larger as 2GB.

Due to the virtual disk sizes growing and the extra limitations - such as max open files - that could be hit with larger disks, this is no longer the case for split virtual disks. 

Nowadays the split disk size (= extent size) depends on the size you have set your virtual disk to be.

The new split disk scheme


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

This means that if you want to keep your Virtual Disks to be transportable via FAT32 that you probably should keep your disk sizes under 128GB.

Note that NTFS or HFS has no such limitation, so choosing your maximum virtual disk size depends on need.

=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>1bf5d9d498b5e795019f535ed4517f3f6177580d</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>Shrink guest on hosted platform</title>
  <ns>0</ns>
  <id>577</id>
  <revision>
    <id>1418</id>
    <timestamp>2016-11-15T13:20:37Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "==== Zero out unused space in a Linux VM ====  Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free spac..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2306" xml:space="preserve">==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Next, reboot your VM from a live CD and mount the file systems.

The reason we are doing this from a live CD is that we are going to write out zero's to the file system and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this "reboot from a live CD" step is important!

 from your live CD, check out the filesystem of your VM, for example:

 fdisk -l
will show you:


 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros.

If you do not have a Live CD, then you can run the command to zero out the unused space as root, but remember to shut down services like databases first.


==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, the trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -r Ubuntu\ Desktop.vmdk

On Windows the command also uses the -r option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.</text>
    <sha1>7012873b3a1f292678f417f3c143d0bf4c115bf6</sha1>
  </revision>
  <revision>
    <id>1419</id>
    <parentid>1418</parentid>
    <timestamp>2016-11-15T14:31:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Zero out unused space in a Linux VM */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2509" xml:space="preserve">==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Next, reboot your VM from a live CD and mount the file systems.

The reason we are doing this from a live CD is that we are going to write out zero's to the file system and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this "reboot from a live CD" step is important!

 from your live CD, check out the filesystem of your VM, for example:

 fdisk -l
will show you:


 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros.

As this command writes out zero's to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected and is also why we suggest to do this from a Live CD.

If you do not have a Live CD, then you can run the command to zero out the unused space as root, but remember to shut down services like databases first.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, the trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -r Ubuntu\ Desktop.vmdk

On Windows the command also uses the -r option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.</text>
    <sha1>fca278707c5f8e0c22bc7e01b7433649231907a7</sha1>
  </revision>
  <revision>
    <id>1420</id>
    <parentid>1419</parentid>
    <timestamp>2016-11-15T14:32:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Shrink the disk */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2509" xml:space="preserve">==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Next, reboot your VM from a live CD and mount the file systems.

The reason we are doing this from a live CD is that we are going to write out zero's to the file system and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this "reboot from a live CD" step is important!

 from your live CD, check out the filesystem of your VM, for example:

 fdisk -l
will show you:


 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros.

As this command writes out zero's to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected and is also why we suggest to do this from a Live CD.

If you do not have a Live CD, then you can run the command to zero out the unused space as root, but remember to shut down services like databases first.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, the trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.</text>
    <sha1>eae8f2e15b1963d80604acf44eb782316f43c740</sha1>
  </revision>
  <revision>
    <id>1421</id>
    <parentid>1420</parentid>
    <timestamp>2016-11-15T14:39:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Zero out unused space in a Linux VM */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2221" xml:space="preserve">==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Next, shut down any services that depend on enough available disk space to run.

The reason we are doing this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros.

As this command writes out zero's to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, the trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.</text>
    <sha1>8b81ceba49445726d07093a14552ef7420e413ca</sha1>
  </revision>
  <revision>
    <id>1422</id>
    <parentid>1421</parentid>
    <timestamp>2016-11-15T14:42:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2321" xml:space="preserve">==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.</text>
    <sha1>661310ca82f64916c63ea03a5c2d10c3c4f61fba</sha1>
  </revision>
  <revision>
    <id>1423</id>
    <parentid>1422</parentid>
    <timestamp>2016-11-15T14:44:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Zero out unused space in a Linux VM */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2627" xml:space="preserve">==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.</text>
    <sha1>10ed13b124a437303407ce4849c9d4e96be5c67f</sha1>
  </revision>
  <revision>
    <id>1424</id>
    <parentid>1423</parentid>
    <timestamp>2016-11-21T08:53:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Zero out unused space in a Linux VM */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3032" xml:space="preserve">Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.</text>
    <sha1>e029a1f0022d65977d2bd703906fff9a408de77b</sha1>
  </revision>
  <revision>
    <id>1431</id>
    <parentid>1424</parentid>
    <timestamp>2017-04-20T16:26:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3303" xml:space="preserve">Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrinnk feature as offered via vmware tools.

In order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.</text>
    <sha1>1116d789bda82b34cd867c3fb9fb0075e13b59a0</sha1>
  </revision>
  <revision>
    <id>1435</id>
    <parentid>1431</parentid>
    <timestamp>2017-07-06T15:24:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Shrink using vmware tools */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3482" xml:space="preserve">Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink</text>
    <sha1>07ac4bb46e318f5b333b48118acb3bcff00fa438</sha1>
  </revision>
  <revision>
    <id>1436</id>
    <parentid>1435</parentid>
    <timestamp>2017-07-27T22:50:28Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Shrink using vmware tools */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3604" xml:space="preserve">Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>363e91e8c020b38a0931bde06d417b940e74f90d</sha1>
  </revision>
  <revision>
    <id>1440</id>
    <parentid>1436</parentid>
    <timestamp>2017-11-04T14:37:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Zero out unused space in a Linux VM */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4515" xml:space="preserve">Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

===== Zero out a part of your disk =====

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If this is a vSphere VM you can then migrate the VM to NFS storage and back and the zero'd out data has been reclaimed.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>2c58598e015ce74a458fb3fd27b74ea146c8fcf7</sha1>
  </revision>
  <revision>
    <id>1444</id>
    <parentid>1440</parentid>
    <timestamp>2018-02-25T10:58:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4531" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

===== Zero out a part of your disk =====

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If this is a vSphere VM you can then migrate the VM to NFS storage and back and the zero'd out data has been reclaimed.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>e35d93739a465ea7427f53aedbd6c536cfea5a53</sha1>
  </revision>
  <revision>
    <id>1445</id>
    <parentid>1444</parentid>
    <timestamp>2018-02-25T11:03:50Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Important */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4678" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

===== Zero out a part of your disk =====

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If this is a vSphere VM you can then migrate the VM to NFS storage and back and the zero'd out data has been reclaimed.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>a97941bad33242a9451deca93a287ed745ef5276</sha1>
  </revision>
  <revision>
    <id>1446</id>
    <parentid>1445</parentid>
    <timestamp>2018-02-25T11:05:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Important */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4752" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

===== Zero out a part of your disk =====

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If this is a vSphere VM you can then migrate the VM to NFS storage and back and the zero'd out data has been reclaimed.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>d6d274f2fdd75aed01bd6de12f2d2753b1fbd5bc</sha1>
  </revision>
  <revision>
    <id>1447</id>
    <parentid>1446</parentid>
    <timestamp>2018-02-25T11:23:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Zero out a part of your disk */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4887" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

===== Zero out a part of your disk =====

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on vSphere and you have a NFS LUN then one way to reclaim your space is to storage VMOTION the VM to NFS storage and back and the zero'd out data has been reclaimed. No need to shut down the VM. If this is not for you, then read on.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>b5db0a2f2bce562a5021a8b3ed30b54cb9b0cb63</sha1>
  </revision>
  <revision>
    <id>1448</id>
    <parentid>1447</parentid>
    <timestamp>2018-02-25T11:26:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Zero out a part of your disk */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4929" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

===== Zero out a part of your disk =====

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>77b4866f8b8f1c9b7d155223ec67620f35733582</sha1>
  </revision>
  <revision>
    <id>1449</id>
    <parentid>1448</parentid>
    <timestamp>2018-02-27T13:08:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Important */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6359" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.


==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

===== Zero out a part of your disk =====

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>5a3314c321a4d1937c8705d3c47ab397d932e934</sha1>
  </revision>
  <revision>
    <id>1450</id>
    <parentid>1449</parentid>
    <timestamp>2018-02-27T13:14:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* How much free space do you need before shrinking? */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6784" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 14 then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) but I'm not sure that that works for Linux guests.

==== Zero out unused space in a Linux VM ====

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

===== Zero out a part of your disk =====

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

==== Zero out unused space on a Windows VM ====

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

=== Shrink the disk ===

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

=== Shrink using vmware tools ===

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>4ac16e36402c5c31932424e9bcb0122e98429908</sha1>
  </revision>
  <revision>
    <id>1451</id>
    <parentid>1450</parentid>
    <timestamp>2018-02-27T13:15:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6768" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 14 then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) but I'm not sure that that works for Linux guests.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your disk ===

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>cba9a4220ec2142f726f015624402c6617cc4d8c</sha1>
  </revision>
  <revision>
    <id>1452</id>
    <parentid>1451</parentid>
    <timestamp>2018-02-27T13:17:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Using the clean up option in the menu */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6794" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 14 then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your disk ===

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>b6c07a60470effa24ec6f6220fb026fe00b5ace9</sha1>
  </revision>
  <revision>
    <id>1453</id>
    <parentid>1452</parentid>
    <timestamp>2018-02-27T13:19:02Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Using the clean up option in the menu */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6804" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your disk ===

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /</text>
    <sha1>af9d4c9db58b1f3cff71b37134ce839d307aac08</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>Vmkfstools</title>
  <ns>0</ns>
  <id>572</id>
  <revision>
    <id>1425</id>
    <parentid>1406</parentid>
    <timestamp>2016-12-21T14:28:36Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* punchzero */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6630" xml:space="preserve">Command for directly working with the (virtual) disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks. 
Beware that if you are working with a virtual disk that in most cases the virtual machine itself should be shut down.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
==== Export a VM disk ====
Export a VM disk in 2GB chunks, note that since [[Esxcli#enable_2GB_Sparse_disks|ESXi 5.1+ the 2GB sparse driver is disabled]].
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk

==== Check or repair a disk ====
 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

==== Set a UUID ====
 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.

==== dumpfs ====
dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 # vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
==== activehosts ==== 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

Example:
 # vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86
==== punchzero ====
Since vSphere 5.1 there's an option to shrink disks besides the normally required storage vmotion.

With the guest shut down you can run vmkfstools with the punchzero option. 

Reclaim disk space by returning unused blocks of data in the virtual disk to the host OS. 

Note that this will only work if your virtual disk is of type thin.


Before running it you will also need to zero out the unused blocks of data in the guest OS.

For a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].
Run it as
 sdelete -z c:
Note that the -z option is needed as of sdelete version 1.6

For a linux based VM, run a command like:
 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill
to zero out the unused space. 

Note of warning that you should stop database -and other disk intensive- services before running the above.

Some more detailed descriptions and tips on zero-ing out data from your guest OS can be found at [Shrink guest on hosted platform]


Example:
 # vmkfstools --punchzero disk.vmdk
 vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 
 Hole Punching: 3% done.


After you're done and list the VM from within the console, it looks like nothing has changed, in this example the disk is 10GB in size.
 # ls -lh *.vmdk
 -rw-------    1 root     root       10.0G Nov 27 20:58 disk-flat.vmdk
 -rw-------    1 root     root         527 Nov 27 21:02 disk.vmdk

If you use the command du however then you can see the difference:
 # du -hs *.vmdk
 4.3G    disk-flat.vmdk
 0       disk.vmdk

You can also use the vSphere Client data browser to see the effect of reclaiming disk space.

If you try to run this command against a VM living on NFS storage you might end up seeing the following error:
 vmkfstools --punchzero myvmdk.vmdk
 Not a supported filesystem type

The error is a bit confusing as you might expect vmkfstools to talk about the guest OS here, but it is actually reporting that NFS does not support the punchzero option. 

Your solution is to either move the vmdk by hand to storage not located on VMFS or use storage vmotion to migrate to non NFS storage. On moving using storage vmotion, the zero data is already being discarded. So you can just storage vmotion back afterwards and you have reclaimed the lost disk space.

=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>fcb4e34795e06a82a52779e4540bebfe7df3b955</sha1>
  </revision>
  <revision>
    <id>1426</id>
    <parentid>1425</parentid>
    <timestamp>2016-12-21T14:29:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* punchzero */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6632" xml:space="preserve">Command for directly working with the (virtual) disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks. 
Beware that if you are working with a virtual disk that in most cases the virtual machine itself should be shut down.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
==== Export a VM disk ====
Export a VM disk in 2GB chunks, note that since [[Esxcli#enable_2GB_Sparse_disks|ESXi 5.1+ the 2GB sparse driver is disabled]].
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk

==== Check or repair a disk ====
 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

==== Set a UUID ====
 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.

==== dumpfs ====
dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 # vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
==== activehosts ==== 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

Example:
 # vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86
==== punchzero ====
Since vSphere 5.1 there's an option to shrink disks besides the normally required storage vmotion.

With the guest shut down you can run vmkfstools with the punchzero option. 

Reclaim disk space by returning unused blocks of data in the virtual disk to the host OS. 

Note that this will only work if your virtual disk is of type thin.


Before running it you will also need to zero out the unused blocks of data in the guest OS.

For a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].
Run it as
 sdelete -z c:
Note that the -z option is needed as of sdelete version 1.6

For a linux based VM, run a command like:
 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill
to zero out the unused space. 

Note of warning that you should stop database -and other disk intensive- services before running the above.

Some more detailed descriptions and tips on zero-ing out data from your guest OS can be found at [[Shrink guest on hosted platform]]


Example:
 # vmkfstools --punchzero disk.vmdk
 vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 
 Hole Punching: 3% done.


After you're done and list the VM from within the console, it looks like nothing has changed, in this example the disk is 10GB in size.
 # ls -lh *.vmdk
 -rw-------    1 root     root       10.0G Nov 27 20:58 disk-flat.vmdk
 -rw-------    1 root     root         527 Nov 27 21:02 disk.vmdk

If you use the command du however then you can see the difference:
 # du -hs *.vmdk
 4.3G    disk-flat.vmdk
 0       disk.vmdk

You can also use the vSphere Client data browser to see the effect of reclaiming disk space.

If you try to run this command against a VM living on NFS storage you might end up seeing the following error:
 vmkfstools --punchzero myvmdk.vmdk
 Not a supported filesystem type

The error is a bit confusing as you might expect vmkfstools to talk about the guest OS here, but it is actually reporting that NFS does not support the punchzero option. 

Your solution is to either move the vmdk by hand to storage not located on VMFS or use storage vmotion to migrate to non NFS storage. On moving using storage vmotion, the zero data is already being discarded. So you can just storage vmotion back afterwards and you have reclaimed the lost disk space.

=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>83e3a38f679325d1f202f846d272c53d12cb4b54</sha1>
  </revision>
  <revision>
    <id>1430</id>
    <parentid>1426</parentid>
    <timestamp>2017-02-16T15:40:11Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* activehosts */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6809" xml:space="preserve">Command for directly working with the (virtual) disk at host level.

With this command you can destroy whole virtual machines if you do not take the right precautions (hint: BACKUPS) and are not familiar with the command.

 
=== Usage ===
 vmkfstools [options] target

Whereby target can be either a physical disk, a virtual disk or a device.

The command is mostly known for using it to manipulate virtual disks. 
Beware that if you are working with a virtual disk that in most cases the virtual machine itself should be shut down.

=== Options ===
from the help page of the command.
====OPTIONS FOR FILE SYSTEMS ====
 
 vmkfstools -C --createfs [vmfs3|vmfs5]
               -b --blocksize #[mMkK]
               -S --setfsname fsName
           -Z --spanfs span-partition
           -G --growfs grown-partition
   deviceName

           -P --queryfs -h --humanreadable
           -T --upgradevmfs
   vmfsPath
 
====OPTIONS FOR VIRTUAL DISKS====
 
 vmkfstools -c --createvirtualdisk #[gGmMkK]
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick]
               -a --adaptertype [buslogic|lsilogic|ide|
                                 lsisas|pvscsi]
           -w --writezeros
           -j --inflatedisk
           -k --eagerzero
           -K --punchzero
           -U --deletevirtualdisk
           -E --renamevirtualdisk srcDisk
           -i --clonevirtualdisk srcDisk
               -d --diskformat [zeroedthick|
                                thin|
                                eagerzeroedthick|
                                rdm:&lt;device&gt;|rdmp:&lt;device&gt;|
                                2gbsparse]
           -X --extendvirtualdisk #[gGmMkK]
               [-d --diskformat eagerzeroedthick]
           -M --migratevirtualdisk
           -r --createrdm /vmfs/devices/disks/...
           -q --queryrdm
           -z --createrdmpassthru /vmfs/devices/disks/...
           -v --verbose #
           -g --geometry
           -x --fix [check|repair]
           -e --chainConsistent
   vmfsPath
 
====OPTIONS FOR DEVICES====
 
           -L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|rea                              dresv] /vmfs/devices/disks/...
           -B --breaklock /vmfs/devices/disks/...
 
 vmkfstools -H --help


=== Examples ===
==== Export a VM disk ====
Export a VM disk in 2GB chunks, note that since [[Esxcli#enable_2GB_Sparse_disks|ESXi 5.1+ the 2GB sparse driver is disabled]].
 vmkfstools -i /vmfs/volumes/storagename/YourVM/YourVM.vmdk -d 2gbsparse /vmfs/volumes/storage2/YourVM/YourVM.vmdk

==== Check or repair a disk ====
 -x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Example:
 vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
 Disk is error free

==== Set a UUID ====
 -J, --miscop [setuuid | getuuid]
'setuuid´ option creates a unique identifier (UUID) for the virtual disk and stores the UUID in the descriptor file of the
 virtual disk. If the descriptor file already contains a UUID, it will be overwritten with a new one. 

Please make sure that the virtual disk does not have a UUID before using this option.

´getuuid´ option displays the UUID of the virtual disk.

==== dumpfs ====
dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.

Example:
 # vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/
 
 Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
 gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
 Addr &lt;4, 0, 0&gt;, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
 len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576
==== activehosts ==== 
activehosts can be used by specifying "--activehosts" and specifying a VMFS volume

Example:
 # vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
 Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
 (1): MAC address 00:50:56:92:3f:86

Displays the MAC address of the management interface of each host which is currently using the datastore.

This is also what vSphere HA uses to see if a host is still active.

==== punchzero ====
Since vSphere 5.1 there's an option to shrink disks besides the normally required storage vmotion.

With the guest shut down you can run vmkfstools with the punchzero option. 

Reclaim disk space by returning unused blocks of data in the virtual disk to the host OS. 

Note that this will only work if your virtual disk is of type thin.


Before running it you will also need to zero out the unused blocks of data in the guest OS.

For a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].
Run it as
 sdelete -z c:
Note that the -z option is needed as of sdelete version 1.6

For a linux based VM, run a command like:
 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill
to zero out the unused space. 

Note of warning that you should stop database -and other disk intensive- services before running the above.

Some more detailed descriptions and tips on zero-ing out data from your guest OS can be found at [[Shrink guest on hosted platform]]


Example:
 # vmkfstools --punchzero disk.vmdk
 vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 
 Hole Punching: 3% done.


After you're done and list the VM from within the console, it looks like nothing has changed, in this example the disk is 10GB in size.
 # ls -lh *.vmdk
 -rw-------    1 root     root       10.0G Nov 27 20:58 disk-flat.vmdk
 -rw-------    1 root     root         527 Nov 27 21:02 disk.vmdk

If you use the command du however then you can see the difference:
 # du -hs *.vmdk
 4.3G    disk-flat.vmdk
 0       disk.vmdk

You can also use the vSphere Client data browser to see the effect of reclaiming disk space.

If you try to run this command against a VM living on NFS storage you might end up seeing the following error:
 vmkfstools --punchzero myvmdk.vmdk
 Not a supported filesystem type

The error is a bit confusing as you might expect vmkfstools to talk about the guest OS here, but it is actually reporting that NFS does not support the punchzero option. 

Your solution is to either move the vmdk by hand to storage not located on VMFS or use storage vmotion to migrate to non NFS storage. On moving using storage vmotion, the zero data is already being discarded. So you can just storage vmotion back afterwards and you have reclaimed the lost disk space.

=== Links ===

[http://blogs.vmware.com/vsphere/2012/08/some-useful-vmkfstools-hidden-options.html Some useful vmkfstools ‘hidden’ options]

[http://www.virtuallyghetto.com/2010/07/vsphere-41-is-gift-that-keeps-on-giving.html William also has a list here]</text>
    <sha1>76becacf9dabb36e74c2fa4583b0fd7c542ce32b</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>DOS</title>
  <ns>0</ns>
  <id>578</id>
  <revision>
    <id>1432</id>
    <timestamp>2017-05-29T17:40:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "When creating a virtual machine with MS DOS (or PC Dos) then you'll notice that there are a few issues.  The first major issue being that the VM will run one of your cores wit..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="521" xml:space="preserve">When creating a virtual machine with MS DOS (or PC Dos) then you'll notice that there are a few issues.

The first major issue being that the VM will run one of your cores with a high CPU.
The reason being that MS DOS did not idle your CPU when it wasn't doing nothing, so instead of having a VM that uses no CPU when not doing anything you have that 1 core going nuts.

The classical way to resolve that is by installing DosIdle.

As it doesn't appear to be available much, here's a copy.

[DosIdle.zip DosIdle download]</text>
    <sha1>f4819d2e759c6fb3fd4534d2491d7f66f46dc52e</sha1>
  </revision>
  <revision>
    <id>1434</id>
    <parentid>1432</parentid>
    <timestamp>2017-05-29T18:20:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="572" xml:space="preserve">When creating a virtual machine with MS DOS (or PC Dos) then you'll notice that there are a few issues.

The first major issue being that the VM will run one of your cores with a high CPU.
The reason being that MS DOS did not idle your CPU when it wasn't doing nothing, so instead of having a VM that uses no CPU when not doing anything you have that 1 core going nuts.

The classical way to resolve that is by installing DosIdle.

As it doesn't appear to be available much, here's a copy.

[https://wiki.vi-toolkit.com/images/f/f2/DOS-Drivers.zip Dos Drivers download]</text>
    <sha1>e1331c003d00a430248d166ae265fbfecf7b4c87</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>File:DOS-Drivers.zip</title>
  <ns>6</ns>
  <id>579</id>
  <revision>
    <id>1433</id>
    <timestamp>2017-05-29T18:19:54Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>This zip contains:

cdrom.img -- Installer for CD-ROM drivers

dosidle.img -- Makes MS-DOS not consume 100% CPU.

wqghlt.img -- Like DOSIDLE, for Windows 3.1

SB16Win3x.iso -- CD image installer for Sound Blaster 16</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="215" xml:space="preserve">This zip contains:

cdrom.img -- Installer for CD-ROM drivers

dosidle.img -- Makes MS-DOS not consume 100% CPU.

wqghlt.img -- Like DOSIDLE, for Windows 3.1

SB16Win3x.iso -- CD image installer for Sound Blaster 16</text>
    <sha1>f28c0846618bc3279bec2c999b217002ea05be4f</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>Build guest vmware kernel modules</title>
  <ns>0</ns>
  <id>573</id>
  <revision>
    <id>1437</id>
    <parentid>1382</parentid>
    <timestamp>2017-10-26T10:10:51Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* The solution */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4154" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /mnt/cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently available:
* vmhgfs - shared folders
* vmxnet3 - virtual network adapter
* vmmemctl - memory
* vmw_balloon - balloon memory driver
* vmw_pvscsi - paravirtual scsi
* vmwgfx - accelerated graphics
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* vmsync -
* vgauth - Guest Authentication
* vmw_vmci - inter-VM and host interface
* vmw_vsock_vmci_transport - 
* vsock - virtual sockets

Interesting tidbit, the reason that there's a "vmw_" prefix means it is VMware only and if there's no prefix, like vsock, then it is because it is a hypervisor-independent interface. See [https://communities.vmware.com/thread/497086 (1)] for details

There's also a number of additional commands/scripts to enable other features
* /usr/bin/vmware-toolbox-cmd - shrink, upgrade, statistics, version, timesync, run scripts on power operations, power operations, control devices
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste. Running this will start the vmtoolsd daemon in /usr/lib/vmware-tools/sbin64
* /usr/lib/vmware-tools/sbin64/vmware-checkvm - prints VMware software version
* /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader option --install-all will actually build all of your modules as well.
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>508301ffdef320d9f56065651d2f72bbe4916785</sha1>
  </revision>
  <revision>
    <id>1438</id>
    <parentid>1437</parentid>
    <timestamp>2017-10-26T15:13:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Troubleshooting */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5709" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /mnt/cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====

===== available kernel modules =====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently available:
* vmhgfs - shared folders
* vmxnet3 - virtual network adapter
* vmmemctl - memory
* vmw_balloon - balloon memory driver
* vmw_pvscsi - paravirtual scsi
* vmwgfx - accelerated graphics
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* vmsync -
* vgauth - Guest Authentication
* vmw_vmci - inter-VM and host interface
* vmw_vsock_vmci_transport - 
* vsock - virtual sockets

Interesting tidbit, the reason that there's a "vmw_" prefix means it is VMware only and if there's no prefix, like vsock, then it is because it is a hypervisor-independent interface. See [https://communities.vmware.com/thread/497086 (1)] for details

There's also a number of additional commands/scripts to enable other features
* /usr/bin/vmware-toolbox-cmd - shrink, upgrade, statistics, version, timesync, run scripts on power operations, power operations, control devices
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste. Running this will start the vmtoolsd daemon in /usr/lib/vmware-tools/sbin64
* /usr/lib/vmware-tools/sbin64/vmware-checkvm - prints VMware software version
* /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader option --install-all will actually build all of your modules as well.
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

===== unable to start services for VMware Tools =====

 Creating a new initrd boot image for the kernel.
 
 NOTE: both /etc/vmware-tools/GuestProxyData/server/key.pem and
       /etc/vmware-tools/GuestProxyData/server/cert.pem already exist.
       They are not generated again. To regenerate them by force,
       use the "vmware-guestproxycerttool -g -f" command.
 
 initctl: Job failed to start
 Unable to start services for VMware Tools
 
 Execution aborted.

If you get the above error then you can probably do as is sugggested above. I simply nuked the folder /etc/vmware-tools/GuestProxyData (rm -rf ) and completely reran the installer, after that it worked.

===== vgauth what? =====

Nowadays VMware Tools asks if you want to enable the CAF agent (Common Agent Framework agent).

If you are like me then you are probably wondering what this is.

At the forums there's an answer ( https://communities.vmware.com/message/2604183#2604183 by VMware employee ykzang)

I'm quoting that here for ease of reading.


''Multiple VMware management solutions (e.g. vCM, Hyperic, Log Insight) require  installation of in-guest agents.The Common Agent Framework attempts to provide a common framework to unify and simplify the management of various types of agents, and these agents would be referred to as Common Agent.


Those VMware solutions are working on distinct administrative domains from the guest. VGAuth provides a way to authorize those solutions users' behaviors(install agent for example) within guest.''

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>da923328b2f21aeb3acfc6af8bc758040f1e904f</sha1>
  </revision>
  <revision>
    <id>1439</id>
    <parentid>1438</parentid>
    <timestamp>2017-10-26T15:13:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* vgauth what? */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5713" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /mnt/cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====

===== available kernel modules =====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently available:
* vmhgfs - shared folders
* vmxnet3 - virtual network adapter
* vmmemctl - memory
* vmw_balloon - balloon memory driver
* vmw_pvscsi - paravirtual scsi
* vmwgfx - accelerated graphics
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* vmsync -
* vgauth - Guest Authentication
* vmw_vmci - inter-VM and host interface
* vmw_vsock_vmci_transport - 
* vsock - virtual sockets

Interesting tidbit, the reason that there's a "vmw_" prefix means it is VMware only and if there's no prefix, like vsock, then it is because it is a hypervisor-independent interface. See [https://communities.vmware.com/thread/497086 (1)] for details

There's also a number of additional commands/scripts to enable other features
* /usr/bin/vmware-toolbox-cmd - shrink, upgrade, statistics, version, timesync, run scripts on power operations, power operations, control devices
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste. Running this will start the vmtoolsd daemon in /usr/lib/vmware-tools/sbin64
* /usr/lib/vmware-tools/sbin64/vmware-checkvm - prints VMware software version
* /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader option --install-all will actually build all of your modules as well.
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

===== unable to start services for VMware Tools =====

 Creating a new initrd boot image for the kernel.
 
 NOTE: both /etc/vmware-tools/GuestProxyData/server/key.pem and
       /etc/vmware-tools/GuestProxyData/server/cert.pem already exist.
       They are not generated again. To regenerate them by force,
       use the "vmware-guestproxycerttool -g -f" command.
 
 initctl: Job failed to start
 Unable to start services for VMware Tools
 
 Execution aborted.

If you get the above error then you can probably do as is sugggested above. I simply nuked the folder /etc/vmware-tools/GuestProxyData (rm -rf ) and completely reran the installer, after that it worked.

===== vgauth what? =====

Nowadays VMware Tools asks if you want to enable the CAF agent (Common Agent Framework agent).

If you are like me then you are probably wondering what this is.

At the forums there's an answer ( https://communities.vmware.com/message/2604183#2604183 by VMware employee ykzang)

I'm quoting that here for ease of reading.


''Multiple VMware management solutions (e.g. vCM, Hyperic, Log Insight) require  installation of in-guest agents.The Common Agent Framework attempts to provide a common framework to unify and simplify the management of various types of agents, and these agents would be referred to as Common Agent.''


''Those VMware solutions are working on distinct administrative domains from the guest. VGAuth provides a way to authorize those solutions users' behaviors(install agent for example) within guest.''

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>d02e212abe959321ffc9e759b65ae94c32479a17</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>Ray Heffer visio stencils</title>
  <ns>0</ns>
  <id>580</id>
  <revision>
    <id>1441</id>
    <timestamp>2018-01-22T22:24:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "===  Ray Heffer Visio Stencils === author: Ray Heffer ==== Description ==== This is the 2nd version of his Visio Stenciles for VMware EUC.   ===== Direct download =====  [http..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="462" xml:space="preserve">===  Ray Heffer Visio Stencils ===
author: Ray Heffer
==== Description ====
This is the 2nd version of his Visio Stenciles for VMware EUC.


===== Direct download =====

[https://www.dropbox.com/s/5pzqqtf94bcat9r/VMware%20EUC%20Visio%20Stencils%202018.rar?dl=1 VMware EUC Visio Stencils 2018 (RAR)]

==== Location ====

For more info please see his website at:

https://www.rayheffer.com/vmware-visio-stencils-powerpoint-icons-2018/

[[Category: VMware Artwork]]</text>
    <sha1>4ad2edc16b36ff862292960e85b8a7b80e23cdfe</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>ESXi vSphere mount LUN problems</title>
  <ns>0</ns>
  <id>581</id>
  <revision>
    <id>1442</id>
    <timestamp>2018-02-12T15:27:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "=== cannot connect to LUN === Sometimes the correct LUN does not show up and trying to mount it only gives an option to format the LUN.  * 1. Log in as root to the ESX host wh..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3289" xml:space="preserve">=== cannot connect to LUN ===
Sometimes the correct LUN does not show up and trying to mount it only gives an option to format the LUN.

* 1. Log in as root to the ESX host which cannot mount the datastore using an SSH client.
* 2. Run the command:
 esxcfg-volume -l

The results appear similar to:

 VMFS3 UUID/label: 4b057ec3-6bd10428-b37c-005056ab552a/ TestDS
 Can mount: Yes
 Can resignature:  No (the volume is being actively used)
 Extent name: naa.6000eb391530aa26000000000000130c:1 range: 0 – 1791 (MB)

Record the UUID portion of the output. In the above example the UUID is 4b057ec3-6bd10428-b37c-005056ab552a.

Note: The Can mount value must be Yes to proceed with this workaround.

* 3. Run the command:
 esxcfg-volume -M &lt;UUID&gt;

Where the &lt;UUID&gt; is the value recorded in step 2.

or you can just use the label:
 esxcfg-volume -M TestDS


=== adding a new NFS LUN from the CLI ===

First list what is there:
 esxcli storage nfs list

Then add:
  esxcli storage nfs add -v NEWLUN -H 1.2.3.4 -s /mnt/newstorage
where NEWLUN is the label, -H is the host

=== adding iSCSI LUN back ===

disable snapshot LUN

 # esxcfg-advcfg -s 0 /LVM/DisallowSnapshotLun
 Value of DisallowSnapshotLun is 0
Then rescan the lot
 # esxcli storage core adapter rescan --all
 # vmkfstools -V
 # esxcli storage vmfs snapshot list
restore the default for your snapshot
 # esxcfg-advcfg -s 1 /LVM/DisallowSnapshotLun
 Value of DisallowSnapshotLun is 1
 # esxcfg-volume -l
 # df -h

The snapshot list and volumes show no results for me, but on df -h after the above commands, the ISCSI mount now shows up at the host.

 [https://kb.vmware.com/kb/2129058 vSAN handling of devices detected as snapshots (2129058)]

=== Adding a host to an NFS datastore in the VCSA errors out ===

Trying to add another host to a NFS datastore errors out and generates the error "Failed: An error occurred during host configuration".
The host should be able to connect to the NFS storage as it is allowed from the NFS server.

Digging deeper on this error gives "Operation failed, diagnostics report: Unable to get console path for volume"

In my case the host had mounted this NFS LUN before under a slightly different name and as such a now obsolete pointer somewhere was preventing the host from connecting to the LUN.

You can fix it from the CLI as follows:

First make sure the LUN isn't in the output of the following command:
 # esxcfg-nas -l

If that's not the case then proceed and try to add the LUN from the CLI.
If your host is 10.0.0.5 and the NFS share on it is /mnt/vol/share which you want to mount as MYLUN then add like
 # esxcfg-nas -a -o 10.0.0.5 -s /mnt/vol/share MYLUN
  Error performing operation: Unable to add new NAS, volume with the label MYLUN already exists
Here the vSphere server is indeed complaining that MYLUN exists.
Run:
 # df -h
and verify that it is NOT in the list.
After that test you can remove the LUN
 # esxcfg-nas -d MYLUN
 IORM: failed to disable IORM: Unable to get console path for volume, MYLUN
 NAS volume MYLUN deleted.
Now you can rerun the above command:
 # esxcfg-nas -a -o 10.0.0.5 -s /mnt/vol/share MYLUN
 Connecting to NAS volume: MYLUN
 MYLUN created and connected.

=== iSCSI shows as normal, degraded ===

In vSphere 6.5 this happens when you have only 1 uplink.</text>
    <sha1>68b1256d13cdfe8b07127cf6026061dc0b631535</sha1>
  </revision>
  <revision>
    <id>1443</id>
    <parentid>1442</parentid>
    <timestamp>2018-02-12T15:32:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>forgot to categorize</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3309" xml:space="preserve">=== cannot connect to LUN ===
Sometimes the correct LUN does not show up and trying to mount it only gives an option to format the LUN.

* 1. Log in as root to the ESX host which cannot mount the datastore using an SSH client.
* 2. Run the command:
 esxcfg-volume -l

The results appear similar to:

 VMFS3 UUID/label: 4b057ec3-6bd10428-b37c-005056ab552a/ TestDS
 Can mount: Yes
 Can resignature:  No (the volume is being actively used)
 Extent name: naa.6000eb391530aa26000000000000130c:1 range: 0 – 1791 (MB)

Record the UUID portion of the output. In the above example the UUID is 4b057ec3-6bd10428-b37c-005056ab552a.

Note: The Can mount value must be Yes to proceed with this workaround.

* 3. Run the command:
 esxcfg-volume -M &lt;UUID&gt;

Where the &lt;UUID&gt; is the value recorded in step 2.

or you can just use the label:
 esxcfg-volume -M TestDS


=== adding a new NFS LUN from the CLI ===

First list what is there:
 esxcli storage nfs list

Then add:
  esxcli storage nfs add -v NEWLUN -H 1.2.3.4 -s /mnt/newstorage
where NEWLUN is the label, -H is the host

=== adding iSCSI LUN back ===

disable snapshot LUN

 # esxcfg-advcfg -s 0 /LVM/DisallowSnapshotLun
 Value of DisallowSnapshotLun is 0
Then rescan the lot
 # esxcli storage core adapter rescan --all
 # vmkfstools -V
 # esxcli storage vmfs snapshot list
restore the default for your snapshot
 # esxcfg-advcfg -s 1 /LVM/DisallowSnapshotLun
 Value of DisallowSnapshotLun is 1
 # esxcfg-volume -l
 # df -h

The snapshot list and volumes show no results for me, but on df -h after the above commands, the ISCSI mount now shows up at the host.

 [https://kb.vmware.com/kb/2129058 vSAN handling of devices detected as snapshots (2129058)]

=== Adding a host to an NFS datastore in the VCSA errors out ===

Trying to add another host to a NFS datastore errors out and generates the error "Failed: An error occurred during host configuration".
The host should be able to connect to the NFS storage as it is allowed from the NFS server.

Digging deeper on this error gives "Operation failed, diagnostics report: Unable to get console path for volume"

In my case the host had mounted this NFS LUN before under a slightly different name and as such a now obsolete pointer somewhere was preventing the host from connecting to the LUN.

You can fix it from the CLI as follows:

First make sure the LUN isn't in the output of the following command:
 # esxcfg-nas -l

If that's not the case then proceed and try to add the LUN from the CLI.
If your host is 10.0.0.5 and the NFS share on it is /mnt/vol/share which you want to mount as MYLUN then add like
 # esxcfg-nas -a -o 10.0.0.5 -s /mnt/vol/share MYLUN
  Error performing operation: Unable to add new NAS, volume with the label MYLUN already exists
Here the vSphere server is indeed complaining that MYLUN exists.
Run:
 # df -h
and verify that it is NOT in the list.
After that test you can remove the LUN
 # esxcfg-nas -d MYLUN
 IORM: failed to disable IORM: Unable to get console path for volume, MYLUN
 NAS volume MYLUN deleted.
Now you can rerun the above command:
 # esxcfg-nas -a -o 10.0.0.5 -s /mnt/vol/share MYLUN
 Connecting to NAS volume: MYLUN
 MYLUN created and connected.

=== iSCSI shows as normal, degraded ===

In vSphere 6.5 this happens when you have only 1 uplink.

[[Category: ESXi]]</text>
    <sha1>88a3d10fe9aed2686ecee131a72d0bd64e7d4faa</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>Vmware-checkvm</title>
  <ns>0</ns>
  <id>582</id>
  <revision>
    <id>1454</id>
    <timestamp>2018-05-05T20:01:56Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "== vmware-checkvm ==  The vmware-checkvm command is part of vmware-tools and allows you to check some vmware properties about your VM.  When run without parameters it returns..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1365" xml:space="preserve">== vmware-checkvm ==

The vmware-checkvm command is part of vmware-tools and allows you to check some vmware properties about your VM.

When run without parameters it returns the software version, from the looks of it, it returns the host major version number.
Eg. vSphere 6.5 returns "VMware software version 6 (good)"

What is probably more interesting though is that it also returns if we are running (return value is 0) or not (return value is 1). If VMware tools is installed on a physical host it will return "Not running in a virtual machine." with return value 1.

You can run the command without privileges.

There are also some parameters you can use, but all of them are undocumented.

=== Parameters ===

The following parameters can be used:

* r - return screensize in width x height. 
Eg.
 vmware-checkvm -r
 1024 768
for a screensize of 1024 pixels wide and 768 pixels heigh.

* p - print out product that it is running on. Not all host types are recognized, known values are:
 ESX Server
 Workstation
 Unknown

Eg.
 vmware-checkvm -p
 ESX Server

* h - hardware version, this is the virtual hardware that the virtual machine is running.
Eg.
 vmware-checkvm -h
 VM's hw version is 4
 

=== External Links ===

https://github.com/vmware/open-vm-tools/tree/master/open-vm-tools/checkvm


[[Category: CLI]] [[Category: bash]] [[Category: vmware-tools]]</text>
    <sha1>c711a300381ba6d7262c708d492549f9f37c6b65</sha1>
  </revision>
</page>
<page arvcontinue="20161109212552|1407">
  <title>Category:Vmware-tools</title>
  <ns>14</ns>
  <id>583</id>
  <revision>
    <id>1455</id>
    <timestamp>2018-05-05T20:07:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "Category that lists vmware tools related topics."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48" xml:space="preserve">Category that lists vmware tools related topics.</text>
    <sha1>a5436466bfeec64d572be6563a6c6fa5d83068e9</sha1>
  </revision>
  <revision>
    <id>1456</id>
    <parentid>1455</parentid>
    <timestamp>2018-05-05T21:44:44Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="180" xml:space="preserve">Category that lists vmware tools related topics.

There's an official documentation PDF from VMware about command line options here: 
http://www.vmware.com/pdf/vmware-tools-cli.pdf</text>
    <sha1>215e102d76c97692a1db62fe3fad1c3bbbe70d40</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>VSphere SOAP</title>
  <ns>0</ns>
  <id>584</id>
  <revision>
    <id>1457</id>
    <timestamp>2019-01-23T21:44:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with " Blog post by Tony Ganchev  * [https://blog.tonyganchev.com/accessing-vsphere-soap-apis-from-c/ Accessing vSphere SOAP APIs from C++]   [[Category: C++]] Category: vSphere A..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="197" xml:space="preserve">
Blog post by Tony Ganchev

* [https://blog.tonyganchev.com/accessing-vsphere-soap-apis-from-c/ Accessing vSphere SOAP APIs from C++]


[[Category: C++]]
[[Category: vSphere API]]
[[Category: SDK]]</text>
    <sha1>4b7ceb07aa1bd04e0ef3d2ad7a5e77f08f141414</sha1>
  </revision>
  <revision>
    <id>1458</id>
    <parentid>1457</parentid>
    <timestamp>2019-01-23T21:46:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="205" xml:space="preserve">
Blog post by Tony Ganchev

* [https://blog.tonyganchev.com/accessing-vsphere-soap-apis-from-c/ Accessing vSphere SOAP APIs from C++]


[[Category: C++]]
[[Category: vSphere API]]
[[Category: vSphere SDK]]</text>
    <sha1>9a7724a3035e3595f966fec6e0c5c245302bbbb6</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Vmrun</title>
  <ns>0</ns>
  <id>470</id>
  <revision>
    <id>1459</id>
    <parentid>1398</parentid>
    <timestamp>2019-02-05T11:21:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Command line help contents */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9415" xml:space="preserve">vmrun is a command line utility that can be used to run certain automation tasks easily.
It is easy to make it part of a script and do things like start a particular VM, create a snapshot, run a program in the guest, etcetera.


==== Limitations while running the VM in the GUI ====
There are some things you can't do things while the VM is open in the UI, but other things should work.

Things you can do:
* Power off the VM
* Suspend the VM
* Create a snapshot 
* Revert to a snapshot (need to verify)
* Pause and unpause the VM
* Power on the VM using the 'gui' option
* Perform guest operations (runProgramInGuest, listDirectoryInGuest, etc.)
* Start and stop recording
* Mount the Tools installer
* Run any vProbes commands
* Change the shared folder settings (add, remove, enable) of a running VM.

Things you cannot do:
* Upgrade the VM's virtual hardware
* Power on the VM using the 'nogui' option 
* Change the shared folder settings (add, remove, enable) of a powered off or suspended VM

==== Command line help contents ====
Output VMware Workstation 12.01 help of vmrun
  C:\Program Files (x86)\VMware\VMware Workstation\vmrun
  
  vmrun version 1.15.1 build-3160714
  
  Usage: vmrun [AUTHENTICATION-FLAGS] COMMAND [PARAMETERS]
  
  
  AUTHENTICATION-FLAGS
  --------------------
  These must appear before the command and any command parameters.
  
     -h &lt;hostName&gt;  (not needed for Workstation)
     -P &lt;hostPort&gt;  (not needed for Workstation)
     -T &lt;hostType&gt; (ws|server|server1|fusion|esx|vc|player)
       for example, use '-T server' for Server 2.0
                    use '-T server1' for Server 1.0
                    use '-T ws' for VMware Workstation
                    use '-T ws-shared' for VMware Workstation (shared mode)
                    use '-T esx' for VMware ESX
                    use '-T vc' for VMware vCenter Server
     -u &lt;userName in host OS&gt;  (not needed for Workstation)
     -p &lt;password in host OS&gt;  (not needed for Workstation)
     -vp &lt;password for encrypted virtual machine&gt;
     -gu &lt;userName in guest OS&gt;
     -gp &lt;password in guest OS&gt;
  
  
  POWER COMMANDS           PARAMETERS           DESCRIPTION
  --------------           ----------           -----------
  start                    Path to vmx file     Start a VM or Team
                           [gui|nogui]
  
  stop                     Path to vmx file     Stop a VM or Team
                           [hard|soft]
  
  reset                    Path to vmx file     Reset a VM or Team
                           [hard|soft]
  
  suspend                  Path to vmx file     Suspend a VM or Team
                           [hard|soft]
  
  pause                    Path to vmx file     Pause a VM
  
  unpause                  Path to vmx file     Unpause a VM
  
  
  SNAPSHOT COMMANDS        PARAMETERS           DESCRIPTION
  -----------------        ----------           -----------
  listSnapshots            Path to vmx file     List all snapshots in a VM
                           [showTree]
  
  snapshot                 Path to vmx file     Create a snapshot of a VM
                           Snapshot name
  
  deleteSnapshot           Path to vmx file     Remove a snapshot from a VM
                           Snapshot name
                           [andDeleteChildren]
  
  revertToSnapshot         Path to vmx file     Set VM state to a snapshot
                           Snapshot name
  
  
  GUEST OS COMMANDS        PARAMETERS           DESCRIPTION
  -----------------        ----------           -----------
  runProgramInGuest        Path to vmx file     Run a program in Guest OS
                           [-noWait]
                           [-activeWindow]
                           [-interactive]
                           Complete-Path-To-Program
                           [Program arguments]
  
  fileExistsInGuest        Path to vmx file     Check if a file exists in Guest OS
  
                           Path to file in guest
  
  directoryExistsInGuest   Path to vmx file     Check if a directory exists in Guest OS
                           Path to directory in guest
  
  setSharedFolderState     Path to vmx file     Modify a Host-Guest shared folder
                           Share name
                           Host path
                           writable | readonly
  
  addSharedFolder          Path to vmx file     Add a Host-Guest shared folder
                           Share name
                           New host path
  
  removeSharedFolder       Path to vmx file     Remove a Host-Guest shared folder
                           Share name
  
  enableSharedFolders      Path to vmx file     Enable shared folders in Guest
                           [runtime]
  
  disableSharedFolders     Path to vmx file     Disable shared folders in Guest
                           [runtime]
  
  listProcessesInGuest     Path to vmx file     List running processes in Guest OS
  
  
  killProcessInGuest       Path to vmx file     Kill a process in Guest OS
                           process id
  
  runScriptInGuest         Path to vmx file     Run a script in Guest OS
                           [-noWait]
                           [-activeWindow]
                           [-interactive]
                           Interpreter path
                           Script text
  
  deleteFileInGuest        Path to vmx file     Delete a file in Guest OS
  Path in guest
  
  createDirectoryInGuest   Path to vmx file     Create a directory in Guest OS
  Directory path in guest
  
  deleteDirectoryInGuest   Path to vmx file     Delete a directory in Guest OS
  Directory path in guest
  
  CreateTempfileInGuest    Path to vmx file     Create a temporary file in Guest OS
  
  listDirectoryInGuest     Path to vmx file     List a directory in Guest OS
                           Directory path in guest
  
  CopyFileFromHostToGuest  Path to vmx file     Copy a file from host OS to guest OS
  Path on host             Path in guest
  
  
  CopyFileFromGuestToHost  Path to vmx file     Copy a file from guest OS to host OS
  Path in guest            Path on host
  
  
  renameFileInGuest        Path to vmx file     Rename a file in Guest OS
                           Original name
                           New name
  
  captureScreen            Path to vmx file     Capture the screen of the VM to a local file
  Path on host
  
  writeVariable            Path to vmx file     Write a variable in the VM state
                           [runtimeConfig|guestEnv|guestVar]
                           variable name
                           variable value
  
  readVariable             Path to vmx file     Read a variable in the VM state
                           [runtimeConfig|guestEnv|guestVar]
                           variable name
  
  getGuestIPAddress        Path to vmx file     Gets the IP address of the guest
                           [-wait]
  
  
  GENERAL COMMANDS         PARAMETERS           DESCRIPTION
  ----------------         ----------           -----------
  list                                          List all running VMs
  
  upgradevm                Path to vmx file     Upgrade VM file format, virtual hw
  
  
  installTools             Path to vmx file     Install Tools in Guest
  
  checkToolsState          Path to vmx file     Check the current Tools state
  
  register                 Path to vmx file     Register a VM
  
  unregister               Path to vmx file     Unregister a VM
  
  listRegisteredVM                              List registered VMs
  
  deleteVM                 Path to vmx file     Delete a VM
  
  clone                    Path to vmx file     Create a copy of the VM
                           Path to destination vmx file
                           full|linked
                           [-snapshot=Snapshot Name]
                           [-cloneName=Name]
 
  
  Examples:
 
  Starting a virtual machine with Workstation on a Windows host
     vmrun -T ws start "c:\my VMs\myVM.vmx"
  
  Stopping a virtual machine on an ESX host
     vmrun -T esx -h https://myHost.com/sdk -u hostUser -p hostPassword stop "[storage1] vm/myVM.vmx"
  
  Running a program in a virtual machine with Workstation on a Windows host with Windows guest
     vmrun -T ws -gu guestUser -gp guestPassword runProgramInGuest "c:\my VMs\myVM.vmx" "c:\Program Files\myProgram.exe"
  
  Running a program in a virtual machine with Server on a Linux host with Linux guest
     vmrun -T server -h https://myHost.com:8333/sdk -u hostUser -p hostPassword -gu guestUser -gp guestPassword runProgramInGuest "[standard] vm/myVM.vmx" /usr/bin/X11/xclock -display :0
  
  Creating a snapshot of a virtual machine with Workstation on a Windows host
     vmrun -T ws snapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Reverting to a snapshot with Workstation on a Windows host
     vmrun -T ws revertToSnapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Deleting a snapshot with Workstation on a Windows host
     vmrun -T ws deleteSnapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Enabling Shared Folders with Workstation on a Windows host
     vmrun -T ws enableSharedFolders "c:\my VMs\myVM.vmx"

==== External links ====

[https://www.vmware.com/support/developer/vix-api/vix112_vmrun_command.pdf vmrun commands (pdf)]

[https://www.vmware.com/support/developer/vix-api/ VMware VIX-API]

[[Category: VIX]]</text>
    <sha1>522b289e1c4a225f70286500ce4a2659e894938b</sha1>
  </revision>
  <revision>
    <id>1501</id>
    <parentid>1459</parentid>
    <timestamp>2020-12-13T01:05:33Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* External links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9578" xml:space="preserve">vmrun is a command line utility that can be used to run certain automation tasks easily.
It is easy to make it part of a script and do things like start a particular VM, create a snapshot, run a program in the guest, etcetera.


==== Limitations while running the VM in the GUI ====
There are some things you can't do things while the VM is open in the UI, but other things should work.

Things you can do:
* Power off the VM
* Suspend the VM
* Create a snapshot 
* Revert to a snapshot (need to verify)
* Pause and unpause the VM
* Power on the VM using the 'gui' option
* Perform guest operations (runProgramInGuest, listDirectoryInGuest, etc.)
* Start and stop recording
* Mount the Tools installer
* Run any vProbes commands
* Change the shared folder settings (add, remove, enable) of a running VM.

Things you cannot do:
* Upgrade the VM's virtual hardware
* Power on the VM using the 'nogui' option 
* Change the shared folder settings (add, remove, enable) of a powered off or suspended VM

==== Command line help contents ====
Output VMware Workstation 12.01 help of vmrun
  C:\Program Files (x86)\VMware\VMware Workstation\vmrun
  
  vmrun version 1.15.1 build-3160714
  
  Usage: vmrun [AUTHENTICATION-FLAGS] COMMAND [PARAMETERS]
  
  
  AUTHENTICATION-FLAGS
  --------------------
  These must appear before the command and any command parameters.
  
     -h &lt;hostName&gt;  (not needed for Workstation)
     -P &lt;hostPort&gt;  (not needed for Workstation)
     -T &lt;hostType&gt; (ws|server|server1|fusion|esx|vc|player)
       for example, use '-T server' for Server 2.0
                    use '-T server1' for Server 1.0
                    use '-T ws' for VMware Workstation
                    use '-T ws-shared' for VMware Workstation (shared mode)
                    use '-T esx' for VMware ESX
                    use '-T vc' for VMware vCenter Server
     -u &lt;userName in host OS&gt;  (not needed for Workstation)
     -p &lt;password in host OS&gt;  (not needed for Workstation)
     -vp &lt;password for encrypted virtual machine&gt;
     -gu &lt;userName in guest OS&gt;
     -gp &lt;password in guest OS&gt;
  
  
  POWER COMMANDS           PARAMETERS           DESCRIPTION
  --------------           ----------           -----------
  start                    Path to vmx file     Start a VM or Team
                           [gui|nogui]
  
  stop                     Path to vmx file     Stop a VM or Team
                           [hard|soft]
  
  reset                    Path to vmx file     Reset a VM or Team
                           [hard|soft]
  
  suspend                  Path to vmx file     Suspend a VM or Team
                           [hard|soft]
  
  pause                    Path to vmx file     Pause a VM
  
  unpause                  Path to vmx file     Unpause a VM
  
  
  SNAPSHOT COMMANDS        PARAMETERS           DESCRIPTION
  -----------------        ----------           -----------
  listSnapshots            Path to vmx file     List all snapshots in a VM
                           [showTree]
  
  snapshot                 Path to vmx file     Create a snapshot of a VM
                           Snapshot name
  
  deleteSnapshot           Path to vmx file     Remove a snapshot from a VM
                           Snapshot name
                           [andDeleteChildren]
  
  revertToSnapshot         Path to vmx file     Set VM state to a snapshot
                           Snapshot name
  
  
  GUEST OS COMMANDS        PARAMETERS           DESCRIPTION
  -----------------        ----------           -----------
  runProgramInGuest        Path to vmx file     Run a program in Guest OS
                           [-noWait]
                           [-activeWindow]
                           [-interactive]
                           Complete-Path-To-Program
                           [Program arguments]
  
  fileExistsInGuest        Path to vmx file     Check if a file exists in Guest OS
  
                           Path to file in guest
  
  directoryExistsInGuest   Path to vmx file     Check if a directory exists in Guest OS
                           Path to directory in guest
  
  setSharedFolderState     Path to vmx file     Modify a Host-Guest shared folder
                           Share name
                           Host path
                           writable | readonly
  
  addSharedFolder          Path to vmx file     Add a Host-Guest shared folder
                           Share name
                           New host path
  
  removeSharedFolder       Path to vmx file     Remove a Host-Guest shared folder
                           Share name
  
  enableSharedFolders      Path to vmx file     Enable shared folders in Guest
                           [runtime]
  
  disableSharedFolders     Path to vmx file     Disable shared folders in Guest
                           [runtime]
  
  listProcessesInGuest     Path to vmx file     List running processes in Guest OS
  
  
  killProcessInGuest       Path to vmx file     Kill a process in Guest OS
                           process id
  
  runScriptInGuest         Path to vmx file     Run a script in Guest OS
                           [-noWait]
                           [-activeWindow]
                           [-interactive]
                           Interpreter path
                           Script text
  
  deleteFileInGuest        Path to vmx file     Delete a file in Guest OS
  Path in guest
  
  createDirectoryInGuest   Path to vmx file     Create a directory in Guest OS
  Directory path in guest
  
  deleteDirectoryInGuest   Path to vmx file     Delete a directory in Guest OS
  Directory path in guest
  
  CreateTempfileInGuest    Path to vmx file     Create a temporary file in Guest OS
  
  listDirectoryInGuest     Path to vmx file     List a directory in Guest OS
                           Directory path in guest
  
  CopyFileFromHostToGuest  Path to vmx file     Copy a file from host OS to guest OS
  Path on host             Path in guest
  
  
  CopyFileFromGuestToHost  Path to vmx file     Copy a file from guest OS to host OS
  Path in guest            Path on host
  
  
  renameFileInGuest        Path to vmx file     Rename a file in Guest OS
                           Original name
                           New name
  
  captureScreen            Path to vmx file     Capture the screen of the VM to a local file
  Path on host
  
  writeVariable            Path to vmx file     Write a variable in the VM state
                           [runtimeConfig|guestEnv|guestVar]
                           variable name
                           variable value
  
  readVariable             Path to vmx file     Read a variable in the VM state
                           [runtimeConfig|guestEnv|guestVar]
                           variable name
  
  getGuestIPAddress        Path to vmx file     Gets the IP address of the guest
                           [-wait]
  
  
  GENERAL COMMANDS         PARAMETERS           DESCRIPTION
  ----------------         ----------           -----------
  list                                          List all running VMs
  
  upgradevm                Path to vmx file     Upgrade VM file format, virtual hw
  
  
  installTools             Path to vmx file     Install Tools in Guest
  
  checkToolsState          Path to vmx file     Check the current Tools state
  
  register                 Path to vmx file     Register a VM
  
  unregister               Path to vmx file     Unregister a VM
  
  listRegisteredVM                              List registered VMs
  
  deleteVM                 Path to vmx file     Delete a VM
  
  clone                    Path to vmx file     Create a copy of the VM
                           Path to destination vmx file
                           full|linked
                           [-snapshot=Snapshot Name]
                           [-cloneName=Name]
 
  
  Examples:
 
  Starting a virtual machine with Workstation on a Windows host
     vmrun -T ws start "c:\my VMs\myVM.vmx"
  
  Stopping a virtual machine on an ESX host
     vmrun -T esx -h https://myHost.com/sdk -u hostUser -p hostPassword stop "[storage1] vm/myVM.vmx"
  
  Running a program in a virtual machine with Workstation on a Windows host with Windows guest
     vmrun -T ws -gu guestUser -gp guestPassword runProgramInGuest "c:\my VMs\myVM.vmx" "c:\Program Files\myProgram.exe"
  
  Running a program in a virtual machine with Server on a Linux host with Linux guest
     vmrun -T server -h https://myHost.com:8333/sdk -u hostUser -p hostPassword -gu guestUser -gp guestPassword runProgramInGuest "[standard] vm/myVM.vmx" /usr/bin/X11/xclock -display :0
  
  Creating a snapshot of a virtual machine with Workstation on a Windows host
     vmrun -T ws snapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Reverting to a snapshot with Workstation on a Windows host
     vmrun -T ws revertToSnapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Deleting a snapshot with Workstation on a Windows host
     vmrun -T ws deleteSnapshot "c:\my VMs\myVM.vmx" mySnapshot
  
  Enabling Shared Folders with Workstation on a Windows host
     vmrun -T ws enableSharedFolders "c:\my VMs\myVM.vmx"

==== External links ====

[https://www.vmware.com/support/developer/vix-api/vix112_vmrun_command.pdf vmrun commands (pdf)]

[https://www.vmware.com/support/developer/vix-api/ VMware VIX-API]

[https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-24F54E24-EFB0-4E94-8A07-2AD791F0E497.html Syntax vmrun command in VMware Fusion 12]

[[Category: VIX]]</text>
    <sha1>f630fff43a4c8512409c81886caa32f7f9071e6f</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Resources</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>1460</id>
    <parentid>1412</parentid>
    <timestamp>2019-02-05T11:37:32Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>removing dead link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2011" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [http://blogs.vmware.com/developer VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the VI Toolkit ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.vinternals.com/ vinternals blog, home of statelesx]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>2479d209ef323fb0dc5bca9d12d246f2c938dc6a</sha1>
  </revision>
  <revision>
    <id>1461</id>
    <parentid>1460</parentid>
    <timestamp>2019-02-05T11:39:04Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>removing dead link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1945" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [http://blogs.vmware.com/developer VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://communities.vmware.com/community/developer/utilities VMware Community Sample Code forum]

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the vSphere API ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>8c21fc20bfc7f7564034138e18787c2bd92ba1c8</sha1>
  </revision>
  <revision>
    <id>1462</id>
    <parentid>1461</parentid>
    <timestamp>2019-02-05T11:43:07Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>removing dead link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1845" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [http://blogs.vmware.com/developer VMware Developer center blog]

* [https://developercenter.vmware.com/home VMware Developer center home]

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the vSphere API ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>556603838da472718f80c1d5264c432a716dd817</sha1>
  </revision>
  <revision>
    <id>1463</id>
    <parentid>1462</parentid>
    <timestamp>2019-02-05T11:43:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Dev center now points to {code} home, link is redundant</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1771" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [http://blogs.vmware.com/developer VMware Developer center blog]

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the vSphere API ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>f5be75478fb36e9561dba2e907691cf8dfa4e933</sha1>
  </revision>
  <revision>
    <id>1464</id>
    <parentid>1463</parentid>
    <timestamp>2019-02-05T11:45:57Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Update dev blog link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1823" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [https://blogs.vmware.com/code/ VMware Developer center blog] (old link is [http://blogs.vmware.com/developer here])

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [http://www.virtuallyghetto.com Virtually Ghetto - William Lam and Tuan Duong's VMware ESX/ESXi Shell and Perl scripts &amp; Resources]

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the vSphere API ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>ccd9c27b1f95f06619d05f08896f42b30c258b5f</sha1>
  </revision>
  <revision>
    <id>1514</id>
    <parentid>1464</parentid>
    <timestamp>2021-06-07T14:05:30Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Fixing link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1776" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [https://blogs.vmware.com/code/ VMware Developer center blog] (old link is [http://blogs.vmware.com/developer here])

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [https://williamlam.com/ William Lam's blog] (formerly known as virtuallyghetto.com)

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the vSphere API ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>3cef5361ccddb1d1203146305e1f52751094f39d</sha1>
  </revision>
  <revision>
    <id>1515</id>
    <parentid>1514</parentid>
    <timestamp>2021-06-07T14:08:03Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VMware Developer targeted sites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1862" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [https://blogs.vmware.com/code/ VMware Developer center blog] (old link is [http://blogs.vmware.com/developer here])

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [https://communities.vmware.com/t5/VMware-code/ct-p/4500-home VMware {code} forum]

* [http://communities.vmware.com/community/developer/codecentral VMware code central] VMware Community Sample Code

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [https://williamlam.com/ William Lam's blog] (formerly known as virtuallyghetto.com)

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the vSphere API ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>acc3c18d2a7a605a3c74c9a9022ddbcc662a66e8</sha1>
  </revision>
  <revision>
    <id>1516</id>
    <parentid>1515</parentid>
    <timestamp>2021-06-07T14:10:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* VMware Developer targeted sites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1894" xml:space="preserve">==== VMware Developer targeted sites ====

* [http://blogs.vmware.com/PowerCLI/ VMware PowerCLI blog]

* [https://blogs.vmware.com/code/ VMware Developer center blog] (old link is [http://blogs.vmware.com/developer here])

* [https://code.vmware.com VMware {code}] and [https://twitter.com/vmwarecode @vmwarecode twitter feed]

* [https://communities.vmware.com/t5/VMware-code/ct-p/4500-home VMware {code} forum]

* [https://communities.vmware.com/t5/Sample-Exchange-Discussions/bd-p/4502 VMware {code} sample exchange discussions] VMware Community Sample Code

* [http://libraries.io/search?page=1&amp;q=vmware Libraries.io VMware pages]

==== Sites with code ====
Places to visit for information, scripts, code snippets and tools (usually) with source code.

* [http://powerscripting.net/ Powershell powerscripting.net]

* [https://sites.google.com/site/chitchatvmback/ Ken Kato VMware's Back]

* [http://sanbarrow.com sanbarrow site]

* [https://williamlam.com/ William Lam's blog] (formerly known as virtuallyghetto.com)

* [http://www.astroarch.com/ Edward Haletky's site]

* [http://www.vm-help.com/index.html Dave Mishchenko's ESX host help site] ( you need it )

* [http://www.vmwarescripting.com/ VMwarescripting.com forum]

==== Must read Blogs about Powershell and the vSphere API ====

* [http://www.virtu-al.net Virtu-Al blog]

* [http://lucd.info Luc D's notes]

* [http://www.peetersonline.nl/index.php/powershell/some-advice-on-creating-powershell-scripts/ peetersonline powershell scripts]

* [http://ict-freak.nl/ ICT-Freak.nl]

* [http://www.van-lieshout.com Arnim van Lieshout]

* [http://jonathanmedd.net/ Jonathan Medd's blog]

* [http://www.ntpro.nl/blog/categories/10-VMware-PowerShell NTPRO Powershell]

==== Interesting Blogs ====

* [http://www.yellow-bricks.com/ Duncan Epping's Yellow Bricks]

* [http://www.planetvm.net/ Tom Howarth's Planet VM]

[[Category: website]]</text>
    <sha1>16e69d195bc97b12faf060e24bce6a82de57ef2e</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Shrink guest on hosted platform</title>
  <ns>0</ns>
  <id>577</id>
  <revision>
    <id>1465</id>
    <parentid>1453</parentid>
    <timestamp>2019-02-11T22:51:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Shrink using vmware tools */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6921" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your disk ===

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]</text>
    <sha1>258c632d4b6a58cc1070189f8aded64e5d601552</sha1>
  </revision>
  <revision>
    <id>1466</id>
    <parentid>1465</parentid>
    <timestamp>2019-05-22T17:10:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Shrink using vmware tools */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7044" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space. 

Clean up your repositories:

For example, on Debian-based VMs, you can run

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

Then shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run:

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your disk ===

If your machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]</text>
    <sha1>4d39a360775f2758a3cc80c520df41a97c5914b9</sha1>
  </revision>
  <revision>
    <id>1467</id>
    <parentid>1466</parentid>
    <timestamp>2019-07-02T15:53:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added a few more words to indicate that these commands are to be run from within the VM</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7385" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]</text>
    <sha1>7dc9c15ff60aa6edf966ba0a5f8a8eff2e753e4a</sha1>
  </revision>
  <revision>
    <id>1489</id>
    <parentid>1467</parentid>
    <timestamp>2020-03-12T23:02:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>added a note to look at the vmdk file ownership after shrinking via the command line.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7773" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]</text>
    <sha1>b32fa86c38be1be49dd6abec62b60719bae6cab1</sha1>
  </revision>
  <revision>
    <id>1503</id>
    <parentid>1489</parentid>
    <timestamp>2021-04-15T22:24:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Note about zero'ing out an encrypted disk</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8150" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]</text>
    <sha1>949eaa044042e84fc7b9fdab8058493ab94bb4a6</sha1>
  </revision>
  <revision>
    <id>1504</id>
    <parentid>1503</parentid>
    <timestamp>2021-04-15T22:30:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>adding links to the official doc of VMware Workstation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8597" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]</text>
    <sha1>207fff388669d29f1d0f3dca4cdeadeb1757292c</sha1>
  </revision>
  <revision>
    <id>1505</id>
    <parentid>1504</parentid>
    <timestamp>2021-04-15T22:39:01Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>and for Fusion</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8823" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run:

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>75762b50d1b9a46f85f62380d8d56c5ec88f8a37</sha1>
  </revision>
  <revision>
    <id>1517</id>
    <parentid>1505</parentid>
    <timestamp>2021-08-09T13:35:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added an example of the shrinking process in progress and listing the RDP side effect that I am seeing here.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9370" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run (as administrator):

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

For example:
 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink c:\
 Please disregard any warnings about disk space for the duration of shrink process.
 Progress: 62 [=======&gt;   ]
The progress you see here is VMware Tools blanking out the unused space.

At 99% it will popup the "Shrinking Disk" progress dialog at the host that takes care of the actual shrinking process.

If you are logged in via remote desktop then do expect to loose the connection for a bit while the actual shrinking is taking place.

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>787f9da85aafd83bff4a6881f2eecd087b1ccf79</sha1>
  </revision>
  <revision>
    <id>1523</id>
    <parentid>1517</parentid>
    <timestamp>2021-10-12T22:12:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Zero out a part of your virtual disk */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9662" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

=== Zero out using fstrim ===

These days there's an alternative way for zero-ing out the parts of the disk that are not used using fstrim.

The great thing about this is that it only zero's out the parts of the disk that are not zero and as such the disk does not inflate to its full size.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run (as administrator):

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

For example:
 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink c:\
 Please disregard any warnings about disk space for the duration of shrink process.
 Progress: 62 [=======&gt;   ]
The progress you see here is VMware Tools blanking out the unused space.

At 99% it will popup the "Shrinking Disk" progress dialog at the host that takes care of the actual shrinking process.

If you are logged in via remote desktop then do expect to loose the connection for a bit while the actual shrinking is taking place.

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>7e71909e7eb8b8ebca73715927fae421b14cd9f5</sha1>
  </revision>
  <revision>
    <id>1524</id>
    <parentid>1523</parentid>
    <timestamp>2021-10-12T22:14:49Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Zero out using fstrim */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9720" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

=== Zero out using fstrim ===

These days there's an alternative way for zero-ing out the parts of the disk that are not used using [https://www.man7.org/linux/man-pages/man8/fstrim.8.html fstrim].

The great thing about this is that it only zero's out the parts of the disk that are not zero and as such the disk does not inflate to its full size.

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run (as administrator):

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

For example:
 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink c:\
 Please disregard any warnings about disk space for the duration of shrink process.
 Progress: 62 [=======&gt;   ]
The progress you see here is VMware Tools blanking out the unused space.

At 99% it will popup the "Shrinking Disk" progress dialog at the host that takes care of the actual shrinking process.

If you are logged in via remote desktop then do expect to loose the connection for a bit while the actual shrinking is taking place.

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>37c9b2e54a304e0857f3157daf936620a76e980d</sha1>
  </revision>
  <revision>
    <id>1525</id>
    <parentid>1524</parentid>
    <timestamp>2021-10-12T22:23:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Zero out using fstrim */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9847" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

=== Zero out using fstrim ===

These days there's an alternative way for zero-ing out the parts of the disk that are not used using [https://www.man7.org/linux/man-pages/man8/fstrim.8.html fstrim].

The great thing about this is that it only zero's out the parts of the disk that are not zero and as such the disk does not inflate to its full size.

[https://forums.freebsd.org/threads/ssd-trim-maintenance.56951/post-328912 Detail comment from Theodore Ts'o on using fstrim]

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run (as administrator):

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

For example:
 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink c:\
 Please disregard any warnings about disk space for the duration of shrink process.
 Progress: 62 [=======&gt;   ]
The progress you see here is VMware Tools blanking out the unused space.

At 99% it will popup the "Shrinking Disk" progress dialog at the host that takes care of the actual shrinking process.

If you are logged in via remote desktop then do expect to loose the connection for a bit while the actual shrinking is taking place.

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>643f07f3473f292eb990809f803ec62a1b9413a4</sha1>
  </revision>
  <revision>
    <id>1526</id>
    <parentid>1525</parentid>
    <timestamp>2021-10-12T23:15:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Zero out using fstrim */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9965" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

=== Zero out using fstrim ===

These days there's an alternative way for zero-ing out the parts of the disk that are not used using [https://www.man7.org/linux/man-pages/man8/fstrim.8.html fstrim].

The great thing about this is that it only zero's out the parts of the disk that are not zero and as such the disk does not inflate to its full size.

* [https://forums.freebsd.org/threads/ssd-trim-maintenance.56951/post-328912 Detail comment from Theodore Ts'o on using fstrim]

* [https://github.com/vmware/open-vm-tools/issues/457 Avoid disk expansion while shrinking (github issue tracker)]

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root.

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run (as administrator):

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

For example:
 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink c:\
 Please disregard any warnings about disk space for the duration of shrink process.
 Progress: 62 [=======&gt;   ]
The progress you see here is VMware Tools blanking out the unused space.

At 99% it will popup the "Shrinking Disk" progress dialog at the host that takes care of the actual shrinking process.

If you are logged in via remote desktop then do expect to loose the connection for a bit while the actual shrinking is taking place.

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>ad0e7721b2d448b5e1887c7f3a3e159a177fb7ab</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>VMware Icons</title>
  <ns>0</ns>
  <id>423</id>
  <revision>
    <id>1468</id>
    <parentid>1193</parentid>
    <timestamp>2019-12-07T19:16:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* VMware Icons */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="568" xml:space="preserve">==== VMware Icons ====

VMware icons and powerpoint backgrounds that you can use in your own products.
Please do check out the guidelines as well.

http://communities.vmware.com/blogs/DeveloperCenter/2009/02/19/vmware-icons

PS: The powerpoints seem to have moved to:
http://viops.vmware.com/home/docs/DOC-1338

The icons can now be found here: http://communities.vmware.com/docs/DOC-9441

Correction, when VIOPS moved, the powerpoints have disappeared.

The most recent visio icons are here: https://communities.vmware.com/docs/DOC-38595

[[Category: VMware Artwork]]</text>
    <sha1>0cbe2ddd2a2c4b4e91c1ce7547427f447ccc1c89</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>VIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>1490</id>
    <parentid>1285</parentid>
    <timestamp>2020-07-24T14:25:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1321" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

Supported on VMware Workstation 6.0.x and up, VMware Server 1.x and up, VMware ESX3.5U2+

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX 1.1 API reference Guide]

[http://www.vmware.com/support/developer/vix-api/vix16_reference/ VMware VIX 1.6 API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

[http://www.virtuallyghetto.com/2013/07/whitepaper-migrating-from-vix-api-to.html Whitepaper: Migrating From VIX API to the vSphere Guest Operations API]

Download. The link for the API page no longer offers a working download (strange)

This one however works, but you do need to login: [https://my.vmware.com/web/vmware/details?productId=492&amp;downloadGroup=VIXAPI114 VMware VIX 1.14] it is probably better to install VMware Workstation Professional which bundles VMware VIX.

==== Presentations ====

[[VIX API Tech Talk Partner Exchange]]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Vix Java Toolkit]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>5645bf2c46c8ef8f0b4885e4a2049a625d1bb6d7</sha1>
  </revision>
  <revision>
    <id>1491</id>
    <parentid>1490</parentid>
    <timestamp>2020-07-25T09:37:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1660" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

Supported on VMware Workstation 6.0.x and up, VMware Server 1.x and up, VMware ESX3.5U2+

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX 1.1 API reference Guide]

[http://www.vmware.com/support/developer/vix-api/vix16_reference/ VMware VIX 1.6 API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

[http://www.virtuallyghetto.com/2013/07/whitepaper-migrating-from-vix-api-to.html Whitepaper: Migrating From VIX API to the vSphere Guest Operations API]

==== Download ====
The link for the API page no longer offers a working download (strange)

These however works, but you do need to login:
* [https://my.vmware.com/web/vmware/details?productId=492&amp;downloadGroup=VIXAPI114 VMware VIX 1.14] 
* [https://download3.vmware.com/software/player/file/VMware-VIX-1.17.0-6661328.x86_64.bundle VMware VIX 1.17 (linux)]

However you might have problems installing. 

If you do then it is probably better to install VMware Workstation Professional which bundles VMware VIX and installs it on your behalf. 

VMware Workstation has VMware Player as well and Player will continue to work after the Professional trial runs out.

==== Presentations ====

[[VIX API Tech Talk Partner Exchange]]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Vix Java Toolkit]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>51b1bbabe4646f5fe6595c85cd230a19c822ba5b</sha1>
  </revision>
  <revision>
    <id>1492</id>
    <parentid>1491</parentid>
    <timestamp>2020-07-25T09:39:53Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Download */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1774" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

Supported on VMware Workstation 6.0.x and up, VMware Server 1.x and up, VMware ESX3.5U2+

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX 1.1 API reference Guide]

[http://www.vmware.com/support/developer/vix-api/vix16_reference/ VMware VIX 1.6 API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

[http://www.virtuallyghetto.com/2013/07/whitepaper-migrating-from-vix-api-to.html Whitepaper: Migrating From VIX API to the vSphere Guest Operations API]

==== Download ====
The link for the API page no longer offers a working download (strange)

These however works, but you do need to login:
* [https://my.vmware.com/web/vmware/details?productId=492&amp;downloadGroup=VIXAPI114 VMware VIX 1.14] 
* [https://download3.vmware.com/software/player/file/VMware-VIX-1.17.0-6661328.x86_64.bundle VMware VIX 1.17 (linux x64)]
* [https://download3.vmware.com/software/player/file/VMware-VIX-1.17.0-6661328.exe VMware VIX 1.17 (Windows)]

However you might have problems installing. 

If you do then it is probably better to install VMware Workstation Professional which bundles VMware VIX and installs it on your behalf. 

VMware Workstation has VMware Player as well and Player will continue to work after the Professional trial runs out.

==== Presentations ====

[[VIX API Tech Talk Partner Exchange]]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Vix Java Toolkit]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>b688f1a51aaeb1de89b4f55d4f8361ffecce5ab3</sha1>
  </revision>
  <revision>
    <id>1498</id>
    <parentid>1492</parentid>
    <timestamp>2020-12-05T22:43:00Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>workaround for getting VIX on VMware Player installed</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2546" xml:space="preserve">VIX allows you to automate virtual machine operations and is the engine behind for example VMware's vmrun command.

Supported on VMware Workstation 6.0.x and up, VMware Server 1.x and up, VMware ESX3.5U2+

[http://www.vmware.com/support/developer/vix-api/ VMware VIX API page]

[http://pubs.vmware.com/vix-api/ReferenceGuide/ VMware VIX 1.1 API reference Guide]

[http://www.vmware.com/support/developer/vix-api/vix16_reference/ VMware VIX 1.6 API reference Guide]

[http://blogs.vmware.com/vix/ VMware VIX API Blog]

[http://www.vmware.com/pdf/vix162_vmrun_command.pdf vmrun commands (see also VIX API link above)]

[http://www.virtuallyghetto.com/2013/07/whitepaper-migrating-from-vix-api-to.html Whitepaper: Migrating From VIX API to the vSphere Guest Operations API]

==== Download ====
The link for the API page no longer offers a working download (strange)

These however works, but you do need to login:
* [https://my.vmware.com/web/vmware/details?productId=492&amp;downloadGroup=VIXAPI114 VMware VIX 1.14] 
* [https://download3.vmware.com/software/player/file/VMware-VIX-1.17.0-6661328.x86_64.bundle VMware VIX 1.17 (linux x64)]
* [https://download3.vmware.com/software/player/file/VMware-VIX-1.17.0-6661328.exe VMware VIX 1.17 (Windows)]

However you might have problems installing. 

A few notes, before VMware Workstation 16.x, on Windows you would need to install VIX manually for VMware Player.
For VMware Workstation Professional however it comes bundled with VMware VIX and installs it on your behalf. 

So for older versions of VMware Workstation, you can install Workstation and use VMware Player from that install. Player will even continue to work after the Professional trial runs out.

For VMware Workstation 16.x, on Windows hosts VIX is already installed for both VMware Workstation Professional as well as VMware Player.
It is also installed on Workstation for Linux afaik.

That leaves us with VMware Player 16.x on Linux hosts. It does not come with VIX pre-installed at this time.

Trying to install VIX 1.17 from above generates errors.
Apparently you can work around that [https://communities.vmware.com/t5/VMware-Workstation-Pro/Problem-installing-VMware-VIX-1-17-0/m-p/1847114/highlight/true#M109726 1] by renaming /usr/lib/vmware-installer into /usr/lib/vmware-installer_OFF (thanks Minir)

==== Presentations ====

[[VIX API Tech Talk Partner Exchange]]

==== 3rd party ====
[[JVix]]

[[pyVix]]

[[pyvmware]]

[[Rexx/Vix]]

[[VMWareTasks]]

[[vixCOMWrapper]]

[[Vix Java Toolkit]]

[[Category: VIX]] [[Category: SDK]]</text>
    <sha1>704215920cd76d3a6e470581450acbe12573f7e2</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1493</id>
    <parentid>1402</parentid>
    <timestamp>2020-12-05T16:56:08Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Contribute / help out */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2966" xml:space="preserve">== VI Toolkit ==
==== Welcome ====
Welcome at our web site which contains information for developers and administrators about extending and managing your VMware virtual environments.&lt;br /&gt;
This includes everything from automation on virtual machines in VMware player up to managing your Virtual Infrastructure using the available Software Development Kits from VMware.

The focus is on trying to provide examples about the source code. (Yes this site is all about the code)&lt;br /&gt;
Over time this will hopefully include a repository of scripts and helpful snippets of code for you all.

On the scripts part, the site is mostly still a collection of links to what you can find on the net. But there's more...

Since January 3rd 2009, we now have a complete command reference to [[Vimsh]], the ''undocumented'' metashell for VMware ESX.

==== Contribute / help out ====
This was originally setup as an OPEN wiki site, but it is now required to sign up for editing as we got severely hit by spammers in the past.

We do encourage anyone to add their findings here, or to make corrections to any of the articles posted in here if you see something wrong. 
If you want to find out how to do this, then do have a look [[VI-Toolkit:Users| here]]

==== Statistics, search and navigation ====
There are currently [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages stored in our wiki database. Almost all of the pages are categorized, so using the [[Special:categories | categories landing page]] to navigate is a good way to quickly see what is currently available to you. 

As extra help, the categories are listed below as well.

==== Available Categories ====
&lt;categorytree mode=pages depth="0"&gt;.net&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Bash&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;CLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;ESXi&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Forensics&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Host Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Hypervisor&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Java&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Perl&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;PowerCLI&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Powershell&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Python&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;SDK&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VI-Toolkit&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VIX&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VM Management&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware Artwork&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;VMware OSS&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Vimsh&lt;/categorytree&gt;
&lt;categorytree mode=pages depth="0"&gt;Website&lt;/categorytree&gt;

I hope that you will enjoy the content posted down here!

-- &lt;br /&gt;
Wil

[[Category: website]]</text>
    <sha1>3bcc1359ede29f279ee80297c0cc01a98b979a06</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Vmx hacks</title>
  <ns>0</ns>
  <id>585</id>
  <revision>
    <id>1494</id>
    <timestamp>2020-12-05T17:15:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with " === VMX hacks ===  ==== Wait 5 seconds on booting ==== Wait 5 seconds on booting:  bios.bootDelay = "5000" Time is in milliseconds, change it accordingly. ==== Open BIOS sett..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18758" xml:space="preserve">
=== VMX hacks ===

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflecHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.</text>
    <sha1>d2790cc4657dcb830d0d1b1e84fc399fc5afae05</sha1>
  </revision>
  <revision>
    <id>1495</id>
    <parentid>1494</parentid>
    <timestamp>2020-12-05T17:31:35Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added a small introduction</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19429" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

I have _not_ removed any options that might be used to circumvent EULA's you have agreed with complying.

While I might not use these options myself, I'm still keeping them in here (at least for now, unless I get complaints).

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflecHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.</text>
    <sha1>033e0f5174a4ea064e977759a9c68f70850a0b8e</sha1>
  </revision>
  <revision>
    <id>1496</id>
    <parentid>1495</parentid>
    <timestamp>2020-12-05T17:36:31Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>it's actually fine, remove the EULA notice</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19202" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflecHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.</text>
    <sha1>f190401d61413f999d26f89c7fada6d776d7c2b0</sha1>
  </revision>
  <revision>
    <id>1497</id>
    <parentid>1496</parentid>
    <timestamp>2020-12-05T17:38:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19372" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflecHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>880cf4bf1870b97039c704a63c8bc0727adff6b4</sha1>
  </revision>
  <revision>
    <id>1506</id>
    <parentid>1497</parentid>
    <timestamp>2021-04-21T14:47:10Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Pass OS X host serial number */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19873" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841051 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflecHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>7d195dd5b6d6ffb7fcde697e5e6ae7537f6f41f6</sha1>
  </revision>
  <revision>
    <id>1507</id>
    <parentid>1506</parentid>
    <timestamp>2021-04-21T14:48:13Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Open file with host OS application */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19896" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflecHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>fd7c9dc0a3f719a967199df8f30dad443035bc40</sha1>
  </revision>
  <revision>
    <id>1518</id>
    <parentid>1507</parentid>
    <timestamp>2021-10-07T16:23:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19897" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>d81058e82a08d24eeb1f3b20541bc2c45d095fee</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Vctl</title>
  <ns>0</ns>
  <id>586</id>
  <revision>
    <id>1499</id>
    <timestamp>2020-12-10T01:16:15Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "== vctl ==  Both VMware Workstation as well as VMware Fusion nowadays have additional support to run and manage containers and the ability to run local kubernetes clusters.  =..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1297" xml:space="preserve">== vctl ==

Both VMware Workstation as well as VMware Fusion nowadays have additional support to run and manage containers and the ability to run local kubernetes clusters.

=== Official documentation === 

The official documentation has this:
* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-78E7339F-7294-4F3E-9AD0-1E14C201FA40.html VMware Workstation 16 - Using vctl Command to Manage Containers and Run Kubernetes Cluster]
* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-78E7339F-7294-4F3E-9AD0-1E14C201FA40.html VMware Fusion 12 - Using vctl Command to Manage Containers and Run Kubernetes Cluster]


=== github ===
Then there's the vctl doc over at github:

https://github.com/VMwareFusion/vctl-docs

With their getting started guide down here: https://github.com/VMwareFusion/vctl-docs/blob/master/docs/getting-started.md

Mike Roy also had some video shoots (one during vmworld, but he did another one.. let me see...)

Here's one: https://www.youtube.com/watch?v=LB8s3i6MCZE

VMware's Jeff Wu also wrote a piece about it here: https://medium.com/@jeff.wu.junfei/project-nautilus-a-new-container-runtime-d7c3574d2ae0

and perhaps this helps too:

https://rguske.github.io/post/a-closer-look-at-vmwares-project-nautilus/</text>
    <sha1>1370abb51c4db664c251270f947dbe2fbfa0b3d7</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Ovftool</title>
  <ns>0</ns>
  <id>587</id>
  <revision>
    <id>1500</id>
    <timestamp>2020-12-11T19:00:41Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "== Ovftool ==  Ovftool is a command line utility that you can run to import/export a VM which is following the OVF standards between different virtualisation products.  There'..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1225" xml:space="preserve">== Ovftool ==

Ovftool is a command line utility that you can run to import/export a VM which is following the OVF standards between different virtualisation products.

There's command line variations for most major operating systems including Windows, Linux and macOS.

This utility also comes bundled with vSphere, VMware Workstation and VMware Fusion. Each of those products provides a user interface for accessing this tool.

=== Command line example ===

Export a vSphere VM called "Pete" to ovf format on a Linux host to the current folder:
 ovftool vi://root@vspherehost.local.lan/Pete .
The ovftool command will prompt for the password that belongs to user "root" for host "vspherehost.local.lan".

This will create a folder "Pete" in your current folder with files that look like:
 # ls -alh Pete/
 total 2.3G
 drwxr-xr-x 2 root root 4.0K Dec 11 14:01 .
 drwxr-xr-x 4 root root 4.0K Dec 11 13:54 ..
 -rw-r--r-- 1 root root 2.3G Dec 11 14:01 Pete-disk1.vmdk
 -rw-r--r-- 1 root root 8.5K Dec 11 14:01 Pete-file1.nvram
 -rw-r--r-- 1 root root  273 Dec 11 14:01 Pete.mf
 -rw-r--r-- 1 root root 9.3K Dec 11 14:01 Pete.ovf


=== see also ===

https://code.vmware.com/web/tool/4.4.0/ovf

https://www.virtuallyghetto.com/ovf</text>
    <sha1>8b34ada9cf9bd2e4a7f03bd41465312c1373fbbf</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>DOS</title>
  <ns>0</ns>
  <id>578</id>
  <revision>
    <id>1502</id>
    <parentid>1434</parentid>
    <timestamp>2021-02-13T17:39:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Added a few relevant links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1027" xml:space="preserve">When creating a virtual machine with MS DOS (or PC Dos) then you'll notice that there are a few issues.

The first major issue being that the VM will run one of your cores with a high CPU.
The reason being that MS DOS did not idle your CPU when it wasn't doing nothing, so instead of having a VM that uses no CPU when not doing anything you have that 1 core going nuts.

The classical way to resolve that is by installing DosIdle.

As it doesn't appear to be available much, here's a copy.

[https://wiki.vi-toolkit.com/images/f/f2/DOS-Drivers.zip Dos Drivers download]

Other interesting notes for DOS users of VMware virtual machines:

* [https://communities.vmware.com/t5/VMware-Workstation-Pro-Documents/Sound-Blaster-16-on-VMware-Workstation-15-5-and-VMware-Fusion-11/ta-p/2781947 SoundBlaster 16 support] which has vastly improved thanks to Darius.

You also might want to check out Zamba's page here:

* http://www.scampers.org/steve/vmware/
and Ken Kato's pages here:

* https://sites.google.com/site/chitchatvmback/</text>
    <sha1>e50ecdbc4e61c0ad9501301ff01b29c6acafa8a7</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>PowerCLI: Change Virtual Machines Guest OS Names</title>
  <ns>0</ns>
  <id>546</id>
  <revision>
    <id>1508</id>
    <parentid>1260</parentid>
    <timestamp>2021-06-05T16:09:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Updated link to point to a copy at web.archive.org as the site is no longer there.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="636" xml:space="preserve">===  PowerCLI: Change Virtual Machines Guest OS Names ===
author: Rawlinson
==== Description ====
The script displayed here queries the VM name at the host level and will use that to set the name of the operating system within the guest OS. The example code here is used for windows guests.

==== Usage ====

Save as a script and run it.

==== Location ====

* [http://web.archive.org/web/20160616222335/http://www.punchingclouds.com/2013/06/06/powercli-change-virtual-machines-guest-os-names/ http://www.punchingclouds.com/2013/06/06/powercli-change-virtual-machines-guest-os-names/]

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>b708b2be805c93fc510af851d10b6ba0cb1b18af</sha1>
  </revision>
  <revision>
    <id>1509</id>
    <parentid>1508</parentid>
    <timestamp>2021-06-05T16:11:05Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Adding the code itself (just in case)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1221" xml:space="preserve">===  PowerCLI: Change Virtual Machines Guest OS Names ===
author: Rawlinson
==== Description ====
The script displayed here queries the VM name at the host level and will use that to set the name of the operating system within the guest OS. The example code here is used for windows guests.

==== Code ====

 $VMs = Get-VM | Where {$_.PowerState -eq "PoweredOn"} 
 
 Foreach ($VM in $VMS){
       $VCName = $VM.Name
       $WinName = $VM.Guest.Hostname
       If ($WinName -ne $VCName) {
             Write-Host "$VCName is currently $WinName... renaming"
             $renamecomputer = "wmic path win32_computersystem where ""Name='%computername%'"" CALL rename name='$VCName'"
             Invoke-VMScript -VM $VM -GuestUser "Administrator" -GuestPassword "vmware" -ScriptType Bat -ScriptText $renamecomputer
             restart-vmguest -VM $VM -Confirm:$false
       }
 }

==== Usage ====

Save as a script and run it.

==== Location ====

* [http://web.archive.org/web/20160616222335/http://www.punchingclouds.com/2013/06/06/powercli-change-virtual-machines-guest-os-names/ http://www.punchingclouds.com/2013/06/06/powercli-change-virtual-machines-guest-os-names/]

[[Category: PowerCLI]] [[Category: VM Management]]</text>
    <sha1>700482c2a86fe582c7bf8e90d7be269e0ae3534c</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Vitoolkit: Status</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>1510</id>
    <parentid>1320</parentid>
    <timestamp>2021-06-05T23:42:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Moved from /wiki folder to wiki subdomain earlier this week</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2551" xml:space="preserve">==== Status site ====

December 5, 2008: Initial setup

December 13, 2008: Full system backup, and added this page :)

Januari 1, 2009: Full system backup.


==== Things to do ====

Here's a list of things still to do, there's no time line as I don't want to put myself (or others) under stress.
This site is completely depending  on free time of its contributors so only work on it if you want to.

* &lt;s&gt; Add daily backup to another machine&lt;/s&gt; weekly is fine
* &lt;s&gt;Add proper category pages. Partly done &lt;/s&gt; 
* &lt;s&gt;Add "what's new" to the main page&lt;/s&gt; use [[Special:RecentChanges|Recent changes]] link at top of page instead.
* &lt;s&gt;Add # of articles/pages to the main page&lt;/s&gt;

* &lt;s&gt;Fix css for code snippets, it doesn't look like the current font is monospaced&lt;/s&gt;
* &lt;s&gt;Fix theme template / settings so that we can edit per paragraph as well&lt;/s&gt;
* Fix the silly html metatag redirection and use a proper 301 redirect
* &lt;s&gt;Redirect all alternative domain names to this site (like the .net and .org one, but especially the vitoolkit.com one)&lt;/s&gt;
* &lt;s&gt;Do email notifications work? (I think not)&lt;/s&gt;

* &lt;s&gt;Find a better way to present what's available on the site, improve ways to restructure the data. &lt;/s&gt; The support for category tree at the main page now gives a much easier way to navigate the site. But it never hurts to find better ways as this doesn't scale too well (look at the vimsh category for example)
* Improve main page
* Add example code
* &lt;s&gt;Add a theme for mobile phones, so it is easier to read the content&lt;/s&gt; Disabled the plugin as it was hopelessly out of date, I think the current theme is rather OK on mobile, but no phone to test now.

==== Things to make our mind up about ====

* Does the site need a forum? &lt;- No, you can use the talk page if you have a comment or contact me directly. Maybe in a later incarnation.
* Does the site need an instant messager type of control ? &lt;- No, use twitter @wilva for contacting me or use email wila under the site's domain name.
* Do we need a version code control system (my personal fav is [http://subversion.tigris.org/ subversion]) ? &lt;- No, we don't host much code on the site right now. Pretty much all of the code snippets are located elsewhere and copying those over to this site makes no sense as it will only complicate things.
* Do we need project tracking a la [http://trac.edgewall.org/ Trac] ? My impression is that at this stage it´s a bit over the top.
* &lt;s&gt;  Would it be better to change our url to https://wiki.vi-toolkit.com ? Probably ;) &lt;/s&gt; 

[[Category: website]]</text>
    <sha1>639f25402475937a1381a622577a4050be518fc4</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Protecting ESX VMFS Stores with Automation</title>
  <ns>0</ns>
  <id>445</id>
  <revision>
    <id>1511</id>
    <parentid>1316</parentid>
    <timestamp>2021-06-07T13:56:27Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Fixing link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1288" xml:space="preserve">author: Mike La Spina

==== Description ====

Some time ago Mike shared some interesting information about VMFS volumes that he found using direct analysis in his blog named [http://blog.laspina.ca/ubiquitous/understanding-vmfs-volumes Understanding VMFS volumes]. 

This spawned some discussions on the VMware Community forums and it became apparent that an automated backup of the critical VMFS info could be useful in the event of an undesirable security event that impacts our system availability. 

By creating a simple backup script process we can provide the ability to recover much more quickly from such events. In this howto guide we will enable this process with a cron job using the existing /etc/cron.daily/ job location directory. 

We simply need to copy an automation script to this location and it will run daily. Or if your change rate is less frequent maybe the /etc/cron.weekly location is more suitable.  ...

==== Location ====

[http://blog.laspina.ca/roller/Ubiquitous/entry/understanding_vmfs_volumes Ubiquitous: Protecting ESX VMFS Stores with Automation]

See also:
[http://blog.laspina.ca/roller/Ubiquitous/entry/additional_vmfs_backup_automation_script Ubiquitous: Additional VMFS Backup Automation script features]

[[Category: Bash]] [[Category: Forensics]]</text>
    <sha1>430c064e37e3d26199d48153d7bd6d94ed7ce558</sha1>
  </revision>
  <revision>
    <id>1512</id>
    <parentid>1511</parentid>
    <timestamp>2021-06-07T13:57:46Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Fixing link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1271" xml:space="preserve">author: Mike La Spina

==== Description ====

Some time ago Mike shared some interesting information about VMFS volumes that he found using direct analysis in his blog named [http://blog.laspina.ca/ubiquitous/understanding-vmfs-volumes Understanding VMFS volumes]. 

This spawned some discussions on the VMware Community forums and it became apparent that an automated backup of the critical VMFS info could be useful in the event of an undesirable security event that impacts our system availability. 

By creating a simple backup script process we can provide the ability to recover much more quickly from such events. In this howto guide we will enable this process with a cron job using the existing /etc/cron.daily/ job location directory. 

We simply need to copy an automation script to this location and it will run daily. Or if your change rate is less frequent maybe the /etc/cron.weekly location is more suitable.  ...

==== Location ====

[http://blog.laspina.ca/ubiquitous/understanding-vmfs-volumes Ubiquitous: Protecting ESX VMFS Stores with Automation]

See also:
[http://blog.laspina.ca/ubiquitous/additional-vmfs-backup-automation-script-features Ubiquitous: Additional VMFS Backup Automation script features]

[[Category: Bash]] [[Category: Forensics]]</text>
    <sha1>3ebdf8e1dd64ae46e84a8a6bed98b4d4398003a8</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Pyvmware</title>
  <ns>0</ns>
  <id>32</id>
  <revision>
    <id>1513</id>
    <parentid>79</parentid>
    <timestamp>2021-06-07T14:01:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Fixing link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="264" xml:space="preserve">A python module that makes use of the vmware client sdk to control vmware instances.

NOTE: Currently beta with limited implemented methods. Enough to start, stop, and revert a VM. 

https://code.google.com/archive/p/pyvmware/

[[Category:SDK]] [[Category:python]]</text>
    <sha1>f20cffa042ae4e1f4c2179b12e3d7255c3e4c19b</sha1>
  </revision>
</page>
<page arvcontinue="20190123214422|1457">
  <title>Open-vm-tools</title>
  <ns>0</ns>
  <id>427</id>
  <revision>
    <id>1519</id>
    <parentid>1401</parentid>
    <timestamp>2021-10-11T22:46:52Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Open Virtual Machine Tools */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1096" xml:space="preserve">==== Open Virtual Machine Tools ====


The Open Virtual Machine Tools (open-vm-tools) are the open source implementation of VMware Tools.

Almost all of the current Linux distributions carry this version of VMware Tools in their repositories.
This is also the preferred version of VMware Tools over what might be bundled with VMware's products.

You will also find this on other open source operating systems such as FreeBSD.

The Open Virtual Machine Tools project aims to provide a suite of open source virtualization utilities and drivers to improve the functionality and user experience of virtualization. The project currently runs in guest operating systems under VMware hypervisors.

Project page: https://github.com/vmware/open-vm-tools

=== Install on Debian / Ubuntu ===

On a server:
 sudo apt-get install open-vm-tools 

On a desktop:
 sudo apt-get install open-vm-tools open-vm-tools-desktop


===== old links =====
* [http://sourceforge.net/projects/open-vm-tools/ sourceforge open-vm-tools project page]

* [http://open-vm-tools.sourceforge.net/ homepage]

[[Category: VMware OSS]]</text>
    <sha1>625f25bb1300baa59e0e5fa3b9f030d858d55881</sha1>
  </revision>
  <revision>
    <id>1520</id>
    <parentid>1519</parentid>
    <timestamp>2021-10-11T22:55:47Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1310" xml:space="preserve">==== Open Virtual Machine Tools ====


The Open Virtual Machine Tools (open-vm-tools) are the open source implementation of VMware Tools.

Almost all of the current Linux distributions carry this version of VMware Tools in their repositories.
This is also the preferred version of VMware Tools over what might be bundled with VMware's products.

You will also find this on other open source operating systems such as FreeBSD.

The Open Virtual Machine Tools project aims to provide a suite of open source virtualization utilities and drivers to improve the functionality and user experience of virtualization. The project currently runs in guest operating systems under VMware hypervisors.

Project page: https://github.com/vmware/open-vm-tools

=== Install on Debian / Ubuntu ===

On a server:
 sudo apt-get install open-vm-tools 

On a desktop:
 sudo apt-get install open-vm-tools open-vm-tools-desktop

=== Install on CentOS / RedHat ===

On a server:
 sudo dnf install open-vm-tools 

On a desktop:
 sudo dnf install open-vm-tools open-vm-tools-desktop

Installing X11 driver:
 sudo dnf install xorg-x11-drv-vmware


===== old links =====
* [http://sourceforge.net/projects/open-vm-tools/ sourceforge open-vm-tools project page]

* [http://open-vm-tools.sourceforge.net/ homepage]

[[Category: VMware OSS]]</text>
    <sha1>ccde1cde13ad9537123edbdd3adf72a7c1c70e5a</sha1>
  </revision>
  <revision>
    <id>1521</id>
    <parentid>1520</parentid>
    <timestamp>2021-10-11T22:56:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* old links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1308" xml:space="preserve">==== Open Virtual Machine Tools ====


The Open Virtual Machine Tools (open-vm-tools) are the open source implementation of VMware Tools.

Almost all of the current Linux distributions carry this version of VMware Tools in their repositories.
This is also the preferred version of VMware Tools over what might be bundled with VMware's products.

You will also find this on other open source operating systems such as FreeBSD.

The Open Virtual Machine Tools project aims to provide a suite of open source virtualization utilities and drivers to improve the functionality and user experience of virtualization. The project currently runs in guest operating systems under VMware hypervisors.

Project page: https://github.com/vmware/open-vm-tools

=== Install on Debian / Ubuntu ===

On a server:
 sudo apt-get install open-vm-tools 

On a desktop:
 sudo apt-get install open-vm-tools open-vm-tools-desktop

=== Install on CentOS / RedHat ===

On a server:
 sudo dnf install open-vm-tools 

On a desktop:
 sudo dnf install open-vm-tools open-vm-tools-desktop

Installing X11 driver:
 sudo dnf install xorg-x11-drv-vmware


==== old links ====
* [http://sourceforge.net/projects/open-vm-tools/ sourceforge open-vm-tools project page]

* [http://open-vm-tools.sourceforge.net/ homepage]

[[Category: VMware OSS]]</text>
    <sha1>abe454b21a0924bebd4556f429bff27d9286d654</sha1>
  </revision>
  <revision>
    <id>1522</id>
    <parentid>1521</parentid>
    <timestamp>2021-10-11T22:56:38Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* old links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1306" xml:space="preserve">==== Open Virtual Machine Tools ====


The Open Virtual Machine Tools (open-vm-tools) are the open source implementation of VMware Tools.

Almost all of the current Linux distributions carry this version of VMware Tools in their repositories.
This is also the preferred version of VMware Tools over what might be bundled with VMware's products.

You will also find this on other open source operating systems such as FreeBSD.

The Open Virtual Machine Tools project aims to provide a suite of open source virtualization utilities and drivers to improve the functionality and user experience of virtualization. The project currently runs in guest operating systems under VMware hypervisors.

Project page: https://github.com/vmware/open-vm-tools

=== Install on Debian / Ubuntu ===

On a server:
 sudo apt-get install open-vm-tools 

On a desktop:
 sudo apt-get install open-vm-tools open-vm-tools-desktop

=== Install on CentOS / RedHat ===

On a server:
 sudo dnf install open-vm-tools 

On a desktop:
 sudo dnf install open-vm-tools open-vm-tools-desktop

Installing X11 driver:
 sudo dnf install xorg-x11-drv-vmware


=== old links ===
* [http://sourceforge.net/projects/open-vm-tools/ sourceforge open-vm-tools project page]

* [http://open-vm-tools.sourceforge.net/ homepage]

[[Category: VMware OSS]]</text>
    <sha1>d01b1aebf4c5834ef76b30d28281cc5e8206ac3b</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>Vmx hacks</title>
  <ns>0</ns>
  <id>585</id>
  <revision>
    <id>1527</id>
    <parentid>1518</parentid>
    <timestamp>2021-10-29T09:07:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Add Dark Mode setting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20270" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

=== Dark Mode ===

In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

 wsFeatureDarkModeSupported = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>4726b339e5af6730be7c684877713570ede199e1</sha1>
  </revision>
  <revision>
    <id>1534</id>
    <parentid>1527</parentid>
    <timestamp>2021-11-12T10:21:06Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Change thumbnail speed */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20922" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

==== Linux Host - switch back from Vulkan to X11 ====
Workstation 16.x and higher

Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

 mks.enableX11Presentation=TRUE
 mks.enableVulkanPresentation=FALSE

That will force us to draw the window using X11 instead of Vulkan, which is normally less performant, but might work better on some setups?


from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-1-Display-3D-acceleration-not-working-Windows-10/m-p/2877574#M172414 VMware 16.2.1 Display 3D acceleration not working Windows 10]

Has a great explanation on the difference by banackm

=== Dark Mode ===

In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

 wsFeatureDarkModeSupported = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>5a85d9c6f2bc1a7c99f6cf093e4a335c85f0b264</sha1>
  </revision>
  <revision>
    <id>1535</id>
    <parentid>1534</parentid>
    <timestamp>2021-11-12T10:24:20Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Linux Host - switch back from Vulkan to X11 */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20924" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

==== Linux Host - switch back from Vulkan to X11 ====
Workstation 16.2.0 and higher

Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

 mks.enableX11Presentation=TRUE
 mks.enableVulkanPresentation=FALSE

That will force us to draw the window using X11 instead of Vulkan, which is normally less performant, but might work better on some setups?


from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-1-Display-3D-acceleration-not-working-Windows-10/m-p/2877574#M172414 VMware 16.2.1 Display 3D acceleration not working Windows 10]

Has a great explanation on the difference by banackm

=== Dark Mode ===

In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

 wsFeatureDarkModeSupported = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>7bcc94cacb906b9e40af394f01ccac58d7efca52</sha1>
  </revision>
  <revision>
    <id>1536</id>
    <parentid>1535</parentid>
    <timestamp>2021-11-17T12:05:09Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Disable all USB devices</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="21373" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

==== Linux Host - switch back from Vulkan to X11 ====
Workstation 16.2.0 and higher

Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

 mks.enableX11Presentation=TRUE
 mks.enableVulkanPresentation=FALSE

That will force us to draw the window using X11 instead of Vulkan, which is normally less performant, but might work better on some setups?


from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-1-Display-3D-acceleration-not-working-Windows-10/m-p/2877574#M172414 VMware 16.2.1 Display 3D acceleration not working Windows 10]

Has a great explanation on the difference by banackm

==== Dark Mode ====

In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

 wsFeatureDarkModeSupported = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

==== All USB devices are disabled ====

Check your .vmx file for the following line:

 usb.restrictions.defaultAllow = "FALSE"

If it has this then remove that line and try again.

It seems that this line is automatically added for Workstation/Player 16.2.x when using "Easy Setup".

More details here: [https://communities.vmware.com/t5/VMware-Workstation-Player/All-USB-devices-are-greyed-out/m-p/2878067#M37999 All USB devices are greyed out]

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>ce45d45c259fedfec3ca38428d0fdb8cc79cffe0</sha1>
  </revision>
  <revision>
    <id>1537</id>
    <parentid>1536</parentid>
    <timestamp>2021-11-17T12:07:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Note about multiple GPU's when having issues with Vulkan</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="21516" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

==== Linux Host - switch back from Vulkan to X11 ====
Workstation 16.2.0 and higher

Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

 mks.enableX11Presentation=TRUE
 mks.enableVulkanPresentation=FALSE

That will force us to draw the window using X11 instead of Vulkan, which is normally less performant, but might work better on some setups?


from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-1-Display-3D-acceleration-not-working-Windows-10/m-p/2877574#M172414 VMware 16.2.1 Display 3D acceleration not working Windows 10]

Has a great explanation on the difference by banackm

Beware that if you have this issue -and your host has more than one GPU- that it also might be because the wrong GPU was selected for Vulkan.

==== Dark Mode ====

In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

 wsFeatureDarkModeSupported = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

==== All USB devices are disabled ====

Check your .vmx file for the following line:

 usb.restrictions.defaultAllow = "FALSE"

If it has this then remove that line and try again.

It seems that this line is automatically added for Workstation/Player 16.2.x when using "Easy Setup".

More details here: [https://communities.vmware.com/t5/VMware-Workstation-Player/All-USB-devices-are-greyed-out/m-p/2878067#M37999 All USB devices are greyed out]

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>37ad8b3b4f021e73c28c36e66b5fa2a071be3c2d</sha1>
  </revision>
  <revision>
    <id>1541</id>
    <parentid>1537</parentid>
    <timestamp>2021-12-08T01:41:26Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Any platform */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22008" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

==== Linux Host - switch back from Vulkan to X11 ====
Workstation 16.2.0 and higher

Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

 mks.enableX11Presentation=TRUE
 mks.enableVulkanPresentation=FALSE

That will force us to draw the window using X11 instead of Vulkan, which is normally less performant, but might work better on some setups?


from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-1-Display-3D-acceleration-not-working-Windows-10/m-p/2877574#M172414 VMware 16.2.1 Display 3D acceleration not working Windows 10]

Has a great explanation on the difference by banackm

Beware that if you have this issue -and your host has more than one GPU- that it also might be because the wrong GPU was selected for Vulkan.

==== Dark Mode ====

In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

 wsFeatureDarkModeSupported = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

==== All USB devices are disabled ====

Check your .vmx file for the following line:

 usb.restrictions.defaultAllow = "FALSE"

If it has this then remove that line and try again.

It seems that this line is automatically added for Workstation/Player 16.2.x when using "Easy Setup".

More details here: [https://communities.vmware.com/t5/VMware-Workstation-Player/All-USB-devices-are-greyed-out/m-p/2878067#M37999 All USB devices are greyed out]

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Disable scoreboard files ====

In VMware Fusion 12.2 and Workstation 16.2 new files have been introduced for keeping some sort of statistics.

These are called scoreboard files.

You can disable that feature.

 vmx.scoreboard.enabled = "FALSE"

See: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-16-2-0-and-scoreboard-files-What-it-is/m-p/2881784/highlight/true#M172906 Suggestion by DaveP on VMware Workstation 16.2.0 and .scoreboard files. What is it?]

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>fb99d24186d8f16b6c92e2497380c35e1fb80f63</sha1>
  </revision>
  <revision>
    <id>1542</id>
    <parentid>1541</parentid>
    <timestamp>2022-03-19T10:30:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Linux Host - switch back from Vulkan to X11 */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22682" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

==== Linux Host - switch back from Vulkan to X11 ====
Workstation 16.2.0 and higher

Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

 mks.enableX11Presentation=TRUE
 mks.enableVulkanPresentation=FALSE

That will force us to draw the window using X11 instead of Vulkan, which is normally less performant, but might work better on some setups?


from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-1-Display-3D-acceleration-not-working-Windows-10/m-p/2877574#M172414 VMware 16.2.1 Display 3D acceleration not working Windows 10]

Has a great explanation on the difference by banackm

Beware that if you have this issue -and your host has more than one GPU- that it also might be because the wrong GPU was selected for Vulkan.

There's another switch to use the openGL renderer instead of Vulkan:

 mks.enableVulkanRenderer = "FALSE"
 mks.enableGLRenderer = "TRUE"

and a switch to allow the Vulkan rendered use unsupported devices:

 mks.vk.allowUnsupportedDevices = "TRUE"

There's even a way to force your VM to use a specific GPU, such as the discrete GPU instead of the integrated GPU.. if your host has both.

 mks.forceDiscreteGPU = "TRUE"

See the tips from BlueFireStorm here: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-cannot-connect-to-the-virtual-machine-Vmware/m-p/2899481/highlight/true#M174703 VMware Workstation cannot connect to the virtual machine]

==== Dark Mode ====

In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

 wsFeatureDarkModeSupported = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

==== All USB devices are disabled ====

Check your .vmx file for the following line:

 usb.restrictions.defaultAllow = "FALSE"

If it has this then remove that line and try again.

It seems that this line is automatically added for Workstation/Player 16.2.x when using "Easy Setup".

More details here: [https://communities.vmware.com/t5/VMware-Workstation-Player/All-USB-devices-are-greyed-out/m-p/2878067#M37999 All USB devices are greyed out]

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Disable scoreboard files ====

In VMware Fusion 12.2 and Workstation 16.2 new files have been introduced for keeping some sort of statistics.

These are called scoreboard files.

You can disable that feature.

 vmx.scoreboard.enabled = "FALSE"

See: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-16-2-0-and-scoreboard-files-What-it-is/m-p/2881784/highlight/true#M172906 Suggestion by DaveP on VMware Workstation 16.2.0 and .scoreboard files. What is it?]

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>1f9385f443766a4cf49981d6df9f1a85a75cbace</sha1>
  </revision>
  <revision>
    <id>1543</id>
    <parentid>1542</parentid>
    <timestamp>2022-07-18T10:10:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Player - disable mitigations</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23492" xml:space="preserve">
=== VMX hacks ===

Here's my internal list of the .vmx hacks that I collected over time.

Beware that editing a .vmx file manually and adding any of these options is unsupported. 

If you end up breaking your VM by editing the .vmx ... then restore the backup! (If you had no backups before hacking on your config, you are doing something wrong)

Also note that some options might no longer be active as they might be for an earlier version of a VMware product.

==== Wait 5 seconds on booting ====
Wait 5 seconds on booting:
 bios.bootDelay = "5000"
Time is in milliseconds, change it accordingly.
==== Open BIOS settings on next boot ====
Open BIOS settings on next boot:
 bios.forceSetupOnce = "TRUE"
In VMware Server 2, this setting is also in the web management interface, choose "Configure VM", power tabdialog, near the bottom.

[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1648 Automatically Connecting USB Devices at Virtual Machine Power On]
==== Disable all Power menu and keyboard shortcuts====
 gui.restricted="true" 
This disables all power menu and keyboard shortcuts. It also disables suspend button

==== Fix repeating keys ====

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

    Power off the virtual machine.
    Add a line, similar to this, at the end of your virtual machine's configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it. 

[http://kb.vmware.com/kb/196 Repeated characters when typing in remote console]

==== Disables suspend option ====
 suspend.disabled = "TRUE"
This disables the suspend option in a virtual machine.

==== Fix Caps Lock synchronisation issues ====
This tip fixes the caps lock sync issue in Fusion 2.0.x and Tech Preview. I found it to be invaluable, add this to your VM's configuration file (.vmx):

 mks.keyboard.syncLEDs = "TRUE"
==== Run a VM without a suspend file====
isn't there an option to run a VM without a suspend file (which is a file named like abcdef01-abcd-abcd-abcd-abcdef012345.vmem)
you mean
 mainmem.useNamedFile = "false"
only works in windows

==== Use FT in a VM under Workstation ====
To use FT in a nested VM, you will still have to supply the entirely unsupported option (for the inner VM):

 replay.allowBTOnly = "TRUE"

[http://communities.vmware.com/message/1343622 VMTN Anyone had sucess setting up a ESX40 Lab on Workstation 7.0?]

==== Disable VIX ====

An interesting tidbit if you’re super security cautious you can disable VIX by adding

 “Guest.Command.Enabled”=”False”

to either the VM or the host.  Be aware that this WILL break upgrading of VMware tools, and Guest customization as they both use vix as the underlying technology!

==== Optimize performance linux VM ====

mainmem.useNamedFile is no longer longer used on Linux hosts that run VMplayer 3 or Workstation 7.

New parameters are :
 mainmem.backing = "swap"
 mainmem.backing = "named"
 mainmem.backing = "unnamed"

see http://sanbarrow.com/vmx/vmx-advanced.html#mainmem

==== Optimize troubleshooting ====
Please power off your VM and add the following configuration option to your .vmx file:
 vmx.buildType = stats
Boot the VM and run your benchmark.  
Shut down the VM and send me the contents of the stats directory that will be created in the same folder as the VM.

from: https://communities.vmware.com/message/2408159#2408159

==== Hardening your vmx file for security ====

http://virtualfoundry.blogspot.com/2009/04/hardening-vmx-file.html

==== Spurious APIC interrupt on CPU#1, should never happen ====

These messages are the result of an optimization Workstation 11 uses for inter-processor interrupts between virtual CPUs.  The interrupt vector used for this purpose is 0xff, which is the Linux spurious APIC interrupt vector.  In some cases, an inter-processor interrupt may arrive on a physical processor after Workstation has relinquished the processor to the host OS.  Linux will discard the interrupt and print this message.

Unless these messages occur with high frequency, they should be innocuous.

The following configuration option should disable the optimization and make the messages stop:
 monitor_control.disable_hostedIPI = TRUE

You can add this setting to /etc/vmware/config, and it will take effect for all VMs the next time they are powered on

from: [https://communities.vmware.com/message/2456565#2456565 Spurious APIC interrupt on CPU#1, should never happen]

==== CPU Masking ====

Yes, it is possible to mask the CPUID values in a VM (except for user mode code when using binary translation).  However, masking only changes what CPUID reports; it doesn't change the way the processor behaves.  Thus, masking may cause unexpected guest behavior.


The general format for CPUID masking is:


 cpuid.&lt;leaf&gt;.&lt;register&gt; = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx


The right hand side is a binary representation of the desired value, most significant bit first.  Aside from '0' and '1,' two other important symbols are 'h,' which means to pass through the bit from the host CPUID and '-,' which means not to override the normal handling for this bit.

Specifying a different CPU vendor is not recommended.

from [https://communities.vmware.com/thread/405727 thread masking] Mr JMattson


In any event, the first thing to do is to pretend to be an AMD CPU.  These settings should accomplish that:

 cpuid.0.ebx = "0110:1000:0111:0100:0111:0101:0100:0001"
 cpuid.0.ecx = "0100:0100:0100:1101:0100:0001:0110:0011"
 cpuid.0.edx = "0110:1001:0111:0100:0110:1110:0110:0101"
 
Then you want to claim the family, model, and stepping of an actual AMD CPU.  This setting should do that (claiming to be an early 64-bit Opteron):

 cpuid.1.eax="----:0000:0000:0000:----:1111:0100:0110"

Even with these settings, some guests may still be unhappy.

=== Workstation ===

==== USB debugging ====

from [https://communities.vmware.com/message/2473661#2473661 Conversion from Workstation 10 to 11 breaks USB connections]
 usb.quirks.device0 = "0x04e8:0x685b skip-reset"

==== USB Passthrough on Linux Host ====
'Passthrough' mode was disabled on Linux host as it conflicted with shared mode provided via pcscd

from [https://communities.vmware.com/message/2462510#2462510 Gemalto Smart Card Reader only appears as "Shared" not "Passthrough"]

* 1) Go to the VM's installation directory. Typically C:\Users\&lt;username&gt;\Documents\Virtual Machines\
* 2) Open &lt;virtual-machine-name&gt;.vmx file
* 3) Append the following lines:
  usb.generic.allowCCID = "TRUE"
  usb.ccid.disable = "TRUE"
* 4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
 sudo kill -9 &lt;pid of the process that corresponds to pcscd&gt;

Notes:
* 1) The first line in step 3 enables the passthrough mode
* 2) The second line in step 3 disables shared mode
* 3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

==== Change thumbnail speed ====

From Workstation 14 including 15, the thumbnail views are not in real time any more and the default refresh interval value is 3000 ms.

You can add

 pref.thumbnailRefreshIntervalMs = 1000

(or other values) in the preference file %appdata%/vmware/preferences.ini to change the refesh rate. But keep in mind that this way may cause high CPU usage.

 
If you really need the previous real time thumbnail, you can use

 pref.closeInactiveMKSWindows =  "false"

But this way may cause mouse/keyboard functions under multi tabs not working well.

Both these settings are not documented or tested, so I cannot guarantee they working normally.

Note that you should make changes to the preferences.ini file with VMware Workstation shut down.

from: https://communities.vmware.com/message/2807350#2807350

==== Linux Host - switch back from Vulkan to X11 ====
Workstation 16.2.0 and higher

Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

 mks.enableX11Presentation=TRUE
 mks.enableVulkanPresentation=FALSE

That will force us to draw the window using X11 instead of Vulkan, which is normally less performant, but might work better on some setups?


from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-1-Display-3D-acceleration-not-working-Windows-10/m-p/2877574#M172414 VMware 16.2.1 Display 3D acceleration not working Windows 10]

Has a great explanation on the difference by banackm

Beware that if you have this issue -and your host has more than one GPU- that it also might be because the wrong GPU was selected for Vulkan.

There's another switch to use the openGL renderer instead of Vulkan:

 mks.enableVulkanRenderer = "FALSE"
 mks.enableGLRenderer = "TRUE"

and a switch to allow the Vulkan rendered use unsupported devices:

 mks.vk.allowUnsupportedDevices = "TRUE"

There's even a way to force your VM to use a specific GPU, such as the discrete GPU instead of the integrated GPU.. if your host has both.

 mks.forceDiscreteGPU = "TRUE"

See the tips from BlueFireStorm here: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-cannot-connect-to-the-virtual-machine-Vmware/m-p/2899481/highlight/true#M174703 VMware Workstation cannot connect to the virtual machine]

==== Dark Mode ====

In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

 wsFeatureDarkModeSupported = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

==== All USB devices are disabled ====

Check your .vmx file for the following line:

 usb.restrictions.defaultAllow = "FALSE"

If it has this then remove that line and try again.

It seems that this line is automatically added for Workstation/Player 16.2.x when using "Easy Setup".

More details here: [https://communities.vmware.com/t5/VMware-Workstation-Player/All-USB-devices-are-greyed-out/m-p/2878067#M37999 All USB devices are greyed out]

=== VMware Player ===

==== Disable mitigations ====

A message about disabling side channel mitigations shows up only when the ULM is used instead of the ring 0 VMM as the hypervisor monitor. 

That means the Windows host has been detected to have Hyper-V enabled.

https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html

There is no advanced options in VMware Workstation Player. 

To disable the side channel mitigation, shut down the VM and add the following to the VM vmx configuration file.

 ulm.disableMitigations = "TRUE"

from: [https://communities.vmware.com/t5/VMware-Workstation-Player/Poor-performance-after-update-with-message-about-side-channel/m-p/2811455/highlight/true#M35855 Poor performance after update with message about side channel mitigation]

=== Fusion ===
==== Applying a setting over all VMs ====

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user global config file that can be found at: ~/Library/Preferences/VMware\ Fusion/config

There's already a 'preferences' file in the same directory, but normally the config file has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

==== Hide the Full Screen application menu ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.showFullScreenTitleBar = "FALSE"

See also: http://communities.vmware.com/message/1348663#1348663

==== Delay drop down Full Screen application menu ====

Edit /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 fusion.fullScreenMenuDelay = "2"

The delay is in seconds and the default is 1.5 seconds, added since Fusion 4.1
A value of "0" removes the delay.

See also: http://communities.vmware.com/message/2273022

On VMware Workstation you would add the following lines to the preferences.ini file.

 pref.fullscreen.showDelay = "5000" 
to delay the showing of the toolbar 5000ms (5 seconds) 
 pref.fullscreen.hideDelay = "1000"
to hide the toolbar after 1000ms (1 second)

For Win7 the preferences.ini file is located under:
 C:\Users\&lt;username&gt;\AppData\Roaming\VMware

==== debug menu ====

 fusion.enableDebugMenu

(never tried)

==== Turn off full screen autofit to host ====

Here's another way to stop the guest from automagically being resized at each swipe:

* Open Finder, select the "Go" menu then select "Go To Folder..." and type in: ~/Library/Preferences/VMware Fusion/
* Open the preferences file in a text editor and add/append the following lines at the end of the file: 

 pref.autoFitGuestToWindow = "FALSE"
 pref.autoFitFullScreen = "stretchGuestToHost"

Taken from: https://communities.vmware.com/message/2293562

==== Pass through host model ====

It's unsupported, but try editing /Users/$USER/Library/Preferences/VMware Fusion/preferences and add the line:

 hw.model.reflectHost = "TRUE"

This will cause the VM to see the same model ID as the host.  The default for this option is FALSE.  Be aware that using this option may cause VM portability issues since the guest may now depend on this behavior and the type of the underlying Mac.

See also: http://communities.vmware.com/thread/336922

==== VM power options always display "Force" ====

If the Virtual Machine was not originally created in VMware Fusion then you will notice that the Fusion Virtual Machine menu has the word "Force" inserted before any power option.
For example copying a VM from a Windows systems to Mac it displays the "Force ..." commands by default.  In other words, pressing the Option Key is backwards of what it is supposed to be.  This is because the following options are missing from the Virtual Machine's .vmx configuration file.

 powerType.powerOff = "soft"  
 powerType.powerOn = "soft"  
 powerType.suspend = "soft"  
 powerType.reset = "soft"  

By default, VMware Fusion creates these options in the Virtual Machine's .vmx configuration file while VMware Player/Workstation does not.  So, add the above options to the Virtual Machine's .vmx configuration file and the "Force ..." commands will then exhibit VMware Fusion normal behavior.  Meaning in order to access the "Force ..." commands one will need to press the Option Key.

See also: http://communities.vmware.com/thread/402281

==== kernel debugging ====

You can attach a remote debugger such as gdb to your vm to do kernel debugging.

DebugStub knows nothing at all about the guest OS.  Think of debugStub as an In-Circuit Debugger for the virtual CPU(s).

 debugStub.listen.guest64 = "TRUE"
 debugStub.listen.guest64.remote = "TRUE"
 debugStub.hideBreakpoints=1
specify a custom port with:
 debugStub.port.guest64 = "8865"
other options:
 debugStub.listen.guest32 = "TRUE"                          # Enable listener for 32 bit guest
 debugStub.listen.guest32.remote = "TRUE"              # Allow remote connection
 debugStub.port.guest32 = "32001"                          # Listen on specified port NNN

see also: [https://communities.vmware.com/thread/470936 Using debugStub to debug a guest linux kernel]

==== Additional logging ====
For troubleshooting boot issues etcetera you can increase the log level in vmware.log

 monitor_control.log_vmsample = "TRUE"

[https://communities.vmware.com/thread/471833 Fusion 6.0.2 / OS X 10.9.2 Host / OS X 10.9 Guest VM running &gt;100% CPU no matter what]

==== memory hole ====

At 3.2 GB there's a 1024kB memory hole.

You can use the pciHole.start option to adjust the start of the memory hole, measured in megabytes from address 0x00000000.  The default is

   pciHole.start = 3072

which corresponds to 0xC0000000.

from [https://communities.vmware.com/thread/478739 Memory hole at 3.2GB]

==== Disable Shared Folder event notification ====

 isolation.tools.hgfs.notify.enable = "FALSE"

See also: http://kb.vmware.com/kb/2011360


==== Shared folder size check ====

The other workaround is to stop the VM, edit the VM's .vmx file and add the following setting:

 tools.hgfs.volumeInfoType = "max"

 
Then start the VM again, and this time you will not need to disable the other shares which are on smaller sized volumes.

 
The default setting causes the shares to be aggregated to the smallest volume size that a share resides on when our file system is queried for size and free space.

The above setting overrides this to pick the largest volume size. The downside is that you can start a copy to a share on volume with a smaller amount of free space and it will only fail when it actually fails to write when the free space is exhausted.

If you know you are not going to run into that type of scenario yourself or you verify prior to starting the copy operation then you will be fine.

 
Note, the above can only be set to "min" or "max" and if not set at all, then "min" is the default.

from: [https://communities.vmware.com/message/2381223#2381223 Folder copy on Windows 7 vm fails for "not enough space", but there is.]

==== Disable location services ====

 sensor.location = "disable" 

to vmx.

[https://communities.vmware.com/message/2383410#2383410 how-to disable location services]

==== Disable automatic USB connect to guest feature ====

1. Suspend or shut down any running VMs and quit Fusion.

2. Ensure that the vmware-usbarbitrator process is no longer running.

3. Create/edit the host-global configuration file, with root privileges: (this example uses nano, but feel free to use any other editor)

    sudo nano /Library/Preferences/VMware\ Fusion/config

4. Add the following line to disable the automatic claiming of USB devices:

    usbarb.autoconnect.claimAll = "FALSE"

5. Save the file and quit the editor.

 
With this change, all USB devices should automatically connect to the host even when VMs are running. Note that it will completely disable the USB connection prompt, and will prevent devices from automatically connecting to VMs (even if the option is selected in settings). However it should still be possible to manually connect USB devices to a running VM (except possibly in cases where the reset command is not correctly issued via the hub).

from: [https://communities.vmware.com/message/2393343#2393343 2014 Preview still has USB 3 hub issue]

==== Open file with host OS application ====
When a file is located on a shared folder (VMware HGFS) then you can choose to be able to open this file with the host OS default application.
For example. Your png file can open in macOS Preview.

  proxyApps.publishToGuest = "TRUE"

See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

==== Pass OS X host serial number ====

If you want an OS X guest to use the host's serial number, you'll need to add this option to the VM's configuration:

  serialNumber.reflectHost = "TRUE"

==== Pass OS X host hardware model ====

To pass hardware model to the guest (not even sure this works, as it does not seem to do anything for me, but ... Fusion does not error on starting the VM )

  hw.model.reflectHost = "TRUE"

==== Pass OS X host hardware model ID ====

If you want an OS X guest to use the host's hardware model ID (i.e. "MacPro5,1"), board ID (i.e. "Mac-12345678") and serial number all together:

  smbios.reflectHost = "TRUE"

=== Any platform ===

==== Disable scoreboard files ====

In VMware Fusion 12.2 and Workstation 16.2 new files have been introduced for keeping some sort of statistics.

These are called scoreboard files.

You can disable that feature.

 vmx.scoreboard.enabled = "FALSE"

See: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-16-2-0-and-scoreboard-files-What-it-is/m-p/2881784/highlight/true#M172906 Suggestion by DaveP on VMware Workstation 16.2.0 and .scoreboard files. What is it?]

==== Slow down time in guest ====

You can't quite stop time, but you can make it go extremely slowly.  Set the following in your system-wide configuration file (/etc/vmware/config on Linux; C:\ProgramData\VMware\VMware Workstation\config.ini on Windows):

 host.cpukHz = 1000

This is probably not all that useful in practice, unless the guest OS has no reliance on any time sources.

from [https://communities.vmware.com/message/2431592#2431592 System time]


==== Set max number of snapshots ====

 snapshot.maxSnapshots = 100

==== Enable DX11 or OpenGL Host Renderer ====

Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 mks.enableDX11Renderer

When 3D accelerated graphics is enabled in Workstation 12/14/15 the default value is "TRUE" (i.e. the line does not have to be present in the vmx file), VMware Workstation uses DX11 of the Windows host to deliver the DX10/OpenGL 3.3 core profile capability inside the VMs. For Linux hosts, the equivalent is mks.enableGLRenderer = "TRUE"

==== Enable D3D Renderer ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 
 mks.enableD3DRenderer

Default is "FALSE" from Workstation 12.x and later. This is only useful in version 12.x if the host graphics card does not have DX11 capability and setting this to TRUE and enableDX11Renderer to FALSE let the VM have some limited 3D accelerated graphics capability. This looks like is already ineffective in version 14/15.

==== Select host Graphics card to use ====
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]


 mks.dx11.vendorID

valid values are the vendor ID of the graphic card, 0x8086 for Intel, 0x10DE for Nvidia, 0x1002 for AMD.

If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

==== ReflectHost ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 SMBIOS.reflectHost

Default is "FALSE". If set to "TRUE" some of the DMI info will use the host values (example: manufacturer will change from VMware to the host value). You can see this difference by using msinfo32 in Windows VM or dmidecode in Linux VM. This is not so useful anymore to hide the fact that the VM is a VM.

==== vmx.buildType ==== 
Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

 vmx.buildType

Valid values are "release" and "debug". The "debug" is the default for the beta versions (aka Tech Preview). When set to "debug", vmware-vmx-debug.exe will be used instead of vmware-vmx.exe and the vmware.log file will be larger.

=== External sites ===

There's only one .vmx site that has most .vmx options and that's Ulli's reference over at sanbarrow:

http://sanbarrow.com/vmx/vmx-advanced.html</text>
    <sha1>a82fb54b1fcf8fcab350c2e495034745dedf71fc</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>Build guest vmware kernel modules</title>
  <ns>0</ns>
  <id>573</id>
  <revision>
    <id>1528</id>
    <parentid>1439</parentid>
    <timestamp>2021-11-02T09:30:23Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* available kernel modules */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5717" xml:space="preserve">====Pre built modules are sometimes not enough====
When you select "install VMware Tools" then your VMware product will try to install the available vmware modules.
If you run linux then sometimes the kernel will not match up with the prebuilt modules as are supplied with your vmware product.
You can unzip the vmware tools .tar.gz bundle from the attached virtual CDrom and run the perl script, but if you just supply defaults you might still miss out on some modules as it will fail silently.

eg running:
 ./vmware-install.pl --default
is great as long as you have provided the VM with the right prerequisites.
====The solution====
Present the linux vmware tools virtual cd-rom to the VM and mount as a CDRom.
    mount /dev/sr0 /mnt/cdrom  
Copy the files to your home folder
    cd ~  
    cp /mnt/cdrom/VMwareTools-*.tar.gz .  
unzip
    tar xfz VMwareTools-*.tar.gz  
go into sub folder to build the tools
    cd vmware-tools-distrib/  
check and run pre-requisites from next paragraph if needed and then run:
    sudo ./vmware-install.pl  
Press &lt;enter&gt; on any questions asked.

After you are done you can remove the vmware-tool-distrib folder as it is only needed before the install.

After installing VMware Tools you now have the possibility to run
 vmware-config-tools.pl
to configure how vmware tools is supposed to work.

Please note that on linux kernels 3.3 and higher, the original vmxnet module is no longer recommended.
You are advised to use a newer virtual NIC such as vmxnet3 or e1000e.

====Preconditions for the script to work====

If you try to run the vmware-install.pl script and you need to build new kernel modules, then the script might give you the following error:
 Before you can compile modules, you need to have the following installed...
 
 make
 gcc
 kernel headers of the running kernel

You will have to get your kernel-headers and a compiler and build system before hand.
On Ubuntu or debian based systems execute this:
 sudo apt-get install build-essential linux-headers-$(uname -r)
On fedora / Red Hat based systems:
 su -c "yum install kernel-devel"
On SUSE / openSUSE use YaST to fetch the latest linux-kernel-headers

====Troubleshooting====

===== available kernel modules =====
After the manual compile, you can run the lsmod command to see what modules it was able to load:
 $ lsmod | grep -i vm

The following kernel modules are currently available:
* vmhgfs - shared folders
* vmxnet3 - virtual network adapter
* vmmemctl - memory
* vmw_balloon - balloon memory driver
* vmw_pvscsi - paravirtual scsi
* [[vmwgfx]] - accelerated graphics
* vmblock - enable drag &amp; drop between guest and host OS (desktop feature)
* vmsync -
* vgauth - Guest Authentication
* vmw_vmci - inter-VM and host interface
* vmw_vsock_vmci_transport - 
* vsock - virtual sockets

Interesting tidbit, the reason that there's a "vmw_" prefix means it is VMware only and if there's no prefix, like vsock, then it is because it is a hypervisor-independent interface. See [https://communities.vmware.com/thread/497086 (1)] for details

There's also a number of additional commands/scripts to enable other features
* /usr/bin/vmware-toolbox-cmd - shrink, upgrade, statistics, version, timesync, run scripts on power operations, power operations, control devices
* /usr/bin/vmware-user - advanced X features, guest resolution fit, drag and drop, file and text copy &amp; paste. Running this will start the vmtoolsd daemon in /usr/lib/vmware-tools/sbin64
* /usr/lib/vmware-tools/sbin64/vmware-checkvm - prints VMware software version
* /usr/lib/vmware-tools/sbin64/vmware-modconfig-console - module helper for acquiring status, kernel headers version, is a link to /usr/lib/vmware-tools/bin64/appLoader option --install-all will actually build all of your modules as well.
* vmware-tools-thinprint - printing integration with the host using a virtual printing daemon

===== unable to start services for VMware Tools =====

 Creating a new initrd boot image for the kernel.
 
 NOTE: both /etc/vmware-tools/GuestProxyData/server/key.pem and
       /etc/vmware-tools/GuestProxyData/server/cert.pem already exist.
       They are not generated again. To regenerate them by force,
       use the "vmware-guestproxycerttool -g -f" command.
 
 initctl: Job failed to start
 Unable to start services for VMware Tools
 
 Execution aborted.

If you get the above error then you can probably do as is sugggested above. I simply nuked the folder /etc/vmware-tools/GuestProxyData (rm -rf ) and completely reran the installer, after that it worked.

===== vgauth what? =====

Nowadays VMware Tools asks if you want to enable the CAF agent (Common Agent Framework agent).

If you are like me then you are probably wondering what this is.

At the forums there's an answer ( https://communities.vmware.com/message/2604183#2604183 by VMware employee ykzang)

I'm quoting that here for ease of reading.


''Multiple VMware management solutions (e.g. vCM, Hyperic, Log Insight) require  installation of in-guest agents.The Common Agent Framework attempts to provide a common framework to unify and simplify the management of various types of agents, and these agents would be referred to as Common Agent.''


''Those VMware solutions are working on distinct administrative domains from the guest. VGAuth provides a way to authorize those solutions users' behaviors(install agent for example) within guest.''

====Alternative solution====
Many Linux distributions now come with a package called [[open-vm-tools]] and while that does give you a good bases, there are still things missing.
Most notable is the host guest file system integration that is provided by the vmhgfs kernel module.

[[Category: CLI]] [[Category: Bash]]</text>
    <sha1>707aabad209979387eb3b73f801b7cf153ba3a33</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>Vmwgfx</title>
  <ns>0</ns>
  <id>588</id>
  <revision>
    <id>1529</id>
    <timestamp>2021-11-02T09:32:25Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "== vmwgfx ==  3D accelerated graphics in Linux  This driver is nowadays part of the linux kernel, see:  https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/vmwgfx  B..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="247" xml:space="preserve">== vmwgfx ==

3D accelerated graphics in Linux

This driver is nowadays part of the linux kernel, see:

https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/vmwgfx

Before it was at freedesktop:

https://gitlab.freedesktop.org/mesa/vmwgfx</text>
    <sha1>84a807d600987cb42e40e36afa373307af7825f4</sha1>
  </revision>
  <revision>
    <id>1530</id>
    <parentid>1529</parentid>
    <timestamp>2021-11-02T09:48:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* vmwgfx */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="384" xml:space="preserve">== vmwgfx ==

3D accelerated graphics in Linux

This driver is nowadays part of the linux kernel, see:

https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/vmwgfx

Before it was at freedesktop:

https://gitlab.freedesktop.org/mesa/vmwgfx

older
https://cgit.freedesktop.org/mesa/vmwgfx

and doc with tips on how-to build your own:
https://docs.mesa3d.org/drivers/svga3d.html</text>
    <sha1>c829864a87fd0a6929c890f27cf5382a93af5864</sha1>
  </revision>
  <revision>
    <id>1531</id>
    <parentid>1530</parentid>
    <timestamp>2021-11-02T09:54:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* vmwgfx */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="447" xml:space="preserve">== vmwgfx ==

3D accelerated graphics in Linux

This driver is nowadays part of the linux kernel, see:

https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/vmwgfx

Before it was at freedesktop:

https://gitlab.freedesktop.org/mesa/vmwgfx

older
https://cgit.freedesktop.org/mesa/vmwgfx

and doc with tips on how-to build your own:
https://docs.mesa3d.org/drivers/svga3d.html

In 2010 I wrote this on my internal wiki [Building Gallium3D]</text>
    <sha1>1b9d42df614b801749339fbe99f45133a1c42293</sha1>
  </revision>
  <revision>
    <id>1532</id>
    <parentid>1531</parentid>
    <timestamp>2021-11-02T09:55:22Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* vmwgfx */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="474" xml:space="preserve">== vmwgfx ==

3D accelerated graphics in Linux

This driver is nowadays part of the linux kernel, see:

https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/vmwgfx

Before it was at freedesktop:

https://gitlab.freedesktop.org/mesa/vmwgfx

older
https://cgit.freedesktop.org/mesa/vmwgfx

and doc with tips on how-to build your own:
https://docs.mesa3d.org/drivers/svga3d.html

In 2010 I wrote this on my internal wiki [[Building Gallium3D]] when I did build my own.</text>
    <sha1>002787dc4f2863ee17664cf0d809e6f63f761c2d</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>Building Gallium3D</title>
  <ns>0</ns>
  <id>589</id>
  <revision>
    <id>1533</id>
    <timestamp>2021-11-02T09:55:58Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Copy from my internal wiki on how-to build Gallium3D (hopelessly out of date now, but perhaps it helps)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3365" xml:space="preserve">==== basic research ====

setup Ubuntu Lucid (10.04) x64

 sudo apt-get mesa-utils

 glxinfo | grep -i render

 sudo add-apt-repository ppa:xorg-edgers/drivers-only 

Brian Paul at vmware

Gallium llvmpipe is what we need and a kernel driver called  vmwgfx driver
===== vmwgfx =====
The vmwgfx kernel driver source can be found at: http://cgit.freedesktop.org/mesa/vmwgfx/commit/
direct download link sources:
http://cgit.freedesktop.org/mesa/vmwgfx/snapshot/vmwgfx-master.tar.gz

In order to built the kernel module you'll need to have the kernel headers installed.
No Configure step is needed.
Just run:
 make
 make install

The install doesn't appear to copy the kernel module into the kernel driver tree for whatever reason, so copy by hand: 
 cp vmwgfx.ko /lib/modules/2.6.33-020633-generic/kernel/drivers/gpu/drm/vmwgfx
(create the vmwgfx subfolder first)

Doesn't work either....

Restarting X server &gt; Right Alt + Print Screen + k
instead of Ctrl + Alt + Backspace

===== Mesa =====
Gallium3D is part of the mesa drivers
The mesa drivers can be found at: http://cgit.freedesktop.org/mesa/mesa/commit/
and a direct download link for the source:

http://cgit.freedesktop.org/mesa/mesa/snapshot/mesa-master.tar.gz


http://www.khattam.info/2010/02/06/installing-kernel-2-6-33-to-lucid-lynx-ubuntu-10-04-without-compiling/

http://www.x.org/wiki/radeonBuildHowTo

 # cd xf86-video-radeonhd/ # ./autogen.sh --prefix=/usr # make # make install

This should install the RadeonHD driver for you. Please note that it might be nontrivial to completely uninstall the driver now.

Also note that you can also drop off the --prefix=/usr part so the driver will be installed to /usr/local. You should at this point find out which path your X downloads its modules from. The next will prepend module search directory under /usr/local before the one which in many computers is the default X.org module path. Not that this can cause your X not to start if main module path is changed for some reason so don't forget this setting's existence. The second path needs to be the real X.org module path.
 File: /etc/X11/xorg.conf
 Section "Files"
   ModulePath "/usr/local/lib/xorg/modules,/usr/lib/xorg/modules"
 EndSection

==== mesa build requirements ====
 sudo apt-get install build-essentials automake autoconf xserver-xorg-dev libdrm-dev x11proto-gl-dev libxfixes-dev x11proto-fixes-dev
 mesa-common-dev libosmesa-dev
 libxext-dev
 libxdamage-dev
 libxxf86vm-dev
 expat libexpat1-dev
 libxt-dev
 libxmu-dev
 libxi-dev
 llvm-dev

 ./autogen.sh --enable-gallium-llvm --prefix=/opt/xorg
 ./autogen.sh --enable-gallium-llvm --with-driver=xlib --prefix=/opt/xorg
 ./autogen.sh --with-driver=osmesa --prefix=/opt/xorg

 ./autogen.sh --prefix=/opt/xorg

Now without gallium-llvm (this is the only one that compiles OK)
 ./autogen.sh --with-driver=xlib --prefix=/opt/xorg


==== External links ====

[http://www.phoronix.com/scan.php?page=article&amp;item=gallium3d_llvmpipe&amp;num=1 LLVMpipe: OpenGL With Gallium3D on Your CPU]

[http://www.phoronix.com/scan.php?page=news_item&amp;px=ODA1OA Gallium3D's LLVMpipe Software Rasterizer Is Kicking]

[http://www.phoronix.com/scan.php?page=news_item&amp;px=Nzc4Ng VMware Goes For Mainline Inclusion Of Its DRM]

[http://www.phoronix.com/scan.php?page=news_item&amp;px=ODIxMw LLVMpipe Doesn't Yet Like The GNOME Shell]

http://vmware-svga.sourceforge.net/</text>
    <sha1>35c61d199a617c31b5599e2b59a90436faa92348</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>Windows 3.1</title>
  <ns>0</ns>
  <id>590</id>
  <revision>
    <id>1538</id>
    <timestamp>2021-11-27T18:53:24Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with " http://www.scampers.org/steve/vmware/#31pack  http://www.stankowic-development.net/?p=6674&amp;lang=en  https://sites.google.com/site/chitchatvmback/misc  [https://github.com/Nat..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="230" xml:space="preserve">
http://www.scampers.org/steve/vmware/#31pack

http://www.stankowic-development.net/?p=6674&amp;lang=en

https://sites.google.com/site/chitchatvmback/misc

[https://github.com/NattyNarwhal/vmwmouse VMware Mouse driver for Windows 3.x]</text>
    <sha1>9334d20cf698a670ec4a52c4b934c565bc9ae5ee</sha1>
  </revision>
  <revision>
    <id>1539</id>
    <parentid>1538</parentid>
    <timestamp>2021-11-27T19:02:48Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">Some links:

http://www.stankowic-development.net/?p=6674&amp;lang=en

[https://github.com/NattyNarwhal/vmwmouse VMware Mouse driver for Windows 3.x]

See also [[DOS]]</text>
    <sha1>aaec00ca42e21b53831b35f1681d06cf50c0e23a</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>DOS</title>
  <ns>0</ns>
  <id>578</id>
  <revision>
    <id>1540</id>
    <parentid>1502</parentid>
    <timestamp>2021-11-27T19:03:16Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1051" xml:space="preserve">When creating a virtual machine with MS DOS (or PC Dos) then you'll notice that there are a few issues.

The first major issue being that the VM will run one of your cores with a high CPU.
The reason being that MS DOS did not idle your CPU when it wasn't doing nothing, so instead of having a VM that uses no CPU when not doing anything you have that 1 core going nuts.

The classical way to resolve that is by installing DosIdle.

As it doesn't appear to be available much, here's a copy.

[https://wiki.vi-toolkit.com/images/f/f2/DOS-Drivers.zip Dos Drivers download]

Other interesting notes for DOS users of VMware virtual machines:

* [https://communities.vmware.com/t5/VMware-Workstation-Pro-Documents/Sound-Blaster-16-on-VMware-Workstation-15-5-and-VMware-Fusion-11/ta-p/2781947 SoundBlaster 16 support] which has vastly improved thanks to Darius.

You also might want to check out Zamba's page here:

* http://www.scampers.org/steve/vmware/
and Ken Kato's pages here:

* https://sites.google.com/site/chitchatvmback/

See also: [[Windows 3.1]]</text>
    <sha1>44a54b5843954fbd44ea3c95eb22ea690519f2b0</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>Shrink guest on hosted platform</title>
  <ns>0</ns>
  <id>577</id>
  <revision>
    <id>1544</id>
    <parentid>1526</parentid>
    <timestamp>2022-09-07T20:37:45Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Shrink the disk */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10136" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

=== Zero out using fstrim ===

These days there's an alternative way for zero-ing out the parts of the disk that are not used using [https://www.man7.org/linux/man-pages/man8/fstrim.8.html fstrim].

The great thing about this is that it only zero's out the parts of the disk that are not zero and as such the disk does not inflate to its full size.

* [https://forums.freebsd.org/threads/ssd-trim-maintenance.56951/post-328912 Detail comment from Theodore Ts'o on using fstrim]

* [https://github.com/vmware/open-vm-tools/issues/457 Avoid disk expansion while shrinking (github issue tracker)]

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

On macOS you run it as:
 /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root. So certainly try it first without running as root!

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run (as administrator):

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

For example:
 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink c:\
 Please disregard any warnings about disk space for the duration of shrink process.
 Progress: 62 [=======&gt;   ]
The progress you see here is VMware Tools blanking out the unused space.

At 99% it will popup the "Shrinking Disk" progress dialog at the host that takes care of the actual shrinking process.

If you are logged in via remote desktop then do expect to loose the connection for a bit while the actual shrinking is taking place.

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>a7bc24e9a274b49b40eaba9abccedc3327fed58b</sha1>
  </revision>
  <revision>
    <id>1550</id>
    <parentid>1544</parentid>
    <timestamp>2024-01-03T16:33:19Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Zero out using fstrim */  adding a small example</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10428" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

=== Zero out using fstrim ===

These days there's an alternative way for zero-ing out the parts of the disk that are not used using [https://www.man7.org/linux/man-pages/man8/fstrim.8.html fstrim].

eg:
 # fstrim -a -v
 /var: 274.3 MiB (287592448 bytes) trimmed on /dev/sda3
 /tmp: 63 MiB (66060288 bytes) trimmed on /dev/sda5
 /home: 125 MiB (131072000 bytes) trimmed on /dev/sda6
 /boot/efi: 505.2 MiB (529735680 bytes) trimmed on /dev/sda1
 /: 5 MiB (5242880 bytes) trimmed on /dev/sda2

The great thing about this is that it only zero's out the parts of the disk that are not zero and as such the disk does not inflate to its full size.

* [https://forums.freebsd.org/threads/ssd-trim-maintenance.56951/post-328912 Detail comment from Theodore Ts'o on using fstrim]

* [https://github.com/vmware/open-vm-tools/issues/457 Avoid disk expansion while shrinking (github issue tracker)]

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

On macOS you run it as:
 /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root. So certainly try it first without running as root!

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run (as administrator):

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

For example:
 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink c:\
 Please disregard any warnings about disk space for the duration of shrink process.
 Progress: 62 [=======&gt;   ]
The progress you see here is VMware Tools blanking out the unused space.

At 99% it will popup the "Shrinking Disk" progress dialog at the host that takes care of the actual shrinking process.

If you are logged in via remote desktop then do expect to loose the connection for a bit while the actual shrinking is taking place.

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>3542e597c8d8d85aab456aed1cd57cd947b9ee1e</sha1>
  </revision>
  <revision>
    <id>1551</id>
    <parentid>1550</parentid>
    <timestamp>2024-01-06T12:02:29Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>/* Zero out using fstrim */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11798" xml:space="preserve">== Important ==
Note that the technique described below to zero out the unused space on the guest OS will in fact make your guest virtual disk grow to the maximum size first. For each byte that is changed to zero the virtual disk will need to claim a byte. This means that while you can use the technique to reclaim disk space after the unused space is zero'd out, it is important to have enough space before you start.

If you don't have that kind of free disk space then you can skip the zero-ing out part. You can still reclaim space, but it will be less optimal.
Alternatively you can use the "Partially zero out" trick described below.

=== How much free space do you need before shrinking? ===
Also please note that you need more free space in order to be able to run the shrinking process.
The shrinking process consists of making a copy of your virtual disk while omitting the zero'd out blocks. 
So how much extra space you need depends on how you configured the virtual disk for your Virtual Machine. 
If your Virtual Disk is a single file, then your free space requirement can grow up-to the full size of that virtual disk.

If OTOH you are using the split disk scheme where a virtual disk is sliced into multiple files the maximum free space you need is the maximum size a slice can be. Nowadays there's not a fixed slice size, it depends on how big your virtual disk actually is.

The split disk scheme since VMware Workstation 11 (VMware Fusion 7), older version of Workstation/Fusion use a 2GB split disk scheme.


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

For extra safety I recommend to make sure you have an additional 2GB of free space on top of those requirements as mentioned above.

As side note, this also explains why it is generally recommended at the forum by the regulars to use a split disk scheme over single disk files.
This same problem also exists when you want to commit snapshots.

=== Using the clean up option in the menu ===

When you use the "Clean Up Disks" option in the menu in VMware Workstation 12 or later, then you do not require extra disk space for reclaiming space (see also: [https://docs.vmware.com/en/VMware-Workstation-Pro/14.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts] ) 

Currently this only works for Windows guests where the filesystem is NTFS.

== Zero out unused space in a Linux VM ==

Before we try to shrink the virtual disk files, we should try to remove any unneeded files from the virtual machine to free space.
More free space means more disk space that can get reclaimed.

One of the areas in a VM that can take up a lot of disk space is the repository cache. So I personally tend to clean the cache in the VM before reclaiming disk space at the host.

Clean up your repositories:

For example, on Debian-based VMs, you can run the following command (in the VM)

 apt-get clean all

to clear out the local repository of retrieved package files.

On red hat based VMs that would be:

 yum clean

The next step is important:

Shut down any services that depend on having enough available disk space to run.

The reason for this is that we are going to write out zero's to the file system until the file system is full and we do not want any application - for example a database system like mySQL or postgreSQL - to run out of disk space while we are zeroing out the file system. If mySQL would try to write when your disk is full you risk a corrupted database. So this step is important!

Next run (also from within the VM):

 cat /dev/zero &gt; zero.fill;sync;sleep 1;sync;rm -f zero.fill

to fill the unused space with zeros and then remove the "zero.fill" that has all the zero's.

As this command writes to the disk until it runs out of disk space, you will get an error "No space left on the device". This is expected.

Note that you have multiple partitions that you have to repeat the above command to zero out for each partition.
Adjust "zero.fill" to the relevant mountpoint, for example if you have a separate partition for home it would become:

 cat /dev/zero &gt; /home/zero.fill;sync;sleep 1;sync;rm -f /home/zero.fill

=== Zero out a part of your virtual disk ===

If your virtual machine cannot be taken down and you do not want to shut down services that might end up corrupting files because of the "No space left on the device" problem then an idea that might work is to zero out a part of your partition.

This for example creates a 100MB size file filled with zero's

 # dd if=/dev/zero of=zero.fill bs=1024 count=102400
 102400+0 records in
 102400+0 records out
 104857600 bytes (105 MB) copied, 0.3839 s, 273 MB/s

So if you want to zero out 10GB instead, add two more zero's to the count parameter, eg: count=10240000

If you want to fill up in steps, just change the output file name from "zero.fill" into "zero.fill2" etcetera..

Then run the "sync; sleep 1; sync" from above and remove the zero.fill files.

If your VM is running on VMware vSphere and you have a NFS LUN with enough free space then one way to reclaim your space is to Storage vMotion the VM to NFS storage and back. Once done the zero'd out data has been reclaimed. No need to shut down the VM. 

If this is not for you, then do read on.

=== Zero out using fstrim ===

These days there's an alternative way for zero-ing out the parts of the disk that are not used using [https://www.man7.org/linux/man-pages/man8/fstrim.8.html fstrim].

eg:
 # fstrim -a -v
 /var: 274.3 MiB (287592448 bytes) trimmed on /dev/sda3
 /tmp: 63 MiB (66060288 bytes) trimmed on /dev/sda5
 /home: 125 MiB (131072000 bytes) trimmed on /dev/sda6
 /boot/efi: 505.2 MiB (529735680 bytes) trimmed on /dev/sda1
 /: 5 MiB (5242880 bytes) trimmed on /dev/sda2

The great thing about this is that it only zero's out the parts of the disk that are not zero and as such the disk does not inflate to its full size.

* [https://forums.freebsd.org/threads/ssd-trim-maintenance.56951/post-328912 Detail comment from Theodore Ts'o on using fstrim]

* [https://github.com/vmware/open-vm-tools/issues/457 Avoid disk expansion while shrinking (github issue tracker)]

On most modern systems fstrim is being run automatically using systemctl. You can check if it is enabled:

 # systemctl status fstrim.timer
 ● fstrim.timer - Discard unused blocks once a week
      Loaded: loaded (/lib/systemd/system/fstrim.timer; disabled; vendor preset: enabled)
      Active: inactive (dead)
     Trigger: n/a
    Triggers: ● fstrim.service
        Docs: man:fstrim

Oh-huh, our system does not have it enabled.. might there be a reason, such as that the UNMAP command is not supported?
If so, the following command would return 0.
 # cat /sys/block/sda/queue/discard_max_bytes
 1073741824

So UNMAP is supported, but fstrim still is not enabled, lets fix that.
 # systemctl enable fstrim.timer
 Created symlink /etc/systemd/system/timers.target.wants/fstrim.timer → /lib/systemd/system/fstrim.timer.
and reload systemctl plus check that it now works...

 # systemctl start fstrim.timer
 # systemctl daemon-reload
 # systemctl status fstrim.timer
 ● fstrim.timer - Discard unused blocks once a week
      Loaded: loaded (/lib/systemd/system/fstrim.timer; enabled; vendor preset: enabled)
      Active: active (waiting) since Sat 2024-01-06 13:00:46 CET; 6s ago
     Trigger: Mon 2024-01-08 01:17:59 CET; 1 day 12h left
    Triggers: ● fstrim.service
        Docs: man:fstrim


see also:
* https://www.suse.com/support/kb/doc/?id=000019447

== Zero out unused space on a Windows VM ==

To do the same with a windows VM, you can use Microsoft's tool [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx sdelete].

Run it as 
 sdelete -z c:

To clean out the free space on disk c:

Careful!

As of sdelete v1.6 -c and -z have changed meanings, many instructions say -c zeros free space, this is no longer the case, it zeros the space then fills with random data in accordance with DOD spec: DOD 5220.22-M, random data will prevent the reclaim logic from working.

The trigger to zero space with 0x00 has changed to -z!

== Zeroing an encrypted disk ==

If you use disk encryption in the guest OS then zero'ing out the disk won't help.

The reason is that a good disk encryption scheme will write out random data to the disk when you write out zero's.

In other words, if you have enabled full disk encryption in the guest then you can not shrink the disk anymore as there is no space to reclaim.

== Shrink the disk ==

Then power down the VM and open a terminal on the Linux host.

Navigate to the directory where the .vmdk files are located, e.g.:

 cd /var/lib/vmware/Virtual\ Machines/Ubuntu\ Desktop/

You can shrink the .vmdk file as follows:

 vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

On Windows the command also uses the -k option, so I leave that for you as an exercise.

Note that vmware-vdiskmanager is probably not in your search path, so you might have to prepend the vmware-vdiskmanager command with the actual path with the command is located.

On macOS you run it as:
 /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -k Ubuntu\ Desktop.vmdk

If you need to use "sudo" in order to be able to run the above then beware that the ownership of the .vmdk files might get changed to root. So certainly try it first without running as root!

You will have to change the ownership back to your own user, eg:
 sudo chown username: *.vmdk
If you don't change the ownership back you might see errors like:
 "Unable to open file .../Virtual Disk.vmdk: Insufficient permission to access file".

== Shrink using vmware tools ==

Nowadays you can also shrink the guest by using the shrink feature as offered via vmware tools.

So for clarity all of the following commands are run from within the guest to shrink the disk while the guest is running.

On linux in order to use this run:
 sudo vmware-toolbox-cmd disk shrink /

Where "/" is the mount point of the partition that you want to shrink.

On Windows in order to use this run (as administrator):

 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink &lt;location&gt;

where &lt;location&gt; is the drive you want to shrink

For example:
 C:\Program Files\VMware\VMware Tools&gt;VMwareToolboxCmd.exe disk shrink c:\
 Please disregard any warnings about disk space for the duration of shrink process.
 Progress: 62 [=======&gt;   ]
The progress you see here is VMware Tools blanking out the unused space.

At 99% it will popup the "Shrinking Disk" progress dialog at the host that takes care of the actual shrinking process.

If you are logged in via remote desktop then do expect to loose the connection for a bit while the actual shrinking is taking place.

On OS X / macOS the command to use is:

 sudo /Library/Application\ Support/VMware\ Tools/vmware-tools-cli disk shrink /

== Shrink macOS VM with APFS ==

[https://communities.vmware.com/thread/581576 Solved: Shrink an APFS virtual disk]

== External links ==

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-421A1073-BF16-4BC7-AA76-46B954CA438D.html Clean Up a Virtual Hard Disk on Windows Hosts - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-3F94C7B5-19A5-4E91-9709-B17FAA93FF75.html Configuring and Maintaining Virtual Hard Disks - Workstation 16 Pro documentation]

* [https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9 Clean up a Virtual Machine - VMware Fusion 12 documentation]</text>
    <sha1>90abf869ddfdfc994cb1378c9154d2065c1434d9</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>Vmware-vdiskmanager</title>
  <ns>0</ns>
  <id>574</id>
  <revision>
    <id>1545</id>
    <parentid>1429</parentid>
    <timestamp>2022-09-12T11:38:39Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>Update vddk link to version 7.0</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6020" xml:space="preserve">== vmware-vdiskmanager ==


With this tool that comes with VMware Workstation and VMware Fusion you can perform special disk actions such as:
* [[Shrink guest on hosted platform|shrink]]
* defragment
* repair

=== Peculiarities ===

* VMware vdisk manager throws a bogus error in all version from VMware Workstation 7 to Workstation 11, Fusion 3 to Fusion 7

The error looks like:
  VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
and can be safely ignored.

This has been fixed in Fusion 8 / Workstation 12.0

* Disk repair option -R was mostly broken from Workstation 8 to Workstation 11.

This works much better since Fusion 8 / Workstation 12.0

* You cannot reduce the capacity of a virtual disk. Eg. if you have defined a virtual disk of 10GB in size then you cannot change it to be 8GB in size. This is because any resizing the tool does is irregardless of the partition definitions, as this is potentially a destructive operation it is not allowed.
Even if you grow a disk in size you will have to adjust the partitions after the resize.

You can shrink a disk if you have a non pre allocated disk, in this case it will wipe out the unused parts on your disk and give that space back to the host OS.

* The remote host fusion in Fusion 8 and Workstation 12 via the -h option is broken. See also [https://communities.vmware.com/thread/527749 BUG: vmware-vdiskmanager does not accept advertised -h option]

* VMware Player does not come with this tool, but in case of need you can download the [https://developer.vmware.com/web/sdk/7.0/vddk Virtual Disk Development Kit (VDDK)] which does include a copy of the program.

=== Command line help ===

Here's an excerpt from the command line help:
  VMware Virtual Disk Manager - build 3160714.
  Usage: vmware-vdiskmanager.exe OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
  Offline disk manipulation utility
    Operations, only one may be specified at a time:
       -c                   : create disk.  Additional creation options must be specified.  Only local virtual disks can be
                              created.
       -d                   : defragment the specified virtual disk. Only local virtual disks may be defragmented.
       -k                   : shrink the specified virtual disk. Only local virtual disks may be shrunk.
       -n &lt;source-disk&gt;     : rename the specified virtual disk; need to specify destination disk-name. Only local virtual
                              disks may be renamed.
       -p                   : prepare the mounted virtual disk specified by the mount point for shrinking.
       -r &lt;source-disk&gt;     : convert the specified disk; need to specify destination disk-type.  For local destination disks
                              the disk type must be specified.
       -x &lt;new-capacity&gt;    : expand the disk to the specified capacity. Only local virtual disks may be expanded.
       -R                   : check a sparse virtual disk for consistency and attempt to repair any errors.
       -e                   : check for disk chain consistency.
       -D                   : make disk deletable.  This should only be used on disks that have been copied from another product.
  
    Other Options:
       -q                   : do not log messages
  
    Additional options for create and convert:
       -a &lt;adapter&gt;         : (for use with -c only) adapter type
                              (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.
       -s &lt;size&gt;            : capacity of the virtual disk
       -t &lt;disk-type&gt;       : disk type id
  
    Disk types:
        0                   : single growable virtual disk
        1                   : growable virtual disk split in 2GB files
        2                   : preallocated virtual disk
        3                   : preallocated virtual disk split in 2GB files
        4                   : preallocated ESX-type virtual disk
        5                   : compressed disk optimized for streaming
        6                   : thin provisioned virtual disk - ESX 3.x and above
  
       The capacity can be specified in sectors, KB, MB or GB.
       The acceptable ranges:
                             ide/scsi adapter : [1MB, 8192.0GB]
                             buslogic adapter : [1MB, 2040.0GB]
          ex 1: vmware-vdiskmanager.exe -c -s 850MB -a ide -t 0 myIdeDisk.vmdk
          ex 2: vmware-vdiskmanager.exe -d myDisk.vmdk
          ex 3: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 0 destinationDisk.vmdk
          ex 4: vmware-vdiskmanager.exe -x 36GB myDisk.vmdk
          ex 5: vmware-vdiskmanager.exe -n sourceName.vmdk destinationName.vmdk
          ex 6: vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \
                -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"
          ex 7: vmware-vdiskmanager.exe -k myDisk.vmdk
          ex 8: vmware-vdiskmanager.exe -p &lt;mount-point&gt;
                (A virtual disk first needs to be mounted at &lt;mount-point&gt;)

=== Split disks ===

Up until Workstation 11 / Fusion 7 a split disk would never be larger as 2GB.

Due to the virtual disk sizes growing and the extra limitations - such as max open files - that could be hit with larger disks, this is no longer the case for split virtual disks. 

Nowadays the split disk size (= extent size) depends on the size you have set your virtual disk to be.

The new split disk scheme


 Capacity           Extent size
 ================================
 &lt;=128GB            4GB (increased from 2GB)
 &gt;128GB &amp;&amp; &lt;2TB     Capacity / 32 (so maximum of 32 extents)
 &gt;=2TB              2TB

This means that if you want to keep your Virtual Disks to be transportable via FAT32 that you probably should keep your disk sizes under 128GB.

Note that NTFS or HFS has no such limitation, so choosing your maximum virtual disk size depends on need.

=== External links ===

* [http://kb.vmware.com/kb/1023856 Repairing a virtual disk in Fusion 3.1 and Workstation 7.1]</text>
    <sha1>fbcff898ff5fe39a9ccfc7acc2fab6603be2c1c6</sha1>
  </revision>
</page>
<page arvcontinue="20211029090716|1527">
  <title>Fixing a VM that had AutoAddVTPM set</title>
  <ns>0</ns>
  <id>591</id>
  <revision>
    <id>1546</id>
    <timestamp>2023-09-22T16:53:59Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <comment>Created page with "You might have made the mistake to use an experimental solution that was offered for a while by VMware to install Windows 11 as guest OS. It involved adding a line to the .vmx file and after that you could add a TPM and thus install Windows 11. This would encrypt parts of the VM, but not give you a password and as such some people to find out that their VM won't work on some other hosts. The good part is that your data isn't actually encrypted, the bad part is that it is..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1371" xml:space="preserve">You might have made the mistake to use an experimental solution that was offered for a while by VMware to install Windows 11 as guest OS.
It involved adding a line to the .vmx file and after that you could add a TPM and thus install Windows 11.
This would encrypt parts of the VM, but not give you a password and as such some people to find out that their VM won't work on some other hosts.
The good part is that your data isn't actually encrypted, the bad part is that it isn't easy perse to get the data out.

=== Here's one solution where you have a few manual setps ===


The steps to recover your VM are as follows:

I've written out the steps here: https://www.reddit.com/r/vmware/comments/qy9wns/comment/hmokzl7/

Let me quote myself from one of my replies...

The steps are basically:

* Create a new VM with a virtual disk of the same size as the encrypted one, make sure it has the same name.
* use the new descriptor file ('MK Win Desktop.vmdk')
* use the old vmdk data files ('MK Win Desktop-s001.vmdk' (001 to 016)
* use the old .vmx file, but remove the lines that start with:
    managedVM.autoAddVTPM
    managedVM.ID
    encryption.encryptedKey
    encryption.keySafe
    encryption.data

If there's no snapshots then you don't need .vmsd (don't copy it in the new vm, delete if there)

Normally also no need for .nvram and .vmxf

That __should__ be all.</text>
    <sha1>a5156c82e2d68abf931f91e69cfd5e060307a01f</sha1>
  </revision>
  <revision>
    <id>1547</id>
    <parentid>1546</parentid>
    <timestamp>2023-09-22T16:55:34Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1371" xml:space="preserve">You might have made the mistake to use an experimental solution that was offered for a while by VMware to install Windows 11 as guest OS.
It involved adding a line to the .vmx file and after that you could add a TPM and thus install Windows 11.
This would encrypt parts of the VM, but not give you a password and as such some people to find out that their VM won't work on some other hosts.
The good part is that your data isn't actually encrypted, the bad part is that it isn't easy perse to get the data out.

=== Here's one solution where you have a few manual steps ===


The steps to recover your VM are as follows:

I've written out the steps here: https://www.reddit.com/r/vmware/comments/qy9wns/comment/hmokzl7/

Let me quote myself from one of my replies...

The steps are basically:

* Create a new VM with a virtual disk of the same size as the encrypted one, make sure it has the same name.
* use the new descriptor file ('MK Win Desktop.vmdk')
* use the old vmdk data files ('MK Win Desktop-s001.vmdk' (001 to 016)
* use the old .vmx file, but remove the lines that start with:
    managedVM.autoAddVTPM
    managedVM.ID
    encryption.encryptedKey
    encryption.keySafe
    encryption.data

If there's no snapshots then you don't need .vmsd (don't copy it in the new vm, delete if there)

Normally also no need for .nvram and .vmxf

That ''should'' be all.</text>
    <sha1>91d15af2f2d69dad315917abace1edd6fe75d956</sha1>
  </revision>
  <revision>
    <id>1548</id>
    <parentid>1547</parentid>
    <timestamp>2023-09-22T17:02:12Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <minor/>
    <comment>/* Here's one solution where you have a few manual steps */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1937" xml:space="preserve">You might have made the mistake to use an experimental solution that was offered for a while by VMware to install Windows 11 as guest OS.
It involved adding a line to the .vmx file and after that you could add a TPM and thus install Windows 11.
This would encrypt parts of the VM, but not give you a password and as such some people to find out that their VM won't work on some other hosts.
The good part is that your data isn't actually encrypted, the bad part is that it isn't easy perse to get the data out.

=== Here's one solution where you have a few manual steps ===


The steps to recover your VM are as follows:

This reddit thread here has the steps: https://www.reddit.com/r/vmware/comments/qy9wns/comment/hmokzl7/ where I helped a user getting back their VM.

For this type of VM none of the data is encrypted and only the descriptor files are encrypted.
You can recreate the descriptor files and get back to a functional VM. If you haven't resized the virtual disks over time then it is a matter of creating a new VM with the exact same virtual disk in size.

That would be enough to get the descriptor data to copy over into the currently encrypted descriptor files. That should work.

If OTOH you have increased the size of your virtual disks over time then you have to repeat that increase in the exact same manner. 

The steps are basically:

* Create a new VM with a virtual disk of the same size as the encrypted one, make sure it has the same name.
* use the new descriptor file ('MK Win Desktop.vmdk')
* use the old vmdk data files ('MK Win Desktop-s001.vmdk' (001 to 016)
* use the old .vmx file, but remove the lines that start with:
    managedVM.autoAddVTPM
    managedVM.ID
    encryption.encryptedKey
    encryption.keySafe
    encryption.data

If there's no snapshots then you don't need .vmsd (don't copy it in the new vm, delete if there)

Normally also no need for .nvram and .vmxf

That ''should'' be all.</text>
    <sha1>cb0d4617f86174550529e4f6ca3d66278780dbf9</sha1>
  </revision>
  <revision>
    <id>1549</id>
    <parentid>1548</parentid>
    <timestamp>2023-09-22T17:05:55Z</timestamp>
    <contributor>
      <username>Wila</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2523" xml:space="preserve">You might have made the mistake to use an experimental solution that was offered for a while by VMware to install Windows 11 as guest OS.
It involved adding a line to the .vmx file and after that you could add a TPM and thus install Windows 11.
This would encrypt parts of the VM, but not give you a password and as such some people to find out that their VM won't work on some other hosts.
The good part is that your data isn't actually encrypted, the bad part is that it isn't easy perse to get the data out.

The following article: https://www.vimalin.com/blog/what-you-should-know-about-vmwares-experimental-vtpm/ has the technical background on what happens if you have used this experimental feature and is good background knowledge if you try to start trying to recover your VM.

=== Here's one solution where you have a few manual steps ===


The steps to recover your VM are as follows:

This reddit thread here has the steps: https://www.reddit.com/r/vmware/comments/qy9wns/comment/hmokzl7/ where I helped a user getting back their VM.

For this type of VM none of the data is encrypted and only the descriptor files are encrypted.
You can recreate the descriptor files and get back to a functional VM. If you haven't resized the virtual disks over time then it is a matter of creating a new VM with the exact same virtual disk in size.

That would be enough to get the descriptor data to copy over into the currently encrypted descriptor files. That should work.

If OTOH you have increased the size of your virtual disks over time then you have to repeat that increase in the exact same manner. 

The steps are basically:

* Create a new VM with a virtual disk of the same size as the encrypted one, make sure it has the same name.
* use the new descriptor file ('MK Win Desktop.vmdk')
* use the old vmdk data files ('MK Win Desktop-s001.vmdk' (001 to 016)
* use the old .vmx file, but remove the lines that start with:
    managedVM.autoAddVTPM
    managedVM.ID
    encryption.encryptedKey
    encryption.keySafe
    encryption.data

If there's no snapshots then you don't need .vmsd (don't copy it in the new vm, delete if there)

Normally also no need for .nvram and .vmxf

That ''should'' be all.

One final note is that it is highly recommended to never touch your original VM and instead work with copies of the data while you try to get your VM back up and running. That way if you make a mistake you can just redo the steps. Otherwise you might introduce more problems and who needs yet another problem?</text>
    <sha1>ddd35ac6780cf4f3dd5c751c90bdf74e5c800af1</sha1>
  </revision>
</page>
</mediawiki>